Connection Conundrum

[pilgrim]

I have access to a lot of VPN's and have rarely had problems with any of them but at the moment I am having a problem (only on Windows 7) with one particular server and before I consign the matter to 'one of life's little mysteries' I thought I would see if anyone had any ideas.

The protocol is PPTP, the server is one of three from the same provider, the other two both work as do all those from other providers, which to my mind would tend to rule out port or firewall issues.
When I try to run this connection from Windows 7 I am getting an 807 error. When I tried to connect from XP Mode (on the same computer) the connection went through, which I would think rules out a server issue.

I do not get 'support' from this provider as I have one of the free (lifetime) licenses they offer from time to time but I did notify them of the problem and they said they could find no reason for it at their end.

I have tried shutting down both the Windows firewall and TinyWall as well as my AV, it never made the slightest difference, which leaves me with the question what (on Windows 7) could be preventing access to that one server?

[Ath]

Have you tried re-typing the site-address and credentials? I often see these issues resolved because of a typo in either one of those.

[pilgrim]

I tried that a couple of times before renewing the entire connection.
I know the credentials are right because they are working in XP Mode.

[Mark0]

If you still have the problem you may check if, for some some reasons, the "Routing and Remote Access" service isn't running.

[4wd]

ERROR_VPN_DISCONNECT 807
The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity.
List of Error Codes that you may receive when you try to make a dial-up connection or a VPN connection in Windows 7

It sounds like something on Win7 is interfering with TCP traffic on port 1723, (or the GRE 47 packets), to that specific IP address - that would usually point to the firewall being the culprit.

From a CLI in both Windows 7 and XP:

tracert <vpn that's failing>

And paste the results, munge your IP if it shows up, (first couple of lines), and you're paranoid.

What AV are you using, some won't stop interfering even when disabled.

Even though it works OK from XP Mode on the same computer, if your router has a DMZ put the computers IP into it and try to connect to the VPN again from Windows 7, or if you have a separate modem, plug the computer directly into it and try.  Bypasses any strange firewall rules in the router.

In Computer Management->Event Viewer->Windows Logs->Applications there'll be the results of rasdial commands, a successful connection looks like:



What do you get if it's not the same, (and the actual event data not a picture, thanks) ?

[pilgrim]

Thanks for the replies, I'll try the suggestions later and let you know.

Mark0,

The R&RA service is disabled and I'll try with it enabled later, but that doesn't explain why all my other PPTP/L2TP VPN's connect without issue.

4wd,

The VPN ports are open for all traffic in both the firewalls and the router, I have even tried a second router and it was doing the same thing.
My usual router does not require rules for VPN's, in the other one the rules were set up manually when I started using the provider whose server I am having trouble with.
As I said in the original post I have tried shutting down both firewalls and the AV (Avira) without any change, I have the same AV on all my computers and they have identical settings apart from file paths to various exclusions, (only one 'Program Files' in XP).
I'll get back to you on tracert.

and you're paranoid

Thanks, I like you too! 

(What's the difference between a 'noid' and a 'paranoid'?
The second implies there's two of them.)

[pilgrim]

OK, a partial report:

I tried enabling the R&RA service nothing changed.

Tried tracert (7):

1 General Failure.

Checked Event Viewer and it showed the following for one failed connection:

CoId={AE3F56B9-E6A4-4FCF-BB7B-1DBE6D654A5E}: The user PILGRIMS-PC\Pilgrim is trying to establish a link to the Remote Access Server for the connection named VPN - NL using the following device:
Server address/Phone Number = 'IP Adress'
Device = WAN Miniport (PPTP)
Port = VPN3-1
MediaType = VPN.

For another failed connection it showed:

CoId={63B5372A-8D8F-4644-925E-8E40E890A72B}: The user PILGRIMS-PC\Pilgrim has started dialing a VPN connection using a all-user connection profile named VPN - NL. The connection settings are:
Dial-in User = 'username'
VpnStrategy = PPTP
DataEncryption = Require
PrerequisiteEntry =
AutoLogon = No
UseRasCredentials = Yes
Authentication Type = CHAP/MS-CHAPv2
Ipv4DefaultGateway = Yes
Ipv4AddressAssignment = By Server
Ipv4DNSServerAssignment = By Server
Ipv6DefaultGateway = Yes
Ipv6AddressAssignment = By Server
Ipv6DNSServerAssignment = By Server
IpDnsFlags =
IpNBTEnabled = Yes
UseFlags = Private Connection
ConnectOnWinlogon = No.

Both of the above showed error type = Information.

When it showed an Error it was:

CoId={8E0F690F-7BF5-4925-99D4-05E12EC4C3B5}: The user PILGRIMS-PC\Pilgrim dialed a connection named VPN - NL which has failed. The error code returned on failure is 807.

Unless this tells you anything I'll try again.

[Shades]

Did you try the hints and tips from this link (answers.microsoft.com)?

[40hz]

You could try this. While it was written to address a Samba file sharing problem, the "fix" itself deals with network security settings which are the likely culprits in your case.

Note: if you do make these changes - and only one VPN of the many you use needs it - I'd suggest switching the settings back afterwards and forgetting about that VPN. Reason being these changes reduce your overall network security globally - and that's an unacceptable price to pay for access to just one recalcitrant resource. At least AFAIC.

(You can also download the above article as a PDF. Link here)
.

Luck!