Solved

cannot ping beyond the LAN

Posted on 2013-02-01
14
312 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
  • 3
  • +1
14 Comments
 
LVL 83

Expert Comment

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

Author Comment

by:biggynet
ID: 38846064
I forgot to mention that I can ping the pbx from FW2, R3, switch1, and switch2.
0
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 38846069
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
Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

 

Author Comment

by:biggynet
ID: 38846081
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 83

Expert Comment

by:Dave Baldwin
ID: 38846105
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
ID: 38846288
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
ID: 38846642
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
 
LVL 57

Expert Comment

by:giltjr
ID: 38846724
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
ID: 38847432
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
ID: 38847440
If the PBX does not have the wrong default gateway, it has the wrong subnet mask.
0
 
LVL 57

Expert Comment

by:giltjr
ID: 38847760
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
ID: 38848017
Perhaps the pbx needs a reboot, after changing network settings.
0
 

Accepted Solution

by:
biggynet earned 0 total points
ID: 38848773
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
ID: 38898333
The problem was the pbx
0

Featured Post

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Bandwidth cap???? 8 57
Monitoring solutions 8 71
Reset HP V1905-24-PoE switch to factory default settings 2 39
ESXi vmnic Stand By Status 3 52
#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…
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…

740 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