Article ID: 108738
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Advanced Server 3.1
- Microsoft LAN Manager 2.1 Standard Edition
This article was previously published under Q108738
SYMPTOMS
When you are using Remote Access Service (RAS) to call a computer that is not on a network (such as a computer at your home) from a networked computer (such as a computer at your office), you are unable to browse the non-networked computer for computer names and share names.
CAUSE
Browsing is automatically disabled in Windows NT if no network other than RAS is present. This behavior is based on the assumption that people will only call from the non-networked (home) computer to the networked (work) computer, and therefore have no need to browse the non-networked (home) computer.
RESOLUTION
To work around this problem, follow these steps:
- In Control Panel, double-click Network.
- On the Services tab, double-click Remote Access Service, click Network, and then click Configure.
- Click Entire Network, click OK, click OK, and then click Continue.
- Make sure the non-networked (home) computer is a member of the domain or workgroup of the network where it is called from.
- In the Network dialog box, click the Adapters tab, click Add, click MS Loopback Adapter, click OK, and then click OK.
-or-
Install an additional network card and driver (in addition to RAS).
NOTE: You now have a fake network and options in File Manager and other applications appear to be active and functional, but are not functional unless you are having a RAS session to another machine.
Additional query words: prodnt
Keywords: kbnetwork KB108738
