Router won't issue IP address - can't ping gateway

augoose

Distinguished
Dec 16, 2011
14
0
18,510
So I've got an HP tower (Vista) with an imbedded Nvidia network card that we were setting up for a client. Whle on the bench, the card was configured for automatic DHCP and the router assigned the card an ip address and everything was working fine- network and internet access.

We shut it down, transport the box and set it back up for the client. The client's router is a different brand/model than the router we used for the bench test, however it is set up the same (automatic DHCP, firewall, no fmac filtering, etc). The service is DSL. Modem feeds router, the router feeds to a hub, then the hub feeds out to the newly installed box.

We connect the network cable and fire up the box. What we find is that the network card can't communicate with the router. Running an ipconfig shows no gateway address and an ip address beginning with 169. Ipconfig /renew & release fails with the description that the network card can't reach the gateway.

I unplug the network cable and connect it to a laptop (windows 10). The router issues the laptop an address and I have internet and gateway access right away. I then disconnect the network cable and connect it back to the box - no access and no ip address assigned.

I tried the following: uninstall / reinstall nvidia drivers, reboots, - nada. Confirmed the card is set up for automatic DHCP. Tried pinging the gateway - nada. Tried 2nd network cable, changed ports in the hub, disabled firewall, confirmed the router is not blocking my mac address (no filtering) - all nada.

I then take a 2nd laptop (xp pro) which has never been on the client's network using the same original cable, automatic DHCP and no firewall and I get an ip address issued and can contact the gateway immediately.

Additionally, other users on the same LAN have had no issues and were actively connected so I didn't try rebooting the router. I felt I didn't need to since I was getting ip addresses assigned to two separate laptops.

So I bring the box back to the shop and I'm thinking the network card died at some point during transport. So we throw it on the bench and connect the network cable - our bench router assigns an ip address and we have instant network access and internet.

What am I missing?
 

augoose

Distinguished
Dec 16, 2011
14
0
18,510


Lol - I know. Its not my network, just something I have to deal with. I haven't check the speed - I suspect it is as both are DSL networks, but I'll add that to the list of things to verify - thank you!
 

augoose

Distinguished
Dec 16, 2011
14
0
18,510


I didn't try pinging 127 - I'll try it and see what I get. Although I can't recall exactly what it reads, there was nothing out of the ordinary when I ran ipconfig /all.
Maybe I don't understand your question regarding the scope - currently the box has a 169 address (can't recall the rest) because it can't contact the router (that's my assumption) - as a result, I have no IP address.