Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
RAS question
- Thread starter unit512
- Start date
In NT 4.0 once you are authenticated, double click on Network Neighborhood. You should see the devices on your domain...??? (true for win95,98,NT Workstation 4.0)<br>
<br>
**If not, check to make sure you are logged in, and you have the proper rights...<br>
<br>
**Also, if you are still having problems, go back and make sure the protocol(s) for RAS are set up properly (TCP/IP,IPX.SPX)....<br>
Hope this helps!~
<br>
**If not, check to make sure you are logged in, and you have the proper rights...<br>
<br>
**Also, if you are still having problems, go back and make sure the protocol(s) for RAS are set up properly (TCP/IP,IPX.SPX)....<br>
Hope this helps!~
- Thread starter
- #7
RoadRunner
Vendor
I agree with Silencer(MIS) <br>
<br>
How do you browse computers on a remote network using a TCP/IP RAS connection? <br>
<br>
By default, a Windows NT RAS/DUN (Dial-up) client will browse a remote network only if the client belongs to the workgroup or domain of the remote network. The workgroup or domain name for the Dial-up client computer should be the same as the workgroup or domain name of the RAS server to which it is connecting. <br>
<br>
On the remote network computer, install and configure the WINS service.<br>
<br>
Network Neighborhood is a NetBIOS API which requires Name Resoulution to work. WINS is your answer. You will need<br>
to install and configure the WINS services. NOTE: For a computer on the remote network to appear on the browse list on the RAS client, it must be registered with the WINS server.<br>
<br>
To get access to the Server even though it does not show up in Network Neighborhood, you must use NetBIOS commmands --<br>
such as NET USE, NET VIEW (Computer) etc.<br>
<br>
Why Use WINS? <br>
There are two primary advantages to using the WINS service. First, before two NetBIOS-based hosts can communicate over a TCP/IP network, the NetBIOS names must be resolved to IP addresses. To resolve NetBIOS names without a WINS server, TCP/IP must rely on broadcast traffic. This extra broadcast traffic can cause network congestion. With a WINS server online, when a computer wants to communicate with another computer, a name query is sent directly to the WINS server. The WINS server returns the destination computer's IP address to the original computer without the need for broadcast traffic. <br>
<br>
The second reason for using WINS is that it's dynamic. As computers attach to and detach from the network, the WINS databases are updated automatically. This means that you don't have to create a static LMHOST file that the computers can read to determine IP addresses. <br>
<br>
<br>
BB
<br>
How do you browse computers on a remote network using a TCP/IP RAS connection? <br>
<br>
By default, a Windows NT RAS/DUN (Dial-up) client will browse a remote network only if the client belongs to the workgroup or domain of the remote network. The workgroup or domain name for the Dial-up client computer should be the same as the workgroup or domain name of the RAS server to which it is connecting. <br>
<br>
On the remote network computer, install and configure the WINS service.<br>
<br>
Network Neighborhood is a NetBIOS API which requires Name Resoulution to work. WINS is your answer. You will need<br>
to install and configure the WINS services. NOTE: For a computer on the remote network to appear on the browse list on the RAS client, it must be registered with the WINS server.<br>
<br>
To get access to the Server even though it does not show up in Network Neighborhood, you must use NetBIOS commmands --<br>
such as NET USE, NET VIEW (Computer) etc.<br>
<br>
Why Use WINS? <br>
There are two primary advantages to using the WINS service. First, before two NetBIOS-based hosts can communicate over a TCP/IP network, the NetBIOS names must be resolved to IP addresses. To resolve NetBIOS names without a WINS server, TCP/IP must rely on broadcast traffic. This extra broadcast traffic can cause network congestion. With a WINS server online, when a computer wants to communicate with another computer, a name query is sent directly to the WINS server. The WINS server returns the destination computer's IP address to the original computer without the need for broadcast traffic. <br>
<br>
The second reason for using WINS is that it's dynamic. As computers attach to and detach from the network, the WINS databases are updated automatically. This means that you don't have to create a static LMHOST file that the computers can read to determine IP addresses. <br>
<br>
<br>
BB
- Thread starter
- #9
RoadRunner explained well!<br>
<br>
In addition, to resolve NetBIOS names without using WINS, the requesting computer broadcasts on the local network asking the destination to answer. The broadcast traffic usually does not go accross routers, therefore, without WINS, you usually can not get a TCP/IP client at another subnet to answer the request.<br>
<br>
Silencer
<br>
In addition, to resolve NetBIOS names without using WINS, the requesting computer broadcasts on the local network asking the destination to answer. The broadcast traffic usually does not go accross routers, therefore, without WINS, you usually can not get a TCP/IP client at another subnet to answer the request.<br>
<br>
Silencer
- Status
Similar threads
- Locked
- Question