• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 511
  • Last Modified:

Cannot ping (or map drive) to server on other network

Why is it when I ping the IP address below that I get the
following response:

>> Pinging 164.224.186.232 with 32 bytes of data:
>> 
>> Reply from 164.224.186.232: bytes=32 time<1ms TTL=128
>> Reply from 164.224.186.232: bytes=32 time=1ms TTL=128
>> Reply from 164.224.186.232: bytes=32 time<1ms TTL=128
>> Reply from 164.224.186.232: bytes=32 time<1ms TTL=128
>> 
>> Ping statistics for 164.224.186.232:
>>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>>     Minimum = 0ms, Maximum = 1ms, Average = 0ms


but when I ping it from another desktop I get this response:

>> Pinging 164.224.186.232 with 32 bytes of data:
>> 
>> Reply from 10.16.0.130: Destination net unreachable.
>> Reply from 10.16.0.130: Destination net unreachable.
>> Request timed out.
>> Reply from 10.16.0.130: Destination net unreachable.



The first ping statistics are when I ping the server from a laptop
thats on the same network as the server.  The 2nd ping statistics
are when I ping the server from a desktop that is not on the same
network.  What could be the reasons that I cannot ping (or map drives)
in the 2nd case?  

I am able to ping others servers that are on the same network as
164.224.186.232 from this desktop but cannot ping to this one successfully.
0
wesunivofmd
Asked:
wesunivofmd
  • 5
  • 2
  • 2
  • +8
1 Solution
 
Mad_JasperCommented:
Could it be possible that there is an access-list on a router that is preventing ICMP traffic from the particular server?
0
 
jli168Commented:
There might be something on your host file point to something else with 164.224.186.232. Check it out.

0
 
jli168Commented:
Also do a tracert from the desktop to 164.224.186.232 and see where it stop you.

tracert 164.224.186.232

0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Craig_200XCommented:
it looks like the route to 10.16.0.130 is saying unreachable which means it doesnt know how to get to that subnet.


there is no route to that subnet.
0
 
ChristianJKochCommented:
you are not routing to that network

if you do n ot have one, you will need to add some kind of router and place it in between the 2 networks and configure it to route between the 2

what does your setup look like?
0
 
mikeleebrlaCommented:
jli168,,, the host file has nothing to do with this since he is pinging by IP address.  the host file only comes into play if he was pinging by DNS name.
0
 
wesunivofmdAuthor Commented:
Craig 200x:
Doesn't the fact that I can ping and map drives to 3 other servers on the this network mean that this subnet is set up?  It's only 1 server (164.224.186.232 ) on this network that I cannot connect to.  The 3 other servers that I can connect to are on the same network as:
164.224.186.232.

ChristianJKock:
See above message to Craig 200x.

jli168:
Where is this host file located?

0
 
Craig_200XCommented:
im not saying its not setup. Im saying that the route is not known. If you do a traceroute, are both machines you are pinging from using the same gateway? do a traceroute, and where it times out is the gateway without the route.

the host file is "C:\WINDOWS\system32\drivers\etc"

if you have something in the host file (viewable/editable with notepad) you might me misdirecting the route.. so its not a bad idea to verify this is not the case.
0
 
ChristianJKochCommented:
you're sayng you can  ping the 3 other servers on 164 network..i see that

but the computer on the 10 network, you cannot ping, what is routing to that network?

is there any other computers on the 10 network? can you ping them?
0
 
pcchecksCommented:
what is the ip address of another one of the servers you can ping?
check your ip status and post them as well eg. ip address and default gateway
0
 
sarmarioCommented:
Check the default gateway against the other machines that work
also run "route print" from the command prompt (minus the " marks) on one of the machines that work and the one that doesn't - see if there is a persistant route shown
If there is you either need a gateway OR add a route so that the machine knows where to route the traffic bound for 164.224.186.232.

0
 
waqaswasibCommented:
The ICMP - Destination net unreachable message is one which a user would usually get from the gateway when it doesn't know how to get to a particular network.

chk if this machine is communicating with other pc
bye
0
 
Craig_200XCommented:
Bill,

being that we dont know for sure what the solutions was or is on this one I feel I was one of the ones who initially suggested to check routing here as this is what appears to be the prob.. can I request to be in on this split of points too?

Thanx
0
 
Bill_FleuryCommented:
Craig,

Your suggestions don't make sense to me.  The hosts file is for resolving hostnames, it has nothing to do with routing IP's.  I made the suggestion to accept the comments that appeared to be on the proper path to having this problem corrected.

However, I have absolutely no say in the final decision, I just post a recommendation.  I would suggest that you post to the Community Support section if you have an objection to my recommendation.

Thanks
0
 
Craig_200XCommented:
the host file response is simply that. wesunivofmd asked where it is...I tried pointing him in the direction of it... as for my opinion,  I made suggestions to check the routing in both of my responses. I feel that those are the same direction as the two experts you recommended get the split.. so I assumed you felt this was heading in that direction and possibly missed my comments. but if you feel i make no sense. that s fine. I will post in the community support section as you request for another opinion.
0
 
Bill_FleuryCommented:
Here is specifically why I did not think you were on the right track:

"you might me misdirecting the route.. so its not a bad idea to verify this is not the case."

You said this in reference to the hosts file, it does not have anything to do with routing.

"It looks like the route to 10.16.0.130 is saying unreachable"

The route to 10.16.0.130 is functioning absolutely fine- it is a router along the path to the 164.224.186.232 IP, and 10.16.0.130 is returning a result indicating it does not know the route to 164.224.186.232.

However, it's up to the mods.  I know it's not alot of points we're talking about here, and it's more of a matter of principal, and I respect your right to stand up and voice your concerns, and have faith the moderators will make a fair judgement.  It wouldn't be the first time my views are not the commonly accepted :)  Keep up the good work in the Exchange Craig, you're doing a heck of a good job and alot of people are getting great help from you.

0
 
Craig_200XCommented:
your right... he may be pinging by IP.. but if he wasnt.. anyway... I figured you never know.. and just in case...... but as you can see I also suggested this is definitely a routing prob. and we have to break that down to figure this one out.... just as the other two were suggesting.. your right.. not alot of points.. I guess ill go try and answer some other questions.... Thanx for understanding..

next time

Craig
0
 
GranModCommented:
PAQed with no points refunded (of 250)

GranMod
Community Support Moderator
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 5
  • 2
  • 2
  • +8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now