Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 26 subscribers
  • Views 386 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

DHCP delivery failed for SSLVPN

Luiz Araújo 
There are a few users who have difficulty connecting to the SSLVPN client.

And after some checks I found that somehow it was being delivered, IP address by DHCP in duplicate.


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

    Hey Luiz,

    It's highly unlikely to happen as if the SSL VPN's DHCP pool runs out of IP addresses, it simply wouldn't allow more users to connect with an authentication failure error on the user's end.

    Could you be more specific about where did you notice this duplicate IP lease? Also confirm that under Current Activities > Live Users, Do you see more than one user with the same Leased IP address? 

  • 0 in reply to FormerMember

    Hello,

    So in case of quantity of addresses from SSLVPN DHCP Pool after having seen duplication. Before I had 60 available I increased it to 200. I still had a case of doubling.

    I noticed when a user called me. And SSLVPN shows connected, shows that it received the routes (route print on the notebook) and does not drip the addresses delivered by the routes. So I decided to connect to my notebook with my user and realized that I received the same address from her. And it was after this that I decided to increase the range.

    However, the error still occurs. As if the DHCP service registers an IP for a certain mac address, but if another device that has ever received that IP connects to the VPN it delivers to the new one and drops the old one. (I don't know if it considers the user to be idle, even so the option to disconnect in case of inactivity is disabled )

    And I've seen the case of the same set the IP received statically, the same if delivered in another notebook.

    Looking at the active users, the login which failed to ping but remains logged in appears with the given IP.