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

Sophos ZTNA issue

Hi, we have an issue with a resource published throguh ZTNA.

Is an old filserver running on win server 2003 sp2, we created resource on the right gateway (CIFS on port 445), we start connection through ZTNA all is working fine but user cannot authenticate (all other resources are working properly, user can auth when is on office)

There is something in ZTNA which block old resources or so?

Any suggestion?

This thread was automatically locked due to age.

Top Replies

LuCar Toni over 1 year ago +1

Essentially you need to check, what Authentication does not work: If you get an Auth Error by your CIFS, it is an issue related by your ressource. ZTNA offers you a secure tunnel, but not adjust the ressource…

0 LuCar Toni over 1 year ago

Essentially you need to check, what Authentication does not work: If you get an Auth Error by your CIFS, it is an issue related by your ressource. ZTNA offers you a secure tunnel, but not adjust the ressource traffic. So the client to server communication is 100% the same like you are connected directly to the server.

__________________________________________________________________________________________________________________
Cancel
Vote Up +1 Vote Down

Cancel
0 Nicola Tassinari over 1 year ago in reply to LuCar Toni

So ZTNA havent any problem even with old protocol (as SMB 1.0) ? is just a auth issue
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 1 year ago in reply to Nicola Tassinari

Essentially - ZTNA does not care what you are doing inside of the tunnel.

You will open a secure connection on Port 445. Then you can do what ever you want there.

If you get an Auth Error, this could be multiple reason. Your client does not support the old protocol anymore etc.

One ZTNA related issue: As you are using a DNS instead of a IP, some apps have a problem with that. This means: You are doing server.local instead of 192.168.1.1, which could (maybe) break an app.

__________________________________________________________________________________________________________________
Cancel
Vote Up 0 Vote Down

Cancel
0 Marco Dal Cin over 1 year ago in reply to LuCar Toni

Hi, I think SMB 1.0 does not use 445 but 139 ecc

https://4sysops.com/archives/smb-port-number-ports-445-139-138-and-137-explained/

Maybe the problem is this
Cancel
Vote Up +1 Vote Down

Cancel