Why Can't I Map a Network Drive Through a VPN?

• Cannot map a network drive through VPN
• Cannot log into NT domain
• Cannot map a drive to NT server
• Cannot log into Exchange server

Some upper layer protocols that ride over the IP layer, such as NetBIOS, require configuration beyond what the NetScreen device provides. This issue creates problems with mapping network drives. The following items are typical areas at fault when configuring VPNs and Microsoft Domain logins:

 

• The NetScreen-Remote client needs to have a WINS server defined in the IP settings of the interface. That WINS server needs to be active and reachable through the VPN tunnel. Running a ping to the name of a host or its IP address in the trusted LAN can test the WINS server. If the WINS server is functioning properly, the ping should be successful.
• The client PC must be added to the domain like any other client, typically by an administrator.
• If this is an NT PC, the Windows login type should be configured such that they will log in into the domain. If this is WIN98 PC, then the login to the network is either cached by Windows or happens when the user tries to attach to a share, at which time they will get a login prompt.
• The client needs to be configured to be on the correct domain in its Microsoft network settings.

 

This will only work with Microsoft Domains, not Workgroups. Since the VPN acts like a route, Workgroup browsing is not possible. Workgroups are broadcast domains and they do not traverse routes; and a VPN connection is a routed connection. For more information on mapping a drive, go to www.microsoft.com.

Troubleshooting