Solved

cannot ping beyond the LAN

Posted on 2013-02-01
14
304 Views
Last Modified: 2013-02-17
I have an interesting issue where the remote site (PC1) cannot ping the PBX. But it can ping anything else. Any thoughts?
                                                                      R3
                                                                       |
PC1<-->FW1<-->R1<--mpls-->R2<-->FW2<-->switch1<-->switch2<-->pbx (10.10.10.10/24)

All the devices on the left of FW2 can ping everything in subnet 10.10.10.0/24 except the pbx.

switch1, R3, and the PBX have the default gateway (DG) as the FW (10.10.10.1)
switch2 DG is R3 (10.10.10.3)
0
Comment
Question by:biggynet
  • 6
  • 3
  • 3
  • +1
14 Comments
 
LVL 82

Expert Comment

by:Dave Baldwin
Comment Utility
Is ping enabled on the PBX?  It doesn't have to be.
0
 

Author Comment

by:biggynet
Comment Utility
I forgot to mention that I can ping the pbx from FW2, R3, switch1, and switch2.
0
 
LVL 82

Expert Comment

by:Dave Baldwin
Comment Utility
Then check FW2 and R2 to see if either of them has ping turned off for incoming requests.  Which of those things can you ping from PC1?
0
 

Author Comment

by:biggynet
Comment Utility
No ping restriction on all devices. PC1 can ping everything, including R2, FW2, switch1, switch2, and R3. But cannot ping the PBX.
FW2, R3, switch1, and switch2 can ping the PBX.
0
 
LVL 82

Expert Comment

by:Dave Baldwin
Comment Utility
Maybe too many hops.  This sounds like an inconvenience rather than a problem.  Is there anything else that isn't working?  After all, ping doesn't do anything else and is one of the lowest priority services.  One of the reasons ping is sometimes inconsistent is because it will be dropped in favor of almost all other traffic.
0
 
LVL 17

Expert Comment

by:pergr
Comment Utility
Seems to me that the pbx has the wrong default gateway configured, or has several gateways configured.

Please double check it.
0
 

Author Comment

by:biggynet
Comment Utility
Sure. But for me when ping does not work then accessing the application will not work and this is the case here. I cannot access the PBX gui interface.

Like I mention earlier, the dg for the pbx is the FW.
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 57

Expert Comment

by:giltjr
Comment Utility
Is it specifically PC1 that can't ping the PBX or is it everything on the "left" of FW1 that can't ping?

Is PC1 on a subnet that is also on FW1?  If so can you try and ping the PBX from FW1 using the source address it is on the subnet PC1 is on?

What type of firewall is FW1?  Can you do a packet capture on it to see if the response to the ping is making it back to FW1?

Hopefully all devices between PC1 and PBX are managed and have the ability to packet captures.  You will need to do a packet capture at each spot to see where the response is being dropped.
0
 

Author Comment

by:biggynet
Comment Utility
PC1 and everything else beyond FW2 cannot ping the PBX. But can ping everything else in the subnet where the PBX is.
Traceroute from PC1 to the PBX failed at FW2.
FW is the Fortigate. Yes it can capture the packet . But the traceroute shows that it failed at FW2. I think packet captured at FW2 will be my next step.
0
 
LVL 17

Expert Comment

by:pergr
Comment Utility
If the PBX does not have the wrong default gateway, it has the wrong subnet mask.
0
 
LVL 57

Expert Comment

by:giltjr
Comment Utility
I would double check the rules/filters on FW2.  Make sure you check the subnet masks in the rules/filters.
0
 
LVL 17

Expert Comment

by:pergr
Comment Utility
Perhaps the pbx needs a reboot, after changing network settings.
0
 

Accepted Solution

by:
biggynet earned 0 total points
Comment Utility
The problem was not the fw but it is from the PBX. The PBX need static routes configured so that the echo reply can have it route back to the source.
0
 

Author Closing Comment

by:biggynet
Comment Utility
The problem was the pbx
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Join & Write a Comment

Network ports are the threads that hold network communication together. They are an essential part of networking that can be easily ignore or misunderstood, my goals is to show those who don't have a strong network foundation how network ports opera…
Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now