Can't ping an ip address from a different subnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 06:03 AM - edited 03-04-2019 08:04 AM
Hi All,
I'm having a problem accessing one particular ip address from different subnets over VPNs. Everything on the network is viewable except this one machine (which runs linux). I can ping it from the local subnet and it replies without exception. I can ping everything else on the network from two different subnets through two different routers and firewalls but I still can't access this one machine. I was wondering if anyone had any ideas?
Regards
Egg
- Labels:
-
Routing Protocols
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 06:45 AM
Wrong mask or gateway configured on host
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 07:45 AM
Damn,
I checked it once, while the engineer was there working on it and I didn't see anything out of place. The ip address and mask were definately correct but you've got me wondering about the gateway now, but I'm pretty sure it was ok. Problem is, it's a massive great steel plasma cutting machine for making bridges that you've got to shut down and restart to get to the config, and I dunno if I can remember how to do it. But I'll have a go. Any other ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 07:51 AM
Not off the top of my head, but similar cases I've seen have always been invalid gateways. Let me know how it works out for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 12:06 PM
do a self ping and see any odd route table by using the command route print / print route
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2010 02:18 PM
Sounds like a pretty important machine. Maybe there's an acl that's blocking icmp traffic to the machine? Try debugging icmp traffic to that machine - if you have access to the machine's first hop router you can run the debugs there and then send traffic. Normally when I try to single out a problemw w/ one device I'll run 'debu ip packet detail "acl" ' to keep from killing my router:
access-list 185 permit tcp host A host B
access-list 185 permit tcp host B host A
debug ip packet detail 185
