Solved Some users cannot access FQDN

[Alphabetic]

Good Morning,

Yesterday I updated the FW on a sonicwall and reconfigured the rules as per 3CX guide to get the 3CX firewall test to pass.

I also upgraded to PBX to 16.0.8.9.

I am able to access the FQDN externally but internally the users are getting ERR_CONNECTION_REFUSED from Chrome and Edge.

When they ping the FQDN it comes back with the correct IP.

Some internal users are able to access it fine.

the IP is not blacklisted in the PBX.

Can access the webclient using internal IP

update: Cannot access another 3CX from this PC either.

 

[Alphabetic]

Figured out this is a FW issue going out on one IP and coming in on another. Once i've figured the rule out i'll be sorted.

 

[jcostlow]

If you want to access the Public IP internally you will need a loopback rule like here: https://www.sonicwall.com/support/k...sing-public-ips-loopback-nat/170505780814635/

If you have access to setup split DNS on the network that would be easier. We typically set up split DNS on the domain to avoid making loopback NAT policies.

 

[Alphabetic]

If you want to access the Public IP internally you will need a loopback rule like here: https://www.sonicwall.com/support/k...sing-public-ips-loopback-nat/170505780814635/

If you have access to setup split DNS on the network that would be easier. We typically set up split DNS on the domain to avoid making loopback NAT policies.

Hi mate

thanks for replying.

this is indeed what I needed - I had SW support sort it for me.

I already had the rule in place I just accidentally disabled it a few days ago

 

[jcostlow]

Glad you got it working.

We have all done that before.

 

[ChrisC_3CX]

I also think that ideally you would allow the FQDN to resolve to the local IP internally, nevertheless, glad to hear you got this resolved!