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
spheteAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JFrederick29Commented:
From a command prompt, type ipconfig /all and verify that all your machines have valid IP addresses and the same subnet mask.  All machines are on the same local subnet right? no routers in between?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ewtaylorCommented:
Also check the lmhosts file to make sure that you do not have an outdated file.
0
JConchieCommented:
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?
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

spheteAuthor Commented:
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?

0
ewtaylorCommented:
it is located in the c:\winnt\system32\drivers\etc
0
JConchieCommented:
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.
0
JConchieCommented:
Spete,
Please explain how the problem was solved and why you accepted the answer you did.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.