Solved Failing to ping FQDN from other machines on the same network.

[willardc]

Hello team

I need you help, I have a new installation and the idea is to have users work remotely. But my challenge is that I can only ping the FQDN on the same machine as the 3CX Phone system. I am not able to ping the FQDN from any other machine on the same network. Hence clients on mobile devices are failing to scan the QR Code giving an error server not found. Anyone to assist please

 

[cobaltit]

A little more info on your setup is needed, as well as what constitutes failing to ping. Is resolution failing or just ping response? Custom FQDN or 3CX FQDN? Are you pinging from the mobile devices or pinging from a PC that is possibly on a different network?

 

[willardc]

Hi Cobaltit

Thank you for the reply. Please find my responses below

1. Both ping and resolving are failing
2. It is a 3XC FQDN
3. I am pinging from my laptop connected on the same network. I only have one link for internet.

 

[NickD_3CX]

Pinging your FQDN from the Server you have installed 3CX on will always succeed, because the FQDN is placed in the "hosts" file and pointed to 127.0.0.1.

When you try to ping from your laptop, do you see something like the following?

Pinging myfqdn.3cx.com [w.x.y.z] with 32 bytes of data:
Reply from w.x.y.z: bytes=32 time=54ms TTL=58
Reply from w.x.y.z: bytes=32 time=53ms TTL=58

 

[Alphabetic]

Is your 3CX in a Windows machine?

if so, it is possible that the firewall is blocking ICMP requests.

If you perform a ping test, is it at least returning the correct IP?

If you ping the IP does it ping?

 

[willardc]

Pinging your FQDN from the Server you have installed 3CX on will always succeed, because the FQDN is placed in the "hosts" file and pointed to 127.0.0.1.

When you try to ping from your laptop, do you see something like the following?

Pinging myfqdn.3cx.com [w.x.y.z] with 32 bytes of data:
Reply from w.x.y.z: bytes=32 time=54ms TTL=58
Reply from w.x.y.z: bytes=32 time=53ms TTL=58

Hi NickD

Thanks for responding. If I ping the FQDN direct from the windows machine (PC DESKTOP) where the 3CX system is installed the pings are successfull. But On the same network I can not ping this FQDN I am getting an error request time out.

 

[NickD_3CX]

But On the same network I can not ping this FQDN I am getting an error request time out.

Ok, but in the ping, does the FQDN resolve?

You are seeing something like this?
Pinging myfqdn.3cx.com [w.x.y.z] with 32 bytes of data:

Is "w.x.y.z" the correct IP?

 

[willardc]

Is your 3CX in a Windows machine?

if so, it is possible that the firewall is blocking ICMP requests.

If you perform a ping test, is it at least returning the correct IP?

If you ping the IP does it ping?

Hi

Thank you for responding

Is your 3CX in a Windows machine? Yes it is a windows desktop

if so, it is possible that the firewall is blocking ICMP requests.

If you perform a ping test, is it at least returning the correct IP?

If you ping the IP does it ping?

Pinging your FQDN from the Server you have installed 3CX on will always succeed, because the FQDN is placed in the "hosts" file and pointed to 127.0.0.1.

When you try to ping from your laptop, do you see something like the following?

Pinging myfqdn.3cx.com [w.x.y.z] with 32 bytes of data:
Reply from w.x.y.z: bytes=32 time=54ms TTL=58
Reply from w.x.y.z: bytes=32 time=53ms TTL=58

Hi

Thank you very much for the assistance, my problem was resolved. I figured out that on my laptop sometime ago I had installed the 3cx System before moving it to the desktop hence the laptop had the same 172.0.0.1 IP resolving to the same FQDN resulting in a conflict. Also issue of firmware update cleared the issue of IOS devices now i can scan the QR Code from anywhere. Many thanks

 

[NickD_3CX]

Lesson learnt, when you ping, always check what IP is being pinged!

Glad to hear the issue is resolved.