Need Ipconfig /renew to get an IP after reboot
in [Network and Web]
|
From: Ian on 31 Mar 2010 12:42 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.
From: Jack [MVP-Networking] on 31 Mar 2010 14:13 Hi What is common (hardware/software) between the different trials? Jack (MS, MVP-Networking). "Ian" <Ian(a)discussions.microsoft.com> wrote in message news:F08F235A-3E3C-470F-BAC2-9874EE38DC20(a)microsoft.com... > 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. >
From: Ian on 31 Mar 2010 15:50 The same core image setup on Dell Optiplex 745/755, Windows XP SP2. Do you mean these? "Jack [MVP-Networking]" wrote: > Hi > What is common (hardware/software) between the different trials? > Jack (MS, MVP-Networking). > > "Ian" <Ian(a)discussions.microsoft.com> wrote in message > news:F08F235A-3E3C-470F-BAC2-9874EE38DC20(a)microsoft.com... > > 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. > > > > . >
From: Jack [MVP-Networking] on 31 Mar 2010 17:09 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).. "Ian" <Ian(a)discussions.microsoft.com> wrote in message news:F08F235A-3E3C-470F-BAC2-9874EE38DC20(a)microsoft.com... > 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. >
From: Ian on 1 Apr 2010 11:02
Tried these steps but still not work. "Jack [MVP-Networking]" wrote: > 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).. > > "Ian" <Ian(a)discussions.microsoft.com> wrote in message > news:F08F235A-3E3C-470F-BAC2-9874EE38DC20(a)microsoft.com... > > 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. > > > > . > |