VERY SLOW Logons

[maxxxsteel]

I have a network at a school that is suffering from very very slow logons. They logon to a Windows 2000 adnvanced server running DNS, DHCP and AD of course. For some reason its taking a very long time for logons, all clients are XP Pro and DHCP. Any help is appreciated!

 

[eightball]

Make sure the clients are pointed to the servers IP (DNS). Also look for errors in the event viewer, pertaing to DNS or netlogon errors. Is there any hops between the clients and the server? Are they on the same subnet? Also check the NIC's for duplex. Sometimes fullduplex will produce these results. I hope this helps.

 

[Ntr0P]

I haven't experienced this issue, but do you have any insight why a full duplex configuration would result in this type of issue?

 

[maxxxsteel]

I was just at this network today and as I was looking over the setup of DHCP I noticed that it was passing out the DNS for another server on the network...a seperate trusted domain..now Im really confused. After I switched the DNS numbers that were being given to the clients, they were no longer able to surf...My DNS must be setup incorrectly

 

[dmandell]

Sounds like your DNS in the trusted domain may be forwarding to your AD DNS server. You should set it up the other way around.

If you do not care about the "other" trusted domain, and you are not using a proxy in that domain for internet browsing, Set your AD DNS server to forward to your ISPs DNS servers (out in the internet)

You did not say if changing the DNS made your login quick?

In response to Ntr0P, I think what was meant was that the "duplicity" of the network card could be set improperly. If it did not match, you would have massive retries and your network operations would be slow. I ran into this once, and matching the duplicity of the net cards solved the problem.
Dana

 

[Ntr0P]

dmandell - Thanks... that actually makes a whole world more sense.

 

[itismeee333]

I had the same issue, to resolve this go into your ip configurations in the tcp/ip property under dns, select advanced. select the DNS tab, under dns suffix for this connection type in the dns ip of your Domain controller. make sure there is a check in register this connection address in DNS. This solve slow logon for me.

 

[dmandell]

itismeee333- Can you shed some more light on this approach?

Using the IP address of a domain controller as a DNS suffix makes no sense at all to me. Did I mis-interpret your suggestion?

Dana

 

[sgscit]

I had a similar problem this morning on a number of machines after a flood incident where we had to unplug the PC's and servers and get them out of the water's path.

I found that the DNS settings were incorrect. By changing them to use automatic DNS (via DHCP options) and removing the "use this connections dns suffix in dns registration" it all worked fine again.

Strangely or not so strangely, the old config even though it was a valid config slowed it down immensely only after the unplugging of the PC's. It was taking 10 or 15 minutes to run through the initial boot to the login screen. Then the same to load the user even though we use local profiles, not remote.

Cheers,

Pete

 

[Ntr0P]

A little off topic, but you actually had a flood in your office?

 

[sgscit]

Yep two of our buildings had major flooding after 2.5 inches of rain in an hour. A trainee engineer was electricuted (he is ok - just a burnt hand and a big scare)when he went to turn off electrical equipment in the office and one of the server rooms had to be temporarily relocated.

One of the offices is still having staff transfered to other locations prior to the carpet being ripped up etc.

We have been in a drought for the last couple of years here in Eastern Australia and the rain has not been coming weekly or every few days, rather - someone pours a giant bucket on us every couple of months. Enough to wet the ground, overflow the drains and flood buildings.

Back to work.

Pete.