Anyone with VPN remote experience / knowlege ?

  • Thread starter Thread starter Lauri
  • Start date Start date
L

Lauri

Hi,

I am trying to configure a 2000 VPN server for remote user
access. I am in test mode and I am having two issues. I
sure hope someone can offer some guidence, because I have
banged my head against the brick wall for several days now
on this.

First, when I set up the VPN client and dial up to the
internet, I enter a valid domain account name and pass I
can connect to the VPN server. However , if I go to
options and check the "include windows domaain" box, It
will not connect. It keeps saying that the account name
or password is not valid on the domain. Can anyone guess
why this option does not work?

Second, and much more of a problem is this: Even when I
connect without the "include domain" option, I can connect
successfully to the VPN server, I can then go to Netowrk
places and see the domain, but when I double click the
domain I get an error message that says "domain name not
accesssible, the list of servers for this workgroup is not
currently available" Huh? Its not a workgroup I am
trying to access, its a domain. I see the domain, but I
get the above message when I dbl click it?

If anyone even has an idea or guess, PLEASE help.

Thank you

Lauri
 
If you have to dial the Internet first, you have two separate
connections, which are set up differently.

The dialup to the Internet usually does not require a domain name. It is
just the connection to your ISP.

The VPN connection over that requires a domain name if you are
connecting to a RRAS server which is part of a domain. If it is a standalone
server, you authenticate to the server's local SAM database. To authenticate
to the domain, the RRAS server needs to be a member of the IAS and RAS
servers group in AD.
 
If you strike probems, it is easier to debug the basic issues locally.
You can make a VPN connection to the server's LAN IP from a LAN client. VPN
will work over the Ethernet connection. This lets you sort out authorisation
and encryption problems.

If you then strike trouble connecting remotely you know that the
problems are new (perhaps firewall blocking).
 
Back
Top