Windows – Connecting to VPN I get – Error 651: The modem (or other connecting device) has reported an error

vpnwindows 7

I have an end user getting the following message whenever trying to connect to our Windows PPTP VPN:

Error 651: The modem (or other connecting device) has reported an
error.

I've performed a number of steps and still haven't been able to resolve the issue. So far I have tried:

Checked for installation of Microsoft Virtual PC or VirtualBox as others have reported problems with these, but neither are installed.
Disabled IPv6 for the connection source.
Recreated VPN connection.
Reinstalled NIC drivers.
Disabled Windows Vista/7 auto-tuning feature source.
Disabled antivirus and Windows Firewall.
Checked router for any problems or firmware updates (there were none).

Any ideas?

Best Answer

One suggestion I might have is to go to your Device Manager and click on View > Show Hidden Devices. Then in the "Network adapters" drop down you should see a bunch of WAN miniports.

There is a method for removing and then re-adding the miniport(s) that might be giving you trouble. I had a similar issue when trying to use an SSTP VPN, and removing + reinstalling the SSTP Miniport solved the problem. Not sure if it will work for you, but it is something that's not on your list of things tried yet ;-)

Here's some additional info: http://forums.techarena.in/vista-hardware-devices/982266.htm

Related Solutions

Windows VPN – Fixing Error 619 Connection Issues

I've finally found the holy grail:

http://www.jcsilva.com/2011/01/09/issues-with-dd-wrt-gre-forwarding-pptp/

This page says the following:

Issues With DD-WRT GRE Forwarding PPTP

A quick fix for DD-WRT not forwarding GRE PPTP packets.

Add the following commands to the startup commands (Administration->Commands):

/sbin/insmod xt_connmark
/sbin/insmod xt_mark
/sbin/insmod nf_conntrack_proto_gre
/sbin/insmod nf_conntrack_pptp
/sbin/insmod nf_nat_proto_gre
/sbin/insmod nf_nat_pptp

As a side note, I'm not sure why the Professional machine was able to connect correctly and at this point I don't really care now that I have a real solution that isn't enabling the DMZ.

Windows – Cisco AnyConnect Secure Mobility Client service can not start on Windows 7 64 bit system

well I have a fix for you, but its not 100% but it will get it working.

Control Panel > Administrative Tools > Services Right Click Cisco AnyConnect Secure Mobility Agent and choose start. Then run the client and connect

The root of the problem is its not respecting automatic start-up in Windows 8 cause the TCP/IP connector is handled differently in Windows 8 to get windows to start up faster. So upon start and coming out of sleep, it reverts back to stopped again. So upon every start-up you have to do this.

Best Answer

Related Solutions

Windows VPN – Fixing Error 619 Connection Issues

Windows – Cisco AnyConnect Secure Mobility Client service can not start on Windows 7 64 bit system

Related Question