I am having a problem with accessing the NT domain. I accidently hit delete owner in the WINS manager (please don't ask how - just stupidity really). Anyway, after that it took a reboot of all the machines to get back in the database listing, and all the computers on the network CAN log in to the domain, but if I try to administer it from another machine, it says domain can not be found. Also, I am trying to add a new machine to the domain, and I am getting the same message. It's strange I can logon to the domain with computers that were already on the domain before, but can't add a computer to the domain, even when it's name is in server manager (I can access it only from the PDC itself now). Any help would be greatly appreciated. PDC is a Win NT 4 SP 6 running WINS, DHCP.. Clients are almost all Windows 2k, some Win98

Do you run a DHCP or a static IP network? I run a static setting and I have forgotten to input the IP for a machine before and got that result, also remember, when adding the machine go into the network stack and go to the Client for Microsoft Networks and set it to log onto the correct domain. Other than that, I have noticed that if I let a PC sit live on the network, it has finally authenticated after a while, maybe was a NIC card issue. Just some ideas, and also reply on the DHCP or static IP part.

Replying to: "Do you run a DHCP or a static IP network?" DHCP (as mentioned in my post above) "I run a static setting and I have forgotten to input the IP for a machine before and got that result, also remember, when adding the machine go into the network stack and go to the Client for Microsoft Networks and set it to log onto the correct domain." You don't set it that way in Windows 2000, but that's when I am getting the error message, when I try to add the computer to the domain under "Network Identification" in System Properties. I am also getting the message about not finding the domain when I try to do any administering (Server Manager for Domains, User Manager for Domains, etc.). "Other than that, I have noticed that if I let a PC sit live on the network, it has finally authenticated after a while, maybe was a NIC card issue. Just some ideas, and also reply on the DHCP or static IP part." Well, it's not a NIC card issue because this system was on the network before and connected to the domain as well, just yesteday. I reformatted and re-installed Win 2k and now I want to add the computer to the domain so it can logon to it (getting the roaming profile, scripts, etc.). The problem started when I stupidly clicked on "Delete owner" in the WINS manager. Maybe uninstalling the WINS service and re-installing would fix the problem? I want to reboot the server to see if that helps, but can't until the weekend. I added the domain to the static settings in the WINS manager, but that didn't help. All help is greatly appreciated. Adam

You can do the following to Flush the Wins Database and let i rebuild. -Create a folder called WinsOld in your WinNT\System32 directory. -In WINS manager, delete all static mappings and turn off all replication partners for both push and pull. -From the command prompt, type in "net stop wins" to stop the WINS service. -Cut,Copy and paste all the contents of the Wins Folder from WinNT\System32 folder to the new WinsOld Folder. -Reboot the machine. -In WINS manager: Create a STATIC Domain mapping for the Domain, which includes the PDC and all BDC's. -Create a group mapping with the IP addr. of the PDC and the name of the Domain. -Also, add a unique mapping for the PDC with it's unique netbios name. In DHCP, make sure that your scope defaults have the right default WINS servers setup. You WINS database should rebuild itself in about an hour or so. Make sure you stop and restart DHCP, and DNS services also. On your PDC, make sure it registers itself as Domain Master Browser. For every 45 computers, you must have a server maintaining a browse list.(ideally) On your BDC's, set teh Is Domain Master registry key to False, and Maintain Browse list to YES Good luck! DM