sphete
asked on
pinging server is unreachable
i've installed win2000 server and i've got 2 win2000 machines and 1 winXP machine, so when i ping the server using one of the clients it says the host is unreachable but when i try to ping client machine using one of the client it pings successfully
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also check the lmhosts file to make sure that you do not have an outdated file.
Are you pinging by name or IP address? if you can ping by ip address but not by name, you have a dns problem and need to configure it properly. If you cannot ping by ip address, then you either have a physical connectivity issue, or your subnet ip addresses are not configured properly as suggested by jFrederick29.
you did configure DNS on the W2k server, didn't you?
you did configure DNS on the W2k server, didn't you?
ASKER
all the client are using apipa and again i was ping by name and by ip, but i think i've got physical connectivity issue , but tell me where do i check imhost file?
it is located in the c:\winnt\system32\drivers\
you can open the lmhosts in word pad.....but if you can't ping by ip address there is definitely something going on at the physical layer........check your nic by pinging 127.0.0.1...the loopback address which will test your nic and it's configuration. If you get 4 good replies, it means your nic is working and is configured properly and the problem is somewhere downwire.
If you don't get four replies, check your tcpip properties and make sure the nic is properly bound......if it is, then the nic is probably bad. check that by substituting a known good nic.
If the nic is ok then you are into cable/hub/switch trouble. First try replacing the patch cable connected to the machine (make sure it is not a cross-over cable) also, try plugging that machine into a different port on your hub/switch......they will often go bad one port at a time. Finally if none of that works, you need to get a cable tester to check any in-wall cat5 runs.
If you don't get four replies, check your tcpip properties and make sure the nic is properly bound......if it is, then the nic is probably bad. check that by substituting a known good nic.
If the nic is ok then you are into cable/hub/switch trouble. First try replacing the patch cable connected to the machine (make sure it is not a cross-over cable) also, try plugging that machine into a different port on your hub/switch......they will often go bad one port at a time. Finally if none of that works, you need to get a cable tester to check any in-wall cat5 runs.
Spete,
Please explain how the problem was solved and why you accepted the answer you did.
Please explain how the problem was solved and why you accepted the answer you did.