Hardware

Ask something
Discussion Locked

Communication Problem

0 helpful
5 replies

by engr

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a machine that is connected to a hub. that hub is connected to the network gateway. I have redirected the connection so that the computer is connected directly to the gateway. but i think there is something wrong. [ when i ping from that pc to any other machine or even to the gateway i get one or two request time out ( out of the four ping packets). or i get Destination Unreachable message. When i ping from other PC to that PC i get request time out (all four packets) which means it isunreachable.
1. Do you think the cable is the cause of the problem..? (i am using Cat 5 patch cable)
2. Do think i shoud restart the router or something..?

5 replies

by jimbb

You're using an excellent tool to determine the root cause of your problem: ping. Ping to anything along your path, from close (router, gateway) to far away.
But it seems you get replies anyway, indicating your IP config is OK everywhere. And if you ping from somewhere else, only your PC is not responding properly, am I correct?

One more thing, try using tracert too, to check your ping is following the correct path.
Syntax: tracert ip_address (can it be more simple ;-)?)

If that too shows that your ping is following the correct route (gateway-other gateway-other PC),then only two things can be wrong: either the NIC in that PC, or the cable connecting that NIC to the LAN. The cable is the quickest thing to try out, but to be sureyou should swap the NIC too.

Jim

by estebandelatorre

Your machines ip address and the ip of the gateway should be in the same Network. In order to use th gateway, under tcp/ip configuration of your pc's, change machine's ip defalut gateway to mach the ip address of the gateway.
The ping should be 100% (they are in the same network). Some problems arrives when the packets is bouncing from router to router and then reach the machine that is close to you.
Use tracet.exe to see the route that the packet do in order to reach the destination, and see wHERE the ping fails.

Hope it helps.

This discussion is closed to new replies.