A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Need Ipconfig /renew to get an IP after reboot



 
 
Thread Tools Display Modes
  #1  
Old March 31st 10, 05:42 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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.

Ads
  #2  
Old March 31st 10, 07:13 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

Hi
What is common (hardware/software) between the different trials?
Jack (MS, MVP-Networking).

"Ian" wrote in message
...
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.


  #3  
Old March 31st 10, 07:13 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

Hi
What is common (hardware/software) between the different trials?
Jack (MS, MVP-Networking).

"Ian" wrote in message
...
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.


  #4  
Old March 31st 10, 08:50 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


.

  #5  
Old March 31st 10, 08:50 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


.

  #6  
Old March 31st 10, 10:09 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


  #7  
Old March 31st 10, 10:09 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


  #8  
Old April 1st 10, 04:02 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


.

  #9  
Old April 1st 10, 04:02 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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" wrote in message
...
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.


.

  #10  
Old April 1st 10, 06:40 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot

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.

"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" wrote in message
...
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.


.

  #11  
Old April 1st 10, 06:40 PM posted to microsoft.public.windowsxp.network_web
Ian
external usenet poster
 
Posts: 656
Default Need Ipconfig /renew to get an IP after reboot


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.

"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" wrote in message
...
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.


.

  #12  
Old April 1st 10, 11:12 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

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)..

"Ian" wrote in message
news
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.

"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" wrote in message
...
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.


.


  #13  
Old April 1st 10, 11:12 PM posted to microsoft.public.windowsxp.network_web
Jack [MVP-Networking]
external usenet poster
 
Posts: 552
Default Need Ipconfig /renew to get an IP after reboot

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)..

"Ian" wrote in message
news
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.

"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" wrote in message
...
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.


.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 04:53 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.