This PC will not ping the server when I plug in the network cable "Destination Host Unreachable".

I have installed several other PCs on this network, just plugged in the network cable and then they just ping the server straight off from the command prompt. Network connectivity is then only a matter of typing in a user name, password and domain. Always very easy.

When I click properties for the network controller it reports bytes being sent but non received.

It is not the cable or the network as I can plug this cable into any other PC with no problems whatsoever.

The PC does recognise the cable being plugged in and will ping in "loopback" mode.

There are no hardware conflicts listed.

Any help appreciated. I would love to just open the case and install another network card it would be much quicker, but there is a warranty seal on the case!

Normally with a new machine I just plug in the network cable and run the XP wizard and put in the user name, password and domain and away you go. This is turning into a real faff. Phone 'support' takes forever as "2nd in the queue".

 

type ipconfig and post the results up

 

Is the network card configured with TCP/IP in DHCP mode or are you using a static IP address?

Go to a command prompt and type ipconfig /all

Compare this to another PC. The IP Address and Subnet Mask are the important bits for local machines. Gateway's are only important when connecting to a computer on another network.

Stefan

 

I'll check tomorrow thanks. I did ipconfig already but didn't note it all down. But it did have an IP address that was completely different to the rest of the network.

 

defaultroute is wrong at a guess.

Steve

 

If the IP address starts 169.254.x.x, it's using APIPA. This usually means the PC can't find a DHCP server and Windows has assigned it's self an address. Check the cable, link lights etc.

 

The Subnet Mask determines the network and host addresses from an IP address.

For example, say the IP address is 192.168.0.15 and the Subnet Mask is 255.255.255.0

The first 3 numbers in the mask set the network address as 192.168.0 This must be the same on any other devices on that local segment of the network. The last number (15 in this example) would define the unique host number.

So, if you were to add other devices to the network, then it would have an IP address of 192.168.0.x (x would be different on each host - between 1 & 254). The subnet mask must be the same as the others and set to 255.255.255.0

The default gateway only plays a part when the devices you are trying to ping do not exist on the same local network segment.

e.g. say I have 192.168.0.15 (subnet 255.255.255.0) and I try to ping 10.0.0.20 (subnet 255.0.0.0), then I need to use a gateway to connect these two network addresses. This would need a default gateway on the PC's to tell them how to get to the different network.

As Chris has mentioned, if the PC is configure to use a DHCP server (this dynamically assigns IP addresses to devices that request them) and it can't find the server it will default to the APIPA (Automatic Private IP Addressing) scheme.

BTW, when an network card is installed in a PC it will default to use DHCP on the TCP/IP protocol.

Stefan

 

It did say it was using Automatic Private IP addressing and it did start with 169.254

But the cable is fine as I can plug it into another PC with no issues. Same in another room where a computer is connected and working. Plugging this one in and it does the same (ie doesn't work and does APIP 169.254.x.x).

How to proceed now? Do I set the IP address manually?

Thanks for the help!

 

Do you know if there's a server running DHCP on your network? Either your don't, it's stopped responding or their's a problem with TCP/IP on the new PC.

Whatever the reason, I'd set a static address and see if that works. Then you can either leave it like that or find out why DHCP isn't working (assuming you have a DHCP server or can be bothered with the hassle).

Check how the other PC's are configured and that will determine what IP network address & subnet you need to use and what host numbers are already in use.

Stefan

 

Thanks Ozzy, I'll have another play tomorrow in between healing the sick

 

LOL

Have you got the whole "walking on water" down to a fine art yet

Anway, I thought most NHS patients just want some antibiotics for every cough or sniffle

Stefan

 

No comment

 

All working now, just gave it an IP address. Thanks. I think someone came in when NHS Net was setup and turned DHCP off, but I had forgotten.

 

Glad to hear it's sorted

Stefan