VPN verifying username and password

June 13, 2006 at 06:17:12
Specs: WindowsXP, P4
I'm trying to make a VPN connection from my Windows XP at home home to my Windows 2000 server at my office. Once in a blue moon I can actually connect. But most times it says "verifying username and password" for 30 or 40 seconds and then ends with an error 721. I don't understand why it doesn't connect most of the time but does connect occasionally. There doesn't seem to be a pattern.

See More: VPN verifying username and password

Report •


#1
June 13, 2006 at 10:34:59
Well, that is an interesting problem and patterns do help to determine causes. This one won't be a quick answer as you've probably guessed. Since there are no patterns, and the vpn establishes sometimes, then there is something that is right sometimes.

What are the service pack levels of the server and the xp machine?

Is the server part of a cluster?

What type of vpn are you trying to establich - pptp?

Is there another server or device that may answering the xp client requests to establich the vpn? If there are other servers, make only the one server be able to talk vpn to the client.

A sniffer on the server side may tell you if it is receiving the requests at all from the client. Check logs on the server. Find them for a vpn session that worked then compare to times when your xp client cannot connect.

The grass may not be greener on the other side . . . but it just might have less weeds. :-D


Report •

#2
June 13, 2006 at 14:18:48
We have a small system, just 2 servers. One acts mainly as the domain controller and the other one has applications and data. The servers are W2k SP4 and the client is XP SP2. I am trying to establish a pptp VPN connection. This is done routinely by employees from their homes on various W2k and XP machines. This one client is the only one having this problem. The VPN logs show when this client logs in successfully, but nothing shows up in the log when it can't connect.

Report •

#3
June 16, 2006 at 06:13:13

It looks like, as you too might have determined already, the problem is likely on the desktop side or desktop characteristics related and not the server since all other clients are not experiencing intermitant success. All others work everytime.

Have you looked at relevent differences between a working system and a non-working system? Differences such as number and types of network adapters, network configuration (tcp/IP), static configurations like default gateways, dns servers, routes, netbios over IP, etc.
Can you bring a working system (hopefully there are laptops that work ok) to the network where there is intermitent success? This would tell us if the issue is network or more definatively desktop.

Is the remote computer that doesn't work all the time a member of the domain too or in it's own workgroup at the remote location? Is the name of the computer unique? Tried differnet username (login credentials)?

The grass may not be greener on the other side . . . but it just might have less weeds. :-D


Report •

Related Solutions

#4
June 16, 2006 at 13:56:06
I do have some new information that may help. The client side router is a Linksys wsp54G. It appears to be configured properly. However, when you bypass the router and run a cable directly from the cable modem to the client PC, it is able to log in through the VPN every time. Does this indicate that the router is defective?
The computer is just a workstation on a home network. The Computer name is unique. I have tried logging in with different ID's with no difference.

Report •

#5
June 16, 2006 at 15:17:08
Look for an option to enable IPSec passthrough.

Linksys('s) has this option depending on firmware. I have had to use it in the past.


The grass may not be greener on the other side . . . but it just might have less weeds. :-D


Report •

#6
June 16, 2006 at 15:22:44
I forgot to mention because i wanted to get my suggestion out to you quickly. That was great added peice of information that truely pushed the cause to the remote network/desktop and away from the server and office network.
I hope enabling ipsec pass-through on the linksys router does the trick - I think it will. I should have considered it sooner for posting.

The grass may not be greener on the other side . . . but it just might have less weeds. :-D


Report •

#7
June 20, 2006 at 05:32:57
I upgraded the firmware and enabled ipsec pass-through and now it works! Thanks for your help!

Report •

#8
June 20, 2006 at 19:31:46
Your welcome.
I'm glad it worked out ok for you.


The grass may not be greener on the other side . . . but it just might have less weeds. :-D


Report •


Ask Question