Windows Forum

Ask something
Discussion Locked

dial-up connection into NT network

0 helpful
10 replies

by dsv920 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have an Exchange Server which has Remote Access Services installed on it. We have remote clients that are dialing into the Exchange Server to reach our network and gain access to other resources on it, such as shared files and databases. Each of these clients have the proper permissions for dial-in, but when they connect, they can't see past the Exchange Server. They can't view any of the workstations on the network. The particular client is using Win2000 prof. Please advise on a solution or help me with this. Thanks in advance.

10 replies

by integrity

First, have you tried using a lmhosts file on the client pointing to your server?

Second, has RAS been configured to allow incoming connections to enter the network and not just locally to the RAS server?

Third, has anyone else got dial rightsto the network?

If this is the first person that attempted to dial in for network resources then I suggest you first ping servers by name and then by IP, if you get a responce by IP and not by name then you have a names resolution problem which can be solved by using either your lmhosts file or by WINS running on your RAS server.
Also try to avoid roaming profiles and browsing the network through network neighbourhood if using a slow connection as this will take up needless bandwidth, instead always try to use locally stored profiles and use UNC paths to conect to the resource that you require.

Is this any help?

by curacao_dejavu

unfortunately I can not give you a detailed answer for w2k. but in NT there was a option when you where configuring the client to dial in, it was if he could see only the that particular server that we connected to or the whole domain (other optionsyou the ipsettings, ipx or tcp, security authentication). There should be something similar on w2k. The problem lies at the client side.

On another note I wouldn't configure the exchange server as a rasserver, use a workstation or a member server, certainly not any Domain Controller.

regards,

Leopold

by dsv920

Our Exchange Server is not a domain controller neither primary or secondary. It was used and setup for RAS for our outlook clients to dial-in remotely and synchronize their inbox and folders. We had a request from one of our clients to gain access to an Access database on another workstation in our domain, so we tried to give them dial-in capabilities to give them access to the rest of the network or workstation. Keep in mind though that we only gave him/her particular access to that database and folder. The involved sharing access and security access. They cannot see the network though or even map a network path to that resource. Thanks for your suggestion though.

by mwc

Just a thought you said the Exchange box they are dialing into is not a DC so I am assuming its just a member server?? If you gave the dial in user access to the this box with the proper permissions and it is not a DC the user is unable to autheneticate to the domain just able to access the Exchange box via RAS.

by mwc

Suggestion: You need to make your Exchange dial in box a DC or try replicating the database needed from the domain to the dial in server.

by curlergirl

Two things you need to check. First, when you configure RAS, you have the option to allow access to the entire network, or just this server. This is a checkbox in the Network area of the RAS configuration - go to Network Properties/services, double click Remote Access Server to bring up the properties of the service, and then click the Network button and then the TCP/IP button. You should see this checkbox here - if it's not checked, then that could be part of the problem. The other part ofthe problem is that the remote workstations need a method of name resolution in order to browse the network after they connect. If you are using WINS, and assuming WINS is on a different server than RAS, the workstations need the IP address of the WINS server. The easiest way to do this is to configure the dial-up properties on the client with the WINS server IP address (on the Server tab of the dial-up connection, click TCP/IP, and you'll see the boxes there to enter the WINS server addresses). Or, if the clients are getting their IP addresses assigned by a DHCP server on the network, they could get the WINS server address(es) from the DHCP server if it's set up for this. On the RAS server you have to be sure that WINS is bound to the dial-up adapter also as well as the internal NIC. If you're not using WINS, then the workstation will need a file - I believe it's an LMHOSTS file - to identify the servers in the domain. Hope this helps!

This discussion is closed to new replies.