using local crendentials instead of domain crendentials

  • Thread starter Thread starter Randy
  • Start date Start date
R

Randy

Hi,

I have set up a VPN for my network. I can successfully
log onto to the VPN but I cannot browse any of the
servers on the network. I can successfully ping them by
hostname. When I try to browse a domain controller it
says that access is denied. When I try to browse just a
member server it brings up a username and password
prompt. It will let me in when I put in my
domain\username and then my password. Here is where it
gets interesting. I had a feeling that when I tried to
browse these servers that it was using the local logon on
the remote machine that I was using to connect to the
VPN. I made a local account on the remote machine with
the same username and password as my domain account and
now it will let me browse the servers. Do you know how I
can get it to authenticate with my domain account which I
use to logon and validate with the VPN instead of trying
to use my local logon? Any help would be greatly
appreiciated. Thanks.

Randy
 
That's the way it works. Authentication just checks to see that you have
the necessary permissions to establish a remote connection. It does not
perform a domain logon. (In many cases this would be impossible, because the
client has already performed a domain login to a local DC).

There is an option to allow you to login using a dialup connection,
rather than doing a local login at bootup.
 
IF your using WIN 98 hit cancel when you logon this will prompt for the
logon box once you connect the VPN
 
Back
Top