Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 8 subscribers
  • Views 9437 views
  • Users 0 members are here
Options
Suggested
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

UTM 9.402-7 SSL VPN users no longer able to browse network

MasonWebster

We have an SG-210 that I updated from 9.355-1 to 9.402-7, and now our SSL VPN users can no longer browse our network via IP address or computer name. The users are able to connect to the firewall and obtain an IP address, and there are no errors in the logs. Has something changed with how SSL VPN users are handled?

Any help would be appreciated; it's very important that our remote people can connect to our network shares.

Thanks.



This thread was automatically locked due to age.
Parents
  • 0

    We had the same issue when we upgraded to 9.402-7. Support advised me that this is a known issue. They are rolling out a fix in the next release. The issue has to do with the clients not receiving the correct route. They were to provide a workaround by editing the openvpn server config and adding the route to my LAN. Unfortunately it broke other profiles, but I am able to connect and browse the LAN. Hope this helps!

  • 0 in reply to DanielGalvan

    Ok, thanks. I got it working for one of the accounts that was on the VPN allow list twice, once from an AD group and then again by their specific username. Having the user on there twice didn't bother it before, but once I removed the user's name from the list, leaving only the AD group, and re-downloaded the  config file, it started working again.

Reply
  • 0 in reply to DanielGalvan

    Ok, thanks. I got it working for one of the accounts that was on the VPN allow list twice, once from an AD group and then again by their specific username. Having the user on there twice didn't bother it before, but once I removed the user's name from the list, leaving only the AD group, and re-downloaded the  config file, it started working again.

Children
No Data
Unfiltered HTML