1

Clients PC takes 30 min to boot… Is it problem of DNS? any solutions? and what DNS plays roles on PC boot up?

It would be nice really nice and grateful to you if anyone can give me solution about this problems…

3 Spice ups
2

If a Windows computer is part of a domain and it can’t find the domain controllers in DNS, they will take forever to start.

If you have an ISP DNS entry on the PC, it can get to the internet but is very slow for filesharing, etc.

3

I usually find it is the profile that tends to slow things up. If it is XP, there is a profile hive helper utility you can install.

4

everything is okey… LOCAL domain iz correct and everythign is fine, just 1 pc got those problem . and i heard that its DNS issue… any reason guys

5

Waaaaaaaaaay too little information. What OS of the desktop? Windows domain controllers? Symptom list?

Working from the presumption it’s a Windows environment… Yes, DNS can cause those types of issues, for a lot of reasons. Check the system and application event logs to see what errors are getting tossed.

6

just 1 PC having those issue… rest of other are working nicely.

DOMAIN OS iz 2k8 and client iz win7

7

I had similar issue, because of a wrong DNS server. It was actually pointing to an non-existent external DNS server. I changed it to a local DNS server and it worked great after the change.

8

Boot in safe mode, reset TCP/IP stack. reboot in normal mode.

Make sure it is set to obtain IP and DNS automatically.

Also, I would check this first, make sure that is not trying to do a PXE boot by the boot order in the BIOS. Since it can be trying to find in the network and will take for-e-ver to boot.

2 Spice ups
9

Just to give you an idea of why it might be slow. (and I’m guessing a Windows PC) Windows has a list of startup actions it must complete every time it starts up. Nowadays that usually includes software looking for updates automatically. Until all those tasks complete, the machine is too busy to want to talk to the user. If DNS is wrong or slow, the machine will request the DNS lookup then wait until it times out. If the timeout value is 5 seconds and you have 8 things requesting updates, thats 40 extra seconds, and each item may try your alternate DNS server. Anything you can cut out of the startup sequence helps. I once had a manger call me up complaining that his machine was taking too long to startup (Windows 3.11). I get there and restart the machine. After he put in his password, it launches in to a 30 second sound bite from the Blues Brothers. I had to explain to him that the pc waits until the sound has completed until continuing. OH, sorry.