slow preparing network connections

[pollardhimself]

Alot of the xp computer's here are extremely slow at slow preparing network connections, Even if they dont have a network cable pluged in or are at home. Any ideas on a fix

 

[Fardringle]

Are the computers attached to a Windows domain? If so, I have seen this happen when the primary DNS server does not know how to locate the domain controller and the computers sit at the "preparing network connections" message while they wait for a response from the domain controller. If this is the case, you need to either make your domain controller's IP address the primary DNS server entry on your DHCP server (and make sure DNS is enabled on the server, including forwarding to your ISP's DNS server for Internet access), or configure your local DNS server/router with an entry for the domain controller.

 

[theevilsharpie]

They're slow preparing a network connection, even if they're not plugged in?

Huh? I assume 'not plugged in' means connecting via wireless.

In my experience, Windows 7's and (particularly) Vista's network status display is inaccurate. I've had it show that my connection is disconnected or limited to internal connectivity only, even though I'm fully capable of accessing the Internet.

If the message is accurate and your computers are taking a long time to get an IP address, there are a number of possible causes. The likely culprits are time-out errors caused by STP (most likely in a corporate network), overly-aggressive duplicate IP checks done by the DHCP server, or a shitty DHCP server that doesn't work quite right (most likely in a home network).

The easiest way to resolve this is to assign yourself a static IP address.

 

[pollardhimself]

They're slow preparing a network connection, even if they're not plugged in?

Huh? I assume 'not plugged in' means connecting via wireless.

In my experience, Windows 7's and (particularly) Vista's network status display is inaccurate. I've had it show that my connection is disconnected or limited to internal connectivity only, even though I'm fully capable of accessing the Internet.

If the message is accurate and your computers are taking a long time to get an IP address, there are a number of possible causes. The likely culprits are time-out errors caused by STP (most likely in a corporate network), overly-aggressive duplicate IP checks done by the DHCP server, or a shitty DHCP server that doesn't work quite right (most likely in a home network).

The easiest way to resolve this is to assign yourself a static IP address.

No I mean booting with no lan connection at all wireless or wired