Avaya VPN Client - Failed to modify route table for VPN connectivity

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • laganm
    Member
    • May 2014
    • 3

    Avaya VPN Client - Failed to modify route table for VPN connectivity

    Hi

    I have a single user receiving a connection error when trying to connect t our AVG 3050 using the Avaya VPN Client in SSL mode. The error is "[SSLC] -E-Failed to modify route table for VPN connectivity." I have asked the user to disable all firewalls however they are still not able to establish a connection. Any ideas what else I can check for as I have several others using the same 10.06.500 client with no issues.

    Thanks,
    Michael
  • rshaynes
    Whiz
    .
    • Mar 2010
    • 27

    #2
    The full debug enabled logs from the VPN Client would be necessary to source what route table manipulation(s) are failing.

    The user may have, for example, a local network IP schema that conflicts with one or more splitnet subnets you may be pushing down the tunnel.

    As you guessed third party firewalls can also impact our ability to manipulate the system route table. Symantec EndPoint or CheckPoint VPN have been observed to continue to effect policies even after being "disabled". A full uninstall would be required.

    However prior to taking this route, review the VPN Client logs for additional signs of errors or failures specific to route table manipulation.

    -Robert

    Comment

    • laganm
      Member
      • May 2014
      • 3

      #3
      Hi Robert

      Thanks for your information. The issue was indeed the users Internet Security software, namely Kaspersky Internet Security. Even after disabling the firewall and all of the other software components the connection was still being blocked. The issue was in the Network Port monitoring system which was monitoring and blocking port 443(SSL). Just thought I'd post this in case anyone else has a similar issue.

      Thanks,

      Michael

      Comment

      Loading