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

This NAT rule completely breaks SMB file sharing ...

I have the following LAN setup on bridged ports on my UTM:

So far so good, then I added a 2nd IP to my LAN so that I can access a device using that subnet (when this device is reset it goes to that IP):

Now comes the weird part, I've added a NAT rule so from 192.168.5.x subnet I can access 192.168.50.x:

And when this rule is enabled, it completely breaks SMB file sharing on 192.168.5.x network ...

Any ideas, how I can achieve what I need and replace this rule with something that would work ?



This thread was automatically locked due to age.
Parents
  • I don't see the logic behind the masquerading rule.   A simple firewall rule should be all you need and maybe disabling the firewall on the device in .50.x.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • You're right, the NAT rule isn't needed and it still works without it,
    however I still wonder why it's causing file sharing issues, and network discover issues ...

Reply Children
No Data