long delay at "preparing network connection" W2K answer found (disable DNS Client)

[AnMig]

I am pretty sure one of you guys know the answer and its probably a network setting that I have to fix, Please lend me your wisdom.

This is a Dell 1.8ghz office machine running W2K with all the latest serice packs and updates (service pack 4).
I currently have a double boot system W2K and XP pro.
The boot up from XP is a breeze.
The boot up from W2K takes about 1 minute at this preparing network connection screen.

I read somewhere that W2K does this when it cant decide if its the master or slave of the network.

P.S. I have full reign over this office computer and can do whatever I please with it.

Please advice

 

[rmrf]

Is it connected to the network at all times? Do you have the current NIC driver installed? Is the netbios name causing any problems on the network (localhost, etc.)? How big of a network is it that the computer is on? What other types of machines are on this network? Do you have any sort of a server type service running that would take a little bit of time to load or start?

These are all questions that you should find out if you haven't already. Sorry if it seems like I am being rude, but these are the questions I ask myself when I have a problem related to networking.

 

[NogginBoink]

It's probably trying to register itself with your ISP's DNS servers and they're not allowing the dynamic registration.

Might I suggest a walk through your system's event logs to garner more clues about potential causes of the problem.

 

[Bleep]

I have this same problem with a win2K system but only when I have 2 hard drives installed or 1 hard drive with a dual boot setup,

Bleep

 

[ProviaFan]

Originally posted by: NogginBoink
It's probably trying to register itself with your ISP's DNS servers and they're not allowing the dynamic registration.

Might I suggest a walk through your system's event logs to garner more clues about potential causes of the problem.

Try DHCP, not DNS. A machine that's trying to get DNS, IP, and routing info (default gate) from a DHCP server, when there is none, will have a pause at boot-up. However, I believe that Windows 2000 will pause during the splash screen (earlier in the boot process) if it can't get DHCP info.

 

[NogginBoink]

Originally posted by: jliechty

Originally posted by: NogginBoink
It's probably trying to register itself with your ISP's DNS servers and they're not allowing the dynamic registration.

Might I suggest a walk through your system's event logs to garner more clues about potential causes of the problem.

Try DHCP, not DNS. A machine that's trying to get DNS, IP, and routing info (default gate) from a DHCP server, when there is none, will have a pause at boot-up. However, I believe that Windows 2000 will pause during the splash screen (earlier in the boot process) if it can't get DHCP info.

While you are correct about your DHCP comments, I did mean DNS.

W2K supports dynamic DNS registration. In a domain, member machines typically do a DDNS registration with the DNS server in the domain. In a misconfigured system, W2K will attempt to do a DDNS registration with your ISP's DNS servers, which results in a long delay as W2K waits for a response from the DDNS registration attempt that never comes back.

I see this happen frequently on upgrades to W2K where the server is still pointing to the ISP instead of the internal DNS server for DNS resolution. And it can cause a very substantial delay in booting.

 

[ProviaFan]

Originally posted by: NogginBoink
While you are correct about your DHCP comments, I did mean DNS.

W2K supports dynamic DNS registration. In a domain, member machines typically do a DDNS registration with the DNS server in the domain. In a misconfigured system, W2K will attempt to do a DDNS registration with your ISP's DNS servers, which results in a long delay as W2K waits for a response from the DDNS registration attempt that never comes back.

I see this happen frequently on upgrades to W2K where the server is still pointing to the ISP instead of the internal DNS server for DNS resolution. And it can cause a very substantial delay in booting.

It's just me speaking prematurely and showing my stupidity again. Sorry.

I did learn something new from your comments, though.

 

[BurnItDwn]

I had that same problem with my windows boxes for a while ... it was a conflict with my samba setup on my server ... best of luck to you

 

[AnMig]

Sorry for not responding

I finally found an answer to my long delay at "preparing network connections" window (60 seconds)



I had to disbale my "DNS CLIENT" I no longer get this window and boot up is instantaneous.



loctaed at:


Control Panel/Administrative tools/Component Services/Services (local) ---then turn off "DNS Client"

hope this helps someone

 

[Guga]

Sorry for not responding
I finally found an answer to my long delay at "preparing network connections" window (60 seconds)



I had to disbale my "DNS CLIENT" I no longer get this window and boot up is instantaneous.



loctaed at:


Control Panel/Administrative tools/Component Services/Services (local) ---then turn off "DNS Client"

hope this helps someone

Don't do that. If you disable DNS Client service you will no more be able to resolve dns querys.

Enable it again, and to the follow:

Go to properties of network connections
go to properties of local area connection (or the name you had in your lan conection)
go to TCPIP
click properties
click advanced
click DNS tab
uncheck Register this connection 's adresses in DNS
click ok
click ok
click ok

Try it now

 

[Guga]

The DNS Client service optimizes the performance of DNS name resolution by storing previously resolved names in memory. If the DNS Client service is turned off, the computer can still resolve DNS names by using the network's DNS servers.

Even so, the method I said must be used.

 

[AnMig]

Don't do that. If you disable DNS Client service you will no more be able to resolve dns querys.

Enable it again, and to the follow:

Go to properties of network connections
go to properties of local area connection (or the name you had in your lan conection)
go to TCPIP
click properties
click advanced
click DNS tab
uncheck Register this connection 's adresses in DNS
click ok
click ok
click ok
.

already tried that in the past and just tried it again. It still results in a 60 sec pause at "preparing network connections"

The only thing that has worked so far is disablng the DNS CLIENT.

thanks anyway.

Any body alse has a alternative? This is a office pc by the way and I have to type in the DNS manually when configuring it.