Remote Access Problem

Basic questions: Is the RAS the same machine as the DC? From your problem, I'm guessing not. If that is the case, can you ping the DC from your RAS machine? I've had a similar problem, and it was because my local machine was using DHCP and the lease had expired and not renewed during the logon. Either setting a static IP or rebooting should take care of that problem.

If the RAS is the DC, sounds like it is a permission problem. Do the users have permission to access the DC or RAS dialinpriviledge? Hopefully this may steer you in a direction.

Roger

Unfortunately, NT's RAS is tempermental. Check the following:
1. Make sure the workgroup name on the RAS client is the same as the workgroup name or domain of your LAN.
2. If you are using DHCP, make sure you have configured the DHCP scope to provide WINs addresses. You may even have to go as far as manually inputting the WINs server IP address under the TCP/IP properties of the DUN settings. You definitely need to do this if your clients have static IP addresses.
3. The WINs server on your network should not be multihomed (two NICs in one server, each connected to a different network).
4. Verify that you selected the "Allow RAS clients to access entire network option on the NT RAS server" if you want the clients to be able to see other network resources other than the RAS server.
5. If the remote client is a laptop that was recently connected via a LAN connection, allow enough time for the browse list to drop the machine before dialing in. Otherwise, a conflict can occur.6. For your Win95 clients, download and install the the Dial Up Networking patch:
http://www.microsoft.com/downloads/release.asp?ReleaseID =12646 (there should be no spaces in this link)
7. Download and install RASUPD.EXE for 95 OSR1 clients. Install RAS2UPD.EXE for OSR 2 and 2.1 clients. You'll find them at the MS Knowledge Base under article Q154434.
8. If problems are still occuring, add an LMHOSTS file to the client.
9. As a last resort, install NetBEUI on the client and RAS server.

You should install your RAS on a (at least) BDC, which could directly verify the userid/password pair.

vh_s

Hi Frank

Fristly you should get one static ip ( not from DHCP) from your network administrator. And store the ip address of your server into lmhosts file resides at (default location) c:\winnt \system32\drivers\etc\lmmhosts

Secondly
the major thing you have to check is, do you to rights remote login that you can chk with user manager on domain

Thirdly
Chk for logon time, logon from computers ( if there is any restriction is defined than remove the restriction).

I am sure this will resolve your problem.

Good Luck
Abhinav