Remote Access to Windows NT Network.

Most of the time you will need to install a wins server on your NT network. Then use dhcp to pass that info to the dial-up computer or enter it manually. Or make sure you have the client computer workgroup name the same as the ras server workfroup or domain. You sould have full connectivity if you know the computer name you are looking for but browsing may not always work.

Browsing has its limitations and the PC maintains only one list to the workgroup/domain, where it belongs to. This doesn't change with Dial-Up Networking. If you logon to a NT domain named DOMAIN with a client which belongs to a workgroup named WORKGROUP, then the client will maintain the browser list for the WORKGROUP only. That might be one of the reasons why you don't see any computers on the network. I don't know much about Lotus Notes Clients, but I'm guessing that the client has the server name or IP address somewhere in its configuration and that is why it is able to find the server.
There are couple of things you can do to browse the remote network. On the client side ensure that the PC belongs to a workgroup named as the name of the remote domain. For example if the remote domain name is DOMAIN, then the client should belong to a workgroup named DOMAIN. As the previous poster mentioned, you could also add the WINS address, if you have any, to the LMHOST file.
On the server side, I like to insta

You forget to click "Allow remote clients to browse the network" in Ras applet in Network(in control panel)
Check if you are able to ping other computers through your client. If you cannot, you forget to click enable ip forwarding in TCP/IP properties.

Not only do the client pc's need to belong to the same workgroup, but the client pc must be logged in locally with the same user ID and Password that it will use on the remote server via RAS. Even though you may use a correct user ID and Pass with the dial up service to dial into the server and connect, it uses the remote PC's local account to authorize shares and network access, so it also must be the same as in the user manager on the server.

This may not solve your browsing problems entirely but the first thing I would do is try pinging the server or workstation. Easy enough.

The second, since I've had the same problems here on a LAN is to try mapping directly (in Windows Explorer -- Tools -> Map Network Drive) to a shared drive using UNC paths...

ie. \\SERVER\C$

I do this every day at work for servers that do not show up on my network neighborhood. The C$ is the hidden C Drive.

Good luck!

Rodney

Something else that you might look at is how you have the TCP/IP setup on the PC you are dialing up with. If you have a hard coded IP and subnet mask this might be keeping you from communicating properly with the remote network.

You Will need to configure a WINS server, so the remote machine will be able to browse the rest of the network. This URL will explain in more detail. http://www.helmig.com/j_helmig/rastcpip.htm

This works I have been running RAS this way for the last few years. You can also do this with DNS but, WINS is easier.

try using pcanywhere

This question was closed by the author