This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RED is online but can't access device on the network

Hello,

We have a PBX inside the network 10.20.0.x and we need to access it from two other different networks (192.168.1.x and 172.14.0.x).

We have two RED15 devices, 192.168.1.1 and 172.14.0.1 so we can connect to the PBX on the 10.20.0.x. Both of them are configured the same way ():

--------------------------------------------------------------------

The situation is like this:

1) Both RED are online

2) I can access the PBX from 172.14.0.x

3) I can acces the network 10.0.0.x from 192.168.1.x

BUT

3) I can't access the PBX from 192.168.1.0

How can I debug this to find the problem? This was working the last week...

This thread was automatically locked due to age.

Top Replies

Victor Moleiro over 2 years ago in reply to emmosophos +3 verified

Problem solved! We could not access other devices on 10.20.0.x. The problem was with the NAT rule associated to the firewall rule, we had to add the Masq. For some reason stopped working...Anyways…

Parents

0 LHerzog over 2 years ago

If this was already working, please re-apply the RED Configs by saving them. We've had multiple issues where this was not working until doing so.

Do the Packet Capture in Web UI to see what is happening to the packets. Are they going to the correct interfaces? are they blocked?

quite useful for the first approach.
Cancel
Vote Up +2 Vote Down

Cancel
0 Victor Moleiro over 2 years ago in reply to LHerzog

I saved the settings to the re-apply, but the problem is still there.

With the Packet Capture we can see the following:

The In and Out interface are correct. Also the Rule ID is the expected one.

The only "strange" value i see is the Connection status = "UNREPLIED".

What does this exactly means?

Thanks!
Cancel
Vote Up 0 Vote Down

Cancel
0 emmosophos over 2 years ago in reply to Victor Moleiro

Hello Victor,

Adding to what LHerzog mentioned, make sure the RED network 192.168.1.x is added in the local networks of your PBX.

Is the PBX the only device on 10.20.0.x that you can't reach?

Regards,

Emmanuel (EmmoSophos)

Technical Team Lead, Global Community Support
Sophos Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 Victor Moleiro over 2 years ago in reply to emmosophos

Problem solved!

We could not access other devices on 10.20.0.x. The problem was with the NAT rule associated to the firewall rule, we had to add the Masq.

For some reason stopped working...Anyways, thanks for your time!
Cancel
Vote Up +3 Vote Down

Cancel
0 LHerzog over 2 years ago in reply to Victor Moleiro

Thanks for posting the solution. Good you figured it out!
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 LHerzog over 2 years ago in reply to Victor Moleiro

Thanks for posting the solution. Good you figured it out!
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data