Need help with RAS issues.

[J741]

Server is Windows 2000 Server.
Local clients are Windows 95 and Windows 98.
All works well. Login scripts for drive mappings are operational.

Added RAS functions to the server.
Remote clients are Window 95, Windows 98, or Windows ME on different workgroups or domains (changing this is not an option).
Remote clients use DUN to establish a VPN connection to the W2K Server. No problem with login authentication (as administrator or any user), but logon scripts do not start automatically.
Windows Terminsal Services for remote administration function without any problem.
Manually executing the command "net use S: \\server\data" will prompt for a share password, but the share is not password protected on the W2K server. The administrator password is not accepted for accessing this network resource.

What do I need to change from the default settings in Windows 2000 Server in order to allow my remote clients to access the desired network resources?

- James.

 

[J741]

Any information would be helpful.

 

[mcconmw]

I doubt this will help but have you read MS Knowledgebase article Q157174. What permissions are on the share?

 

[J741]

Thank you, but that did not help. The article makes reference to canceling the initial windows login, until the RAS connection is attempted, but if I do this then I can not connect to the internet before making my VPN/RAS connection.

The share is a directory for which I have given "everyone" full access.

- James.

 

[ianf]

Have you activated your Client Access Licenses ?. The Terminal Services admin sessions will run for two clients without activating your licenses. Further sessions will not. Ian

"IF" is not a word it's a way of life

 

[mcconmw]

I think I was looking at this wrong. I am assuming that they are dialing in to one machine but trying to access resources on another. When users connect, how are they authenticating? Are they using credentials for the local machine or a domain? Everyone is a bit of a misnomer because it does not literally mean everyone. It means in a domain all users that are a member of the domain or a trusted domain. If you do not have a domain, then it means all user on the actual machine. In other words, if both machines aren't in a domain AND the user is not authenticating with a domain account you will have to maintain accounts on both machines with the same password to have seamless connections. If this doesn't help, please describe your network and account setup a little more. Good luck.

 

[paasch]

how about saving youself a lot of time and brain resources. Do this at the server. Create a new s: drive share and call it s: give everyone rights (default) and that will do it. simple huh! See ya.

 

[paasch]

sorry, the remote guys arent a member of your "domain". So setup a generic non $c or $s share. This gets around a lot of problems.

 

[J741]

Alright here's a little more detail to aleviate the confusion...

The server is Windows 2000 Server, configured as a PDC.
The resource I'm trying to access is a subdirectory on the C: drive. The share name assigned to this directory is "data". I shared it using the default settings.

The client I am using to test the connection with is running Windows ME. Both the client and the server have a permanent internet connection (one via cable modem, one via DSL). I connect to the server from the client by way of a VPN connection which uses PPTP. The common networking protocol is TCP/IP.

When the client connects, the client screen reports the following sequence: "Dialing", then "connecting", then "verifying user name and password", then "logging on to network", then "connected". Note: There is no actual dialing by a telephone line, because both machines are already on the interent.

Now, the user name and password for this VPN connection is currently identical to the Windows 2000 server's administrator account.

When connected, I can ping the server without issue. It is only when I try to access anything that is on the server that I have a problem.

I think it may have something to do with the VPN login not being recognised by the server as a domain login, or something like that. But I do not know any way to get by this. Even if I need to reduce the server's security somehow, that will be acceptable. (it's a very small office network).

It's getting to be very frustrating for me, as I can do this without any problem on Windows NT Server 4.0

- James.

 

[J741]

** I FOUND THE SOLUTION **

I found the solution in Microsoft Knowledge Base article Q258938

It seems that the "guest" user account needs to be enabled before remote users can access network shares. The "guest" user accound was enabled by default in Windows NT, but is disabled by default in Windows 2000.

What a huge pain that was !

- James.