bit-tech.net

SeT · 10th Jun 2009, 20:59

I'm working on a computer that was just re-imaged with Windows XP SP1 that is having network connectivity issues...

The computer gets a valid IP but is not pingable from outside the network(it's at a remote site) but I can ping other computers on their network from outside. If I remote into the server at the site, I can ping the computer that was re-imaged and I'm also then able to remote in to the re-imaged computer from the server so jumping remote-to-remote. The re-imaged is unable to ping anything at all.

I have tried everything I can think of from checking for Proxy, /release/renew IP(It still pulls the same IP from DHCP), flush DNS and Routing... I checked for the windows firewall and it was off also.

The software installed is all standard, MS Office, McAfee AV and Windows. No additional firewall.

finally(doubting that it would work) I set a static IP. IT WORKED! The computer has full internet access and can ping internal and external addresses. This makes no sense at all to me. I checked the IP before setting static and there was a valid IP, Subnet, and Gateway. How does it get the IP and then can't contact anything? It successfully released the IP showing all 0's, I removed the lease on the server, renewed and the lease shows up with the new name I had given the computer so I know it did that much yet couldn't even ping the dhcp server once it had the IP again.

I'm stumped. I don't want to leave it with the static IP due to possible duplicate IP issues down the road but I don't know what to do to get it to communicate on the network without static. Any ideas, anyone?

capnPedro · 10th Jun 2009, 21:26

Run "ipconfig" after getting an address from DHCP; make sure it's not a provate address, on the wrong subnet, or within the DMZ.

SeT · 11th Jun 2009, 11:53

The IP, Subnet, and Gateway obtained from DHCP were correct.

capnPedro · 11th Jun 2009, 17:11

When you set the static IP, was it the same as obtained from DHCP? Or did you use a different one outside of the DHCP range?

SeT · 11th Jun 2009, 19:38

It was a different IP but still in DHCP range.

capnPedro · 11th Jun 2009, 20:25

Interesting...

Try this at command prompt:
ipconifg /release
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns

Sorry, I don't have a machine on my network configured via DHCP to test with, but I'm pretty sure that's the correct order to run the commands.

If it then still doesn't work, try the old Right click on network connection -> Repair

Pendarus · 13th Jun 2009, 05:56

It sounds like a DNS registration problem.

Try removing the computers entry manually from the DNS server. If it has the same name on the network as before it was re-imaged, you may find multiple entries with different IP's assigned.
Reboot and run:

"ipconfig /registerdns"

This should solve your issue.

Hope this helps.

sui_winbolo · 13th Jun 2009, 06:44

Feel free to correct me on this, I work better at resolving issues in person.

But if it was a DNS issue, you should still be able to ping internally, correct?

Because he couldn't ping internally, that leads me to believe that it's not a DNS problem.

One thing that might be overlooked, have you tried updating to SP3?

I'm not going to lie, it wouldn't be one of the first places I would look either. But, I would look considering SP1 is pretty outdated and it could simply be a problem with Windows, or a driver.

Do you have a dedicated DHCP server or is a router acting as the DHCP?

Pendarus · 13th Jun 2009, 18:54

Quote:

Originally Posted by sui_winbolo

Feel free to correct me on this, I work better at resolving issues in person.

But if it was a DNS issue, you should still be able to ping internally, correct?

Because he couldn't ping internally, that leads me to believe that it's not a DNS problem.

One thing that might be overlooked, have you tried updating to SP3?

I'm not going to lie, it wouldn't be one of the first places I would look either. But, I would look considering SP1 is pretty outdated and it could simply be a problem with Windows, or a driver.

Do you have a dedicated DHCP server or is a router acting as the DHCP?

I know it seems a bit odd, but I have had this issue on my network.

The suggestions I made solved my problem. If not I have also found replacing the Network card will solve it as well. The card is not bad, it can be used in another system.

I find the network gets confused when you re-image a system, it is just a little different and is seen as a new computer.

10th Jun 2009, 20:59	#1
SeT Hypermodder Join Date: Oct 2003 Location: Cincinnati Posts: 644	Windows networking issues I'm working on a computer that was just re-imaged with Windows XP SP1 that is having network connectivity issues... The computer gets a valid IP but is not pingable from outside the network(it's at a remote site) but I can ping other computers on their network from outside. If I remote into the server at the site, I can ping the computer that was re-imaged and I'm also then able to remote in to the re-imaged computer from the server so jumping remote-to-remote. The re-imaged is unable to ping anything at all. I have tried everything I can think of from checking for Proxy, /release/renew IP(It still pulls the same IP from DHCP), flush DNS and Routing... I checked for the windows firewall and it was off also. The software installed is all standard, MS Office, McAfee AV and Windows. No additional firewall. finally(doubting that it would work) I set a static IP. IT WORKED! The computer has full internet access and can ping internal and external addresses. This makes no sense at all to me. I checked the IP before setting static and there was a valid IP, Subnet, and Gateway. How does it get the IP and then can't contact anything? It successfully released the IP showing all 0's, I removed the lease on the server, renewed and the lease shows up with the new name I had given the computer so I know it did that much yet couldn't even ping the dhcp server once it had the IP again. I'm stumped. I don't want to leave it with the static IP due to possible duplicate IP issues down the road but I don't know what to do to get it to communicate on the network without static. Any ideas, anyone?

10th Jun 2009, 21:26	#2
capnPedro Hacker. Maker. Engineer. Join Date: Apr 2007 Location: North-East England Posts: 4,381	Run "ipconfig" after getting an address from DHCP; make sure it's not a provate address, on the wrong subnet, or within the DMZ. __________________ There is no better previewing system than the 'Submit Reply' button. I <3 Aquatuning & Enermax long time!

11th Jun 2009, 17:11	#4
capnPedro Hacker. Maker. Engineer. Join Date: Apr 2007 Location: North-East England Posts: 4,381	When you set the static IP, was it the same as obtained from DHCP? Or did you use a different one outside of the DHCP range? __________________ There is no better previewing system than the 'Submit Reply' button. I <3 Aquatuning & Enermax long time!

11th Jun 2009, 20:25	#6
capnPedro Hacker. Maker. Engineer. Join Date: Apr 2007 Location: North-East England Posts: 4,381	Interesting... Try this at command prompt: ipconifg /release ipconfig /flushdns ipconfig /renew ipconfig /registerdns Sorry, I don't have a machine on my network configured via DHCP to test with, but I'm pretty sure that's the correct order to run the commands. If it then still doesn't work, try the old Right click on network connection -> Repair __________________ There is no better previewing system than the 'Submit Reply' button. I <3 Aquatuning & Enermax long time!

13th Jun 2009, 06:44	#8
sui_winbolo Computer Technician Join Date: Sep 2004 Location: There's no place like 127.0.0.1 Posts: 1,516	Feel free to correct me on this, I work better at resolving issues in person. But if it was a DNS issue, you should still be able to ping internally, correct? Because he couldn't ping internally, that leads me to believe that it's not a DNS problem. One thing that might be overlooked, have you tried updating to SP3? I'm not going to lie, it wouldn't be one of the first places I would look either. But, I would look considering SP1 is pretty outdated and it could simply be a problem with Windows, or a driver. Do you have a dedicated DHCP server or is a router acting as the DHCP? __________________ SUI-OMEGA :: Intel i5-2500K \| ASUS P8Z68-M Pro \| Corsair Vengeance LP 8GB RAM \| XFX 6870 1GB \| WD Black 1TB HDD \| Corsair Pro 650w PSU \| Lian-Li Mini Tower ::

bit-tech.net

Site Links

Our Other Sites

11th Jun 2009, 11:53	#3
SeT Hypermodder Join Date: Oct 2003 Location: Cincinnati Posts: 644	The IP, Subnet, and Gateway obtained from DHCP were correct.

11th Jun 2009, 19:38	#5
SeT Hypermodder Join Date: Oct 2003 Location: Cincinnati Posts: 644	It was a different IP but still in DHCP range.

13th Jun 2009, 05:56	#7
Pendarus What's a Dremel? Join Date: Jun 2007 Posts: 6	It sounds like a DNS registration problem. Try removing the computers entry manually from the DNS server. If it has the same name on the network as before it was re-imaged, you may find multiple entries with different IP's assigned. Reboot and run: "ipconfig /registerdns" This should solve your issue. Hope this helps.