General discussion

Locked

Remote Access to Windows NT Network.

By VJanssens ·
How do I have to configure my Windows NT RAS Server, and/or my client computer to be able to browse the remote network using Dial-Up Networking? I am using TCP/IP as the only protocol on both computers. When I connect using Dial-Up networking to my RAS Server I do not see any computers on the network. What i find strange is that my Lotus Notes Client is able to find an to communicate with it's server.
Thanks a lot,
Vincent

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Remote Access to Windows NT Network.

by rcarlino In reply to Remote Access to Windows ...

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.

Collapse -

Remote Access to Windows NT Network.

by VJanssens In reply to Remote Access to Windows ...

Browsing should normally work if on your RAS server you type the IP address of the WINS server in the network properties.

Collapse -

Remote Access to Windows NT Network.

by otto3 In reply to Remote Access to Windows ...

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

Collapse -

Remote Access to Windows NT Network.

by VJanssens In reply to Remote Access to Windows ...

Poster rated this answer

Collapse -

Remote Access to Windows NT Network.

by nitin In reply to Remote Access to Windows ...

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.

Collapse -

Remote Access to Windows NT Network.

by VJanssens In reply to Remote Access to Windows ...

Poster rated this answer

Collapse -

Remote Access to Windows NT Network.

by steve.smith In reply to Remote Access to Windows ...

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.

Collapse -

Remote Access to Windows NT Network.

by VJanssens In reply to Remote Access to Windows ...

Poster rated this answer

Collapse -

Remote Access to Windows NT Network.

by ccs In reply to Remote Access to Windows ...

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

Collapse -

Remote Access to Windows NT Network.

by VJanssens In reply to Remote Access to Windows ...

Poster rated this answer

Back to Desktop Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Hardware Forums