WatchGuard Technologies SSL VPN Client Connections from a Windows Server, NTLM Authentication

Models: SSL VPN

1 198
Download 198 pages 26.5 Kb
Page 158
Image 158
Client Connections from a Windows Server 2003

Troubleshooting

Client Connections from a Windows Server 2003

If a connection to the Firebox SSL VPN Gateway is made from a Windows Server 2003 computer that is its own DNS server, local and public DNS resolution does not work. To fix this issue, configure the Win- dows Server 2003 network settings to point to a different DNS server.

NTLM Authentication

The Secure Access Client does not support NTLM authentication to proxy servers. Only Basic authentica- tion is supported for proxy servers.

WINS Entries

When the Secure Access Client is disconnected, WINS entries are not removed from the computer that is running the client.

Using Third-Party Client Software

If a user’s computer is running Secure Access Client, and also has a third-party VPN software application installed on the computer, and connections are not correctly crossing the Firebox SSL VPN Gateway, make sure the third-party application is disabled or turned off. When the third-party application is dis- abled or off, try the Firebox SSL VPN Gateway connection again.

148

Firebox SSL VPN Gateway

Page 158
Image 158
WatchGuard Technologies SSL VPN manual Client Connections from a Windows Server, NTLM Authentication, WINS Entries