We have a Microsoft Windows Network within our school. The Domain Controller runs Windows Server 2003 Standard with SP2 and the Clients run XP with SP3 All of the Client Workstations grind when Windows starts up at the 'Preparing Network Connections' point so on until logon. (Approx. 2 Minutes) From what I have read it can be related to DNS but I don’t think it’s that in our case. I think there is a service or setting somewhere, either on the client or DC, which can prevent the start-up dialogue boxes appearing at all. Has anyone had similar problems and if so, PLEASE HELP!

Can you provide the ipconfig /all of client XP machine and DC?

From what I have read it can be related to DNS but I don’t think it’s that in our case. If it were just one client stalling out here, I'd suspect the client. If it's all of them, then it's more likely to be your DNS setup. So what troubleshooting steps have you taken that makes you think it isn't DNS? If you haven't actually done any troubleshooting on DNS and are just assuming it's not.....then I'd recommend you start by looking at DNS. First, check to ensure the clients have the correct DNS address. Then check to ensure DNS is setup correctly and your records are correct for the clients. How long have you had this domain setup? Has this issue always existed or is it new? If new, what, if anything, did you change on the DC/clients prior to the issue starting? I think there is a service or setting somewhere, either on the client or DC, which can prevent the start-up dialogue boxes appearing at all Which dialogue boxes are you talking about?

Is there DHCP configured on server or using static ip address for all clients? if DHCP then try to put the DNS ip address into nic properties on the client machine. let me know the confi on the server for releasing the ip address to the client.

I agree with Sujet; it looks like the client machine is using an external DNS instead of your Local DNS server. That will cause the clients to slow down since they will try to go out to the internet looking for the DC.

I have solved my problem. Like many suggested, it was a DNS problem. The client machines were setup to pick up a different IP from that of the DC. I changed this and also knocked off there GP 'Always wait for the network to be fully initialized before logon'. Much quicker now, thanks a lot. We also found that some OU's were picking up the same GPO several times which once removed increased the login time too.