Need Ipconfig /renew to get an IP after reboot

  • Thread starter Thread starter Ian
  • Start date Start date
I

Ian

This is not a dhcp server issue because all existing PCs are fine.
This is not hardware issue since it happend on different PCs with the new
image.
I setup NIC speed as 100/Full like all other PCs.
After log on local admin and run ipconfig /renew, I get the IP.

I ping this PC "ping xxxx.xxxx.xxxx.xxxx -t" when it reboots. Then I get
something like below. Any suggestions?

Request timed out.
Request timed out.
Request timed out.
Reply from xxxx.xxxx.xxxx.xxxx: bytes=32 time=1ms TTL=123
Reply from xxxx.xxxx.xxxx.xxxx: bytes=32 time=1ms TTL=123
Reply from xxxx.xxxx.xxxx.xxxx: bytes=32 time=1ms TTL=123
Reply from xxxx.xxxx.xxxx.xxxx: bytes=32 time=1ms TTL=123
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Hi
What is common (hardware/software) between the different trials?
Jack (MS, MVP-Networking).
 
Hi
Uninstall/Delete the NIC in the Device Manager.
Boot the computer enter to the BIOS and disable the Network card.
Reboot one time with No network card.
Boot again enable the NIC and make sure that you install the latest Drivers.
Set the Drivers to Auto Negotiate.
Other computers might be OK to work at Full Duplex level, however forcing a
Network card to Full Duplex when something mighty be wrong with a network
Device/Computer is not a Good idea.
Jack (MS, MVP-Networking)..
 
Tried these steps but still not work.

Jack said:
Hi
Uninstall/Delete the NIC in the Device Manager.
Boot the computer enter to the BIOS and disable the Network card.
Reboot one time with No network card.
Boot again enable the NIC and make sure that you install the latest Drivers.
Set the Drivers to Auto Negotiate.
Other computers might be OK to work at Full Duplex level, however forcing a
Network card to Full Duplex when something mighty be wrong with a network
Device/Computer is not a Good idea.
Jack (MS, MVP-Networking)..



.
Click to expand...
 
Just like what I said that all existing PCs are able to get IPs after each
reboot on this network except this one. However, when I connected this PC
that has a new image on, to another network and reboot, it got IP.
 
Hi
Check all setting of the Router and make sure that there is No duplication
or banning of the MAC address. Make sure that the MAC number is the actual
MAC number of the current hardware and not a residual of the image.
Also try a static IP that is Not within the range of the DHCP and see if it
work normally with static IP.
Jack (MS, MVP-Networking)..
 
Back
Top