Unsolved
This post is more than 5 years old
7 Posts
0
64561
October 17th, 2008 07:00
DHCP problem, APIPA
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
No Events found!


volcano11
2 Intern
•
28K Posts
0
October 17th, 2008 12:00
Try downloading and running winsockfix for Windows XP from the Here
Steve
jvandamme
7 Posts
0
October 17th, 2008 13:00
disabled that too, still same story :(
jvandamme
7 Posts
0
October 17th, 2008 13:00
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
2 Intern
•
1.7K Posts
0
October 17th, 2008 13:00
volcano11
2 Intern
•
28K Posts
0
October 17th, 2008 14:00
After the clean install, did you install the chipset drivers before attempting to install the network drivers?
Steve
kikomatsing
121 Posts
0
October 17th, 2008 23:00
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
2 Intern
•
12K Posts
0
October 18th, 2008 03:00
jmwills
2 Intern
•
12K Posts
0
October 20th, 2008 07:00
jvandamme
7 Posts
0
October 20th, 2008 07:00
jvandamme
7 Posts
0
October 20th, 2008 08:00
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
7 Posts
0
October 20th, 2008 08:00
Someone already advised this in the start of this post. Still the same
jmwills
2 Intern
•
12K Posts
0
October 20th, 2008 08:00
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
2 Intern
•
12K Posts
0
October 20th, 2008 08:00
Larry R
2 Intern
•
1.7K Posts
0
October 20th, 2008 15:00
jvandamme
7 Posts
0
October 23rd, 2008 12:00
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