RAS Client Registers with WINS Using RAS Server's IP Address (176991)
The information in this article applies to:
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows for Workgroups 3.11
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11a
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11b
- Microsoft Windows 95
This article was previously published under Q176991 SYMPTOMS
When you view the Windows Internet Name Service (WINS) mappings in WINS
Manager, your Remote Access Service (RAS) Clients are registered with the
IP address of your RAS Server's network interface card (NIC).
You may expect the RAS Clients to register with the WINS Server using
their RAS-assigned IP addresses instead.
CAUSE
The RAS Client is configured with one of the following: - The TCP/IP protocol and either NetBEUI or NWLink IPX/SPX Compatible
Transport protocol.
-or-
- NetBEUI or NWLink IPX/SPX Compatible Transport protocol without the
TCP/IP protocol.
RESOLUTION
Use one of the following methods to force your RAS Clients to register in
WINS using their RAS IP addresses: - Configure your RAS Clients to use only the TCP/IP protocol.
-or-
- Configure your RAS Server to accept connections using only the TCP/IP
protocol.
MORE INFORMATION
This issue is a function of the NetBIOS Gateway portion of the RAS Server.
It allows RAS Clients to communicate with non-IP or IP-only Local Area
Network (LAN) clients.
Modification Type: | Major | Last Reviewed: | 12/5/2003 |
---|
Keywords: | kbinfo kbinterop kbnetwork KB176991 |
---|
|