Filter
Top Products
Open Caveats
52
Release Notes for VPN Client, Release 4.0 through Release 4.0.5.D
OL-5450-10
0.0.0.0 255.255.255.255 n.n.n.n n.n.n.n 1
Where n.n.n.n is the IP address assigned to the VPN.
Workaround:
This is due to a misconfiguration on the VPN3000 at the central site. Make
sure that the Group | Client Config settings for Split Tunneling Policy are
correct. If the group is set to “Only tunnel networks in the list” and the Split
Tunneling Network List is the predefined “VPN CLient Local LAN” list this
problem will occur.
If split tunneling is the desired result, change the Split Tunneling Network
List to an appropriate list, otherwise make sure that the Split Tunneling Policy
is set to “Tunnel Everything” and check “Allow the networks in the list to
bypass the tunnel”. This allows for proper Local LAN function.
• CSCea03597
When the VPN Client is installed and Start before Logon is configured,
logging into an Active Directory Domain might take a long time, with or
without a VPN connection.
This issue occurs under the following conditions:
–
The VPN Client is installed on Windows 2000 or Windows XP
Professional.
–
You have enabled “Start before Logon” in the VPN Client.
–
You are logging in to a Windows Active Directory domain (not an NT 4
Domain).
Workaround:
This problem occurs because of a fix that was added for CSCdu20804. This
fix adds the following parameter to the registry every time Start before Logon
is enabled:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetL
ogon\Parameters
ExpectedDialupDelay
Removing “ExpectedDialupDelay” from the registry (then rebooting) should
fix the problem with slow logons to an Active Directory Domain.