RAS'd in but not fully connected

[Crockett]

I have 3 users with the same laptop, same configuration,
same OS (Windows 2000). 1 of them can fully connect to
our network via RAS, the other 2 cannot. What I mean by
fully connect is that the 1 user can access all of the
network resources, including our Intranet, with no problem
via RAS. When the other 2 attempt to access network
resources via RAS they get the validation screen asking
for their user name and password even though they have
made a successful RAS connection. When they then try to
get to our Intranet they get the dreaded page could not be
found message. This is very frustrating since I need all
of them to access our Intranet site to complete
departmental forms.

 

[Bill Grant]

The username/password used to connect over RAS is only used to
validate the connection. It is not used as your credentials on the remote
network (unless you use the login using a dialup connection option).

So whether the users can access resources on the network depends on what
their original login was. If this is accepted on the LAN, they get access.
If not, they don't.

You can always specify your credentials later by using things like the
"Run as " option or specifying credentials in net use commands with the user
option.

 

[Crockett]

All of that I understand. What I don't understand is why
they can't access our Intranet site even though they have
made a successful connection to the network via RAS and
why are they getting the user name and password screen to
access network shares once they have connected?

 

[Bill Grant]

Because when they do a local logon to their machine, they use a local
account. This will only give them access to machines on the LAN if it
exactly matches a valid account on the LAN. That means either a valid domain
account or an account which is valid on that particular server (depending on
your LAN setup).

The server on the LAN checks the client's credentials, and if they are
not sufficient, requests a username/password.