Nortel Networks NN46110-602 - Manual (Page 78)

78 Chapter 4 Troubleshooting
NN46110-602
Cannot access Web servers on the Internet after establishing a
VPN Client connection
Cause: For both PPTP and IPsec, this condition occurs as a result of all network
traffic passing through the corporate network. Typically, firewalls and other
security measures on the corporate network limit access to the Internet.
Action: The administrator can set up a default route on the VPN Router to
forward traffic to the Internet. If this default route is not configured, you must
disconnect the extranet connection to Web browse the Internet through your ISP
connection.
Alternatively, if you are using a proxy-based firewall, you must set the Web
browser to use the firewall to proxy for HTTP traffic when the tunnel connection
is in use.
Cannot access network shares after establishing an extranet
access connection
Cause: A Windows Internet Name Service (WINS) server is not configured for
PPTP or IPsec connections on the VPN Router.
Action: Validate that the VPN Client is configured with a WINS server. Follow
the steps outlined above under
"Problems with name resolution using DNS
services" to run ipconfig at a command prompt on Windows NT 4.0 or to run
winipcfg on Windows 95. Verify that a primary WINS server is listed under the
section for the adapter named IPsecShm on Windows NT 4.0, and on Windows 95
verify that a primary WINS server is listed in
winipcfg for the VPN Client
adapter. If there is no primary WINS server listed, notify the network
administrator that the VPN Router may not be properly configured.
Cause: Your system is set up for a different domain other than the one on the
remote network.
Action: Skip the initial domain login when Windows 95 starts and choose Log on
to the Remote Domain under the Options menu of the VPN Client dialog box.
You are then prompted to log in to the domain of the remote network after the
extranet connection is made. This is the recommended method for users with
docking station configurations.