Another 2000 Server problem

[Hoober]

Ok, I've got my server up and running, even had the domain up and running so that clients could join it and everything was running great. All of a sudden, after a restart of the server because of a software install, no one can browse the domain... "cannot connect to this remote computer because it already has as many conections as it can set."

I've got the licensing set at some ungodly amount as per server. I've tried per seat, but that didn't help. My router is handing out DHCP except for the server which is on a static ip from the router. The DNS numbers have to coded in for my ISP in order to get out to the internet -- so I've got DNS suffix numbers appended to all the clients to find the DC.

The weird thing is that it was working fine until I restarted the server. Then all of a sudden I get the weird error message and the event log displays the error that there is a duplicate name on the network. Except that the server is the only one of its name on my network... somebody has to have some ideas, please!

 

[randal]

turn off the server. turn off every other computer. turn the server on. let it boot *completely*, then turn on all the other machines ...

taking the domain controller offline and bringing it online without either A) removing it from the network or B) removing everything else on the network often causes problems.

$.02
randal

 

[Hoober]

Ok -- I went home for lunch and everything's working fine on the two client computers that I booted up. I didn't restart the server or anything since it stopped working last night. Sounds like that other name was interfering with it, but that doesn't make sense unless it was finding that name somewhere on the ISP's network.