Internet Connection Sharing Clients on Different Subnets Cannot Access Shares Using the Universal Naming Convention (261734)


The information in this article applies to:

  • Microsoft Windows Millennium Edition
This article was previously published under Q261734

SYMPTOMS

Internet Connection Sharing (ICS) clients that reside on two different subnets behind an ICS host that supports the two subnets cannot access files on each other's shares using the Universal Naming Convention (UNC).

CAUSE

This behavior occurs because clients, by default, do not use their Domain Name Service (DNS) domain as part of their NetBIOS lookup. Because it is not proper syntax to append this domain manually to a NetBIOS name (for example, \\client1.mshome.net), the only way clients can access each other's files is through an Internet Protocol (IP) address.

WORKAROUND

To work around this issue, configure NetBIOS to use the DNS resolver on the ICS server, so that clients on multiple subnets are able find each other by name. To do this, follow these steps:

  1. Right-click My Network Places and click Properties.
  2. Double-click TCP/IP. (If more than one TCP/IP configuration exists, you can click any one; this is a global setting.)
  3. Click the DNS Configuration tab.
  4. Click to select the DNS radio button.
  5. In the Host box, type computer name.
  6. In the Domain box, type mshome.net.
  7. Click OK to close the TCP/IP Properties window.
  8. Click OK and restart your computer.

This configuration only needs to be added to the client machines behind the ICS host.

MORE INFORMATION

The DNS cache that is created by ICS is stored in the registry and is modified as clients are added or if clients change subnets. All clients have access to this cache when they run a DNS query, but clients only find each other by name if they use the DNS server to resolve the name. If you are searching for the client using the ping command, the query is sent to the DNS server by default, and you are able to search for other clients.

By default, NetBIOS does not use DNS to resolve its names. ICS clients must check their cache, check the LMHOSTS file, and then broadcast to resolve a NetBIOS name. Usually, when the broadcasts do not resolve the name, the clients stop trying.

If clients have these registry keys enabled, after they attempt a broadcast, they should append their DNS suffix (mshome.net) onto the name they are trying to resolve and query their DNS server (the ICS computer). The name is then successfully resolved.
Modification Type:MinorLast Reviewed:1/14/2006
Keywords:kbprb KB261734
©2004 Microsoft Corporation. All rights reserved.