VPN hangs on verifying username/password

  • Thread starter Thread starter tcv
  • Start date Start date
T

tcv

Hi there,

I know this is a common issue and there are a ton of ways to fix it.

But, alas, I've not run across anything that has helped me.

When I attempt to create a VPN connection with Microsoft's standard
PPTP VPN, the dialogue hangs and eventually times out on Verifying
Username and Password.

I actually have three systems in my home.

1. Windows XP Pro SP1
2. Windows XP Pro SP2
3. Windows XP Pro SP2 attached to an SBS domain

All systems are connected to a single m0n0wall router and, guess what,
the XP Pro SP1 system can connect all day but the other two cannot.

So, it seems to be something related to SP2. I have tried to disable
the Windows Firewall and that hasn't helped. I also punched a hole for
1725 in the Windows Firewall and that hasn't helped.

Any other thoughts? Pretty please!

Cheers,

m
 
Assuming you receive VPN error 800 or 721, that could be the GRE issue. These search result may help,

error 721 and error 800 Q: Error 721 and error 800. I have SBS 2003 Standard Edition. ... I double checked the check list in server management and enabled VPN to the appropriate ...
www.chicagotech.net/Q&A/vpn25.htm - Similar pages


case Studies - VPN error 721 and 800 Case 1: When a user attempts to access the Windows VPN server that is behind a Linksys WRT54G, he receives VPN Error 800 or 721. ...
www.chicagotech.net/VPN/vpncase800.htm


cannot establish VPN with error 721 and 800 Whenever he tries to establish the VPN, he receives Error 721 or 800. Troubleshooting: 1. Telnet port 1723 and get respond. 2. We can establish the VPN in ...
www.chicagotech.net/cisco/vpngre1.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<tcv> wrote in message Hi there,

I know this is a common issue and there are a ton of ways to fix it.

But, alas, I've not run across anything that has helped me.

When I attempt to create a VPN connection with Microsoft's standard
PPTP VPN, the dialogue hangs and eventually times out on Verifying
Username and Password.

I actually have three systems in my home.

1. Windows XP Pro SP1
2. Windows XP Pro SP2
3. Windows XP Pro SP2 attached to an SBS domain

All systems are connected to a single m0n0wall router and, guess what,
the XP Pro SP1 system can connect all day but the other two cannot.

So, it seems to be something related to SP2. I have tried to disable
the Windows Firewall and that hasn't helped. I also punched a hole for
1725 in the Windows Firewall and that hasn't helped.

Any other thoughts? Pretty please!

Cheers,

m
 
Assuming you receive VPN error 800 or 721, that could be the GRE
issue. These search result may help,

Well, here are some results of various tools' output:

First, the pptpclnt mentioned:

======================================
Enter data to send to server (between 1 and 255 chrs.), then hit enter:
-->0

Successfully connected to server using TCP port 1723 (PPTP)
Sending data to server

Waiting for a reply to the data which was just sent...
Received a reply. Reply contains the following text:
--->

=================================
Connectivity test to TCP Port 1723 was successful!!!
Closing down socket...
=================================

Creating a socket to test GRE protocol traffic...

Total GRE packets sent = 1
Total GRE packets sent = 2
Total GRE packets sent = 3
Total GRE packets sent = 4
Total GRE packets sent = 5

=====================================
Check server to see if the GRE packets were received successfully
=====================================

Closing down socket

Goodbye!

------

Secondly, portquery's results on 127.0.0.1 to 1723.

Starting portqry.exe -n 127.0.0.1 -e 1723 -p TCP ...


Querying target system called:

127.0.0.1

Attempting to resolve IP address to a name...


IP address resolved to VAIO.TheComputerValet.local

querying...

TCP port 1723 (pptp service): FILTERED
portqry.exe -n 127.0.0.1 -e 1723 -p TCP exits with return code 0x00000002.

-------

I checked the Event Viewer and found this:

Windows Defender Real-Time Protection agent has detected spyware or other
potentially unwanted software.
For more information please see the following:
http://www.microsoft.com
Scan ID: {0BF8EB16-CD65-4B18-BFA1-4FFB800E437A}
User: XXXXXX
Name: Unknown
ID:
Severity ID:
Category ID:
Path Found: firewallport:HKLM\System\CurrentControlSet\Services
\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts
\List\\1723:TCP
Alert Type: Unknown
Detection Type:

---

That last part is kind of interesting...

What do you think?

Cheers,

mw
 
Actually, the logs for Windows Defender shows that I allowed the action.
So, I suppose I'm okay.

But the port at 127.0.0.1 is still filtered. Hmmmmmm... Should it be
reported as open? Perhaps I should try it on the machine that can
connect...

mw
 
Another piece of information:

The system I am primarily concerned about is the SBS connected system. The
firewall stuff is all greyed out, but "OFF" is selected in the firewall. I
don't know how to wake it up, honestly, or if it makes a difference.

I can make local exceptions.

I want to know how to wake it up, so I'll research that.
 
cannot establish VPN with error 721 and 800 Whenever he tries to
establish the VPN, he receives Error 721 or 800. Troubleshooting: 1.
Telnet port 1723 and get respond. 2. We can establish the VPN in ...
www.chicagotech.net/cisco/vpngre1.htm

Ooook, so it really helps when:

1. You figure out that you're running a third-party firewall, even when
that third-party firewall is actually a first-party firewall. (Windows Live
One Care)

2. You actually _read_ the instructions that come with the tools.

I have determined, without a doubt, that GRE is NOT getting through to the
laptop from which I'm trying to make the connection. 1723 is fine.

So, why would that be?

Now remember, I have another machine in this building going through the
same router and it has no trouble receiving GRE. It's XP Pro SP1.

It's definitely within the computer. It's not the router.

Cheers,

Mike...
 
Success!!

I reapplied the Security Descriptor in a MSKB article and that seems
to have done it!!

Woohoo!
 
Would you please tell us which Security Descriptor KB?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<tcv> wrote in message Success!!

I reapplied the Security Descriptor in a MSKB article and that seems
to have done it!!

Woohoo!
 
I was wondering how you fixed this? Im having the exact same problem.
Could you explain what you meant by reapplying the security
descriptors? Or point me to the place that helped you!!?
 
Back
Top