DHCP problem, APIPA

Question

Hello,   I have a Dell Optiplex GX620 with a weird DHCP problem.   When using the network connection on a fresh installed device I cannot contact the DHCP server to get a lease. But I receive an APIPA address 169....   When I use the same networking cable on another device I have no problems there. When I use another networking cable on the troubled device I get the same issue. I already reinstalled the drivers, reinstalled the OS(windows XP). Still nothing better. I even tried manual static settings for the NIC, doesn't work either.   Would this be related to a broken NIC?   Anyone any other suggestions?    Thanks already,   J

volcano11 · Answer

Try downloading and running winsockfix for Windows XP from the Here   Steve

jvandamme · Answer

disabled that too, still same story :(

jvandamme · Answer

Good suggestion but that doesn't work, I have a clean install now with only the NIC drivers installed, so spyware isn't possible.

I even disabled APIPA in the register, but now the NIC is always trying to acquire a network address.

J

Larry R · Answer

Windows firewall?

volcano11 · Answer

After the clean install, did you install the chipset drivers before attempting to install the network drivers?   Steve

kikomatsing · Answer

by the way do you have an integrated NIC or a separate one?? if you tried the drivers, winsock, etc.. in windows, try to run diags on the NIC itself..

jmwills · Answer

The results of an ipconfig /all would be helpful.

jmwills · Answer

This could be nothing more than a bad cable.  The PC does not see a valid DHCP server as evidenced by the 169.254.x.x address. The card is working properly.

jvandamme · Answer

Yes I tried both, first the NIC drivers and another time first the chipset. Still nothing, shows always as correct installed though.

ipconfig /all result:

Windows IP Configuration

Host Name . . . . . . . . . . . . : sysadmin-2f3279

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller

Physical Address. . . . . . . . . : 00-12-3F-64-AF-17

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.70.138

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

Thanks for thinking with me,

J

jvandamme · Answer

yes , well that's the weird thing, the cable is fine because when I connect my laptop to it, I receive DHCP settings.    It just doesn't follow the logic of networking :(

jvandamme · Answer

Someone already advised this in the start of this post. Still the same

jmwills · Answer

The only other thing it could be, possible two, is the wrong driver or just a bad NIC.

Download the newest driver to the desktop. Find the current driver in use, rename it by placing a "1" at the end, reboot, and when the deivce need a driver, point it to the new driver on the desktop.

If that fails, get a new NIC.

jmwills · Answer

Google for a program named Winsockfix for XP and run it.  If the cable is good, I suspect the TCP stack is corrupt.  Thsi utility will reset the stack to default settings.

Larry R · Answer

Do you have MAC address filtering enabled on the router?

jvandamme · Answer

The problem was the VLAN, my mistake, but the mac filtering hint did me recheck that part. Although it was in the MAC filtering list , it was in the wrong one and as 1 Switch had a specific VLAN where this device couldn't connect to... no ip was given, of course I didn't try this desktop on the other side of the company :)

Thanks for helping me all!

J

Networking, Internet, & Bluetooth

Was this post helpful?