Cannot connect windows 7 Pro to Server 2003 VPN
Hi, I am running a RAS Server on Server 2003 SP2 , XP Pro clients can connect to the vpn no problem, but when I try connect 7 Pro clients connection fails with a 800 error. As far as I can see the settings are identical to the XP ones, I have turned off windows firewall and the additional one that is part of the security suite installed on the 7 Pro client but still nothing, it just hangs at veryfying username and password. Thanks :-)
March 30th, 2011 8:27am

After looking at the router log and comparing the two systems,the xp one sends: Wed, 2011-03-30 13:33:50 - TCP Packet - Source:83.217.***.***,3356 Destination:192.168.0.158,1723 - [VPN-PPTP match] Wed, 2011-03-30 13:33:50 - GRE Packet - Source:83.217.***.*** Destination:192.168.0.158 - [VPN-PPTP Data match] This works fine...... The 7 Pro client sends : Wed, 2011-03-30 13:35:03 - TCP Packet - Source:83.217.***.***,62741 Destination:192.168.0.158,1723 - [VPN-PPTP match] This is as far as it gets, for some reason no GRE Packet is sent / received
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 8:44am

What protocol are you using to connect, PPTP or L2TP? To get mine to work with a Windows 2003 VPN Server I had to go into the connection's properties and change the type from Automatic to the specific type of connection I wanted (in my case PPTP) otherwise I had the same issue.
March 30th, 2011 8:48am

PPTP, I have gone into the windows 7 connection and changed that already and it didnt do anything, well it did, as it was trying to connect using L2TP before as I found out by looking at the router log, but it still wont connect even using PPTP
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 8:56am

Make sure TCP port 1723 is open in both directions on your Windows 7 firewall. I know you said that you turned it off, but I've found that sometimes it's not really off even when it says it is.
March 30th, 2011 9:04am

Added that, with firewall still off and still wont connect.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 9:27am

Hmmm. Okay, strange as it might seem, check that the Routing and Remote Access service on the Windows 7 machine is set to automatic and is running. Then we need to step back and make sure that something else isn't happening - check your router (if one's involved) and make sure that its VPN Passthrough function is enabled.
March 30th, 2011 9:53am

That service was disabled on the 7 Pro machine, so enabled and started, re tried connecting and still the same 806 error, the router is the same router that the XP machine is connected to and it works ok, so is really confusing.......
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 10:01am

Even though it works with the XP machine, I thought I would allow all inbound and outbound ports and protocols on the router at the client end just to rule things out and this makes no difference, the xp machine still connects fine and the 7 one still does not :-( .
March 30th, 2011 10:21am

Forget the Routing and Remote Access service, that was bad advice. Go ahead and set it back to Disabled. It's confusing me too. I use Windows 7 with a Windows 2003 VPN all the time - pretty much daily in fact - and it works fine after I made the protocol change from Automatic to PPTP. One thing I did find though which might be relevant: ... The VPN server may not be able to get IP from DHCP for the VPN client. So, you may want to re-configure VPN host networking settings. For XP pro VPN host, go to the Properties of the VPN>Network, check Specify TCP/IP address and Allow calling computer to specify its own IP address, and uncheck Assign TCP/IP addresses automatically using DHCP. I know it says XP, but the same would hold true for Windows 7. Basically what it's saying is that the VPN server is having problems assigning an IP address to the connection - either it's out of addresses allocated to it from DHCP or your client isn't accepting the address it's trying to assign. There were some other things too, but you'd already tried all of them. Other than that I'm out of ideas. Sorry.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 10:22am

Ok thanks for your help, I am trying one other thing first before I go insane, I have windows 7 laptop I am sending someone home with tonight and I am going to remote into it tomorrow and try connecting into the VPN with it using their router and a different laptop, that would rule out my router and laptop being the problem if its not a generic windows 7 problem. If that still doesnt work I will try that IP fix of yours and see if that resolves the problem. thanks :-)
March 30th, 2011 10:47am

Ok, just incase this helps anyone with diagnostics, here are the details of the XP machine's connection that is WORKING Device name : wan miniport (PPTP) Device name : VPN Server Type : PPP Transports : TCP/IP Authentication : MS CHAP V2 Encryption : MPPE 128 Compression : MPPC PPP multilink framing : on Server IP address : 192.168.*.** Client IP address : 192.168.*.***
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 10:54am

Okay, looking over your XP settings I'll give this one more shot. No guarantees though. Let's check your Windows 7 connection settings and make sure they're exactly the same as the XP settings. Go into the settings for the connection: Start Orb, right-click on Network and select Properties. In the left pane click on Change adapter settings. Find the connection and insure that it says WAN Miniport (PPTP) - from what you've already said it should be fine. Right-click on it and select Properties. Select the Options tab. Click on the PPP Settings... button. Make sure all three boxes are checked (your XP config shows they are.) On the Security tab make sure it's set to PPTP and that both CHAP and MS-CHAP v2 are selected (by default they should be for PPTP.) On the Networking tab turn off TCP/IPv6 (this shouldn't matter, but since XP doesn't use this protocol we won't here either.) Click OK. Now your connection should be identical to the XP setup. If it still won't connect I have to suspect an external source like security software or the router.
March 30th, 2011 1:27pm

Well it is all a mystery, the other laptop that I tried on win 7 seemed to work, so I am putting it down to my laptop at the moment until I can test at another house as the xp one works fine through my router, so a fresh install of win 7 would probably fix the prob if I cant work out the mystery.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 6:12am

The issue may be related to your router. Please refer: Error Message: VPN Connection Error 800: Unable to Establish Connection http://support.microsoft.com/kb/319108Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 1st, 2011 4:34am

Surely if it was my router the XP client wouldnt work as it is connected to the same router ?.
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 8:53am

Just to tidy this one up for everyone, I came back to this problem tonight after a couple of weeks and thought....well we know the vpn works with xp, so I initially ignored the router at the client end, but after going over the windows 7 client with a fine, and I mean fiiiiine touchcomb, checking logs, running multiple diagnostic tools etc I came to the conclusion it couldnt possibly be the client as everything seemed to be running as it was, it was leaving the network card and seemingly coming to a brick wall..... So I created some rules on the router firewall for outbound traffic, it was currently set to allow all traffic out so I went and created some rules for the vpn ports to allow them anyways and also a useful one I found out later was to allow logging when those rules where triggered so I could see what was going on in the router log. I also added the same ports on the inbound side and added logging for those also........ and now it works........ this seems to make no sense what so ever as the xp machine is using the same ports etc, so after adding those rules to the CLIENT router's firewall it seems to work now on windows 7 and XP. Its a mystery....but it works so at least that problem is fixed.
April 19th, 2011 4:27pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics