Desktop

Ask something
Discussion Locked

XP Home not using DHCP server

0 helpful
11 replies

by jenral_sam 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A computer using XP Home SP1 is connected to a network, which has a DHCP server that other computers connect to, but it will not connect to and assigns its own ip (169.254...). Does anyone know a fix for this.
I know the card works, because i can manually configure it, but i do need it to use the DHCP server. OS up/down-grade is not an option.

Thanks 4 Reading.

Sam Stevens

11 replies

by p.j.hutchison

Make sure TCP/IP is installed and set up to automatic.
Make sure the 'DHCP Client' service is running.
Make sure the 'IPSEC Services' service is running.
Make sure the 'Remote Procedure Call (RPC)' service is running.

Make sure Network cable is firmly connected to back of PC and connected to hub, switch or router or whatever...

by dmwoodcock

My Network Card Won't Connect
Another common problem is when your network card won't connect and you've got an IP address that starts with 169.254. This can happen with either a regular network card or a wireless card, but is more common with a wireless card. The IP address that starts with 169.254 indicates that you didn't receive an IP address from a Dynamic Host Configuration Protocol (DHCP) server for some reason, probably because there is a connectivity issue. If this is a wired connection, start by checking that the status lights on the back of the network card are the proper color. See your network card documentation for what the different colours mean. If they aren't the right color, there are at least five possibilities:

? The cable is bad.

? The cable is not firmly connected at both ends.

? The port on the hub or router is bad. Try plugging the network cable into a different port on the hub or router.

? The network card is bad.

? The cable is the wrong kind of network cable.

Let's examine that last possibility. You should always use CAT5, CAT5+ or CAT6 network cable. Not phone cable or other kinds of cable that may look the same. Second, there are both "straight-through" and "cross-over" cables. If you're connecting to a hub, switch, or gateway, then you need a straight-through cable. If you're connecting directly from the network card on one computer to the network card on another, you need a cross-over cable. For more information about cables, see Understanding Ethernet Cabling.

by jenral_sam

Quote from my question "know the card works, because i can manually configure it" and i can reach other computers when doing this

by joed_jackson

No fix but Part of your answer is in the network functions include is XP Professional not include XP Home. Microsoft states Unlike Windows XP Professional, Windows XP Home Edition is NOT able to join a Domain: (no possibility to define the Domain name in the Properties of your XP Home Edition system) Which may be the reason DCHP issue.
A little help, I hope

by wlbowers

Check the other computers. Duplicate the gateway, wins, and make sure DHCP is enabled.

Lee

by john

Not enough information to properly diagnose but here is a shot.

What message appears when you release and renew the IP? Is it the default "unable to obtain address"?

Is XP's firewall set a little too high?

Most likely problem - drivers for NIC work OK but not completely.

I had the same type of problem on a Dell (with onboard NIC) for my home network. I could pimg the router (also providing DHCP services) and connect if I manually set the address, etc. but getting the system to automatically receive an IP would not work.

Unfortunately my only solution at the time was disable the onboard NIC and use an inexpensive replacement. Worked great first time and every time since. I believe your answer lies in the drivers. You may find a specific resolution by searching for the NIC model number and XP home.

Hope you find a solution.

This discussion is closed to new replies.