Cannot communicate with internal resources for 15 minutes with VPN client

Cannot communicate with internal resources for 15 minutes with VPN client
Cannot resolve DNS names with BorderManager VPN client
Cannot ping protected resources through VPN client

Apply latest VPN client from Jan. 2005 (will ship with BM38SP3.exe). As a worksaround, open a DOS box after connecting and execute the following shell commands

- net stop "DNS client"
- net start "DNS client"

The problem is that the DNS entries that the VPN client pushed to the WIndows registry are not getting read with the shell command that the VPN client executes (ipconfig /registerdns). The only application that does this is NSLOOKUP. To force the rereading of the registry settings that the VPN client pushes down, use the above shell scripts. The newer VPN client released just automates this process.
The fix is included on the vpn client version 3.8.15, included in BM38SP5 support pack and above.

Formerly known as TID# 10096383

This is still an issue with vpn client 3.8.13 if you are using a German Windows.

The English syntax for this command is:

net start "dns client"

While vpn client is installed on a German windows, the correct command is:

net start dns-client.

This is a bug in windows.
Engineering is working on a fix, changing the script to call net stop dnscache, which it is language independent. The fix is included on the vpn client version 3.8.15, included in BM38SP5 support pack and above.