VPN Server in AD Problem

From: anonymous (anonymous@nowhere.ville)
Date: 01/02/03 

From: "anonymous" <anonymous@nowhere.ville>
Date: Thu, 2 Jan 2003 10:35:11 -0500

Hi again.

One lingering issue:
In our NT4 domain, we had an NT4 server (BDC) acting as a VPN server. The
VPN server was upgraded to a 2000 domain controller and we are trying to
reconfigure the VPN.

I followed a ton of MS articles in the knowledgebase during setup... I
believe that I have a properly configured VPN/RRAS/RADIUS server... However,
no WindowsXP clients seem to be able to establish a tunnel.

Attempting to log into the VPN from an XP machine hangs during the verifying
username/password portion of the login. If you wait long enough, you
eventually get back one of several error codes.. The most popular are:
    Error 721: Remote computer did not respond
 and Error 619: The port was disconnected.

I've searched the KB and followed the steps these article reference. Anyone
have a clue what might be hanging the login?

Thanks,
Nony Mouse

Relevant Pages

  • Re: How many users/clients can connect to a VPN in Windows XP pro ?
    ... I can find no information about how many users can login into a windows xp ... pro computer that is functioning as a "vpn server". ...
    (microsoft.public.windowsxp.work_remotely)
  • AT&T Network Client - cant connect to companys network
    ... through Authenticating with the VPN servers...here is the log the ... 11:42:10.376 Retrieving VPN server list... ... 11:42:11.488 Wait for asynchronous action to complete. ... 11:43:56.739 The VPN login request did not complete in the allowed ...
    (microsoft.public.windowsxp.work_remotely)
  • Acess denied to user name and password in radius
    ... I tried to login to my Win2k3 AD vpn server from Win XP sp2 machine but ...
    (microsoft.public.windows.server.networking)
  • WEIRD VPN Behavior
    ... Ok...I've setup VPN servers many times, but recently I setup a VPN ... But when "I" login the server gets a new route. ... now points to my IP on the VPN server (maybe 10.1.4.0 now ... login the routes stays ok, pointing to 172.20.1.1 and all is fine. ...
    (microsoft.public.windows.server.sbs)