SYMPTOMS: 1. Workstations will intermittantly loose access to the domain. 2. Most users will intermittantly loose access to the PDC, this will usually continue all day. At that time the PDC is pingable to its IP address and not name. 3. We recieve authentication errors from other servers trying to get into the PDC. 4. In the WINS database _MSBROWSE_ changes rapidly and is only sometimes our PDC. 5. Lost another network that is in our domain but is remotely connected via T1. They do not show up in Network Neighborhood at all. 6. On most workstations the event ERROR 8032 = Browser has failed to retrieve backup list, Backup browser is stopping. 7. When using browstat the ERROR 53 will display when we cant connect while symptom 2 is happening. 8. The PDC is a WINS server and a server on the second subnet is a WINS server. 9. On the PDC we input the same ip address statically as per technet. We attempted to do so on the second WINS server and then that server would not see our second subnet. 10. On some workstations at a remote site we are getting Lanman errors. I am not aware if there are older OS's installed. 11. Browstat & Browmon will sometimes show only one backup browser. NETWORK FACTS: 1. We have two subnets and have a win server on each subnet on the PDC and a server on the second subnet. It is neccessary that we have 2 subnets due to a contractual agreement. 2. Server is not multihomed. 3. WINS scheme: Hub & Spoke: 9 WINS servers alltogether. A remote site from our own is the hub and everyone else is set to push and pull from the hub. One sit is set only to pull from the hub because we thought it may have been problematic 4. Static entries have been input for each site. Some servers would not show up and some workstations When the entries were input the machines would then be browsable. 5. All servers are NT4.0. with the most current service pack. Work stations consist of NT4.0 and 2K. TROUBLESHOOTING STEPS TAKEN SO FAR: 1. Checked the PDC's NIC card. It was working correctly. changed it to a new NIC card anyway. At that time our PDC's services (all) stopped running (melt down of some sort). We promoted the BDC to PDC and reinstalled NT on it once it was back up we made it the BDC. Once promoted, browsing worked properly for a day and then all problems were back. 2. Stopped, deleted and rebuilt the WINS database simutaneously on all wins servers (9). Browsing worked well for 1 day and then back to its dirty old tricks. 3. The PDC's reg keys were changed to yes for "IsDomainMaster" & "MaintainServerList" Craig

Is the wins server also set to be a wins client?