Article ID: 176321 - Last Review: October 31, 2006 - Revision: 1.1 Unable to Resolve NetBIOS Names Through PPTP ConnectionThis article was previously published under Q176321 On This PageSYMPTOMS
If the Windows Internet Name Service (WINS) server is on the same computer
as the Point-to-Point Tunneling Protocol (PPTP) server, and you attempt to
connect to a computer using a PPTP client, either or both of the following
symptoms may occur:
CAUSE
This issue can occur if there is a host route added to the PPTP client
that routes all Internet Protocol (IP) traffic destined for the PPTP
server through your original dial-up connection to your Internet service
provider (ISP). This path may contain routers or firewalls that block User
Datagram Protocol (UDP) ports 137 or 138, or Transmission Control Protocol
(TCP) port 139. These ports must be open for NetBIOS traffic to pass.
RESOLUTION
To resolve this issue, use either of the following methods:
Method 1Use the NetBEUI protocol for your PPTP tunnel instead of, or in addition to, TCP/IP.Method 2Enable unicast traffic through UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP client and PPTP server.NOTE: If you use this method, your PPTP client and server may be susceptible to unwanted traffic from other hosts. Please ensure that you enable the proper permissions and rights to secure your computers. Method 3If the WINS server is on the same computer as the PPTP server, move the WINS server to a different computer.NOTE: If UDP ports 137 and 138 and TCP port 139 are not enabled, you may be able to resolve the NetBIOS name of the PPTP server, but you may be unable to connect to its resources. Method 4Create an additional IP interface on the PPTP server. To do so, use any of the following methods:
ARTICLE-ID: 133241 (http://support.microsoft.com/kb/133241/EN-US/ ) TITLE : Browsing Domain Master Browsers w/ Multiple NICs and Protocols ARTICLE-ID: 135404 (http://support.microsoft.com/kb/135404/EN-US/ ) TITLE : Multihomed Master Browser May Cause Event ID 8021 and 8032
| Article Translations
|
Back to the top
