WSASocket() failed: 10013
Trying to make a VPN connection, I setup a Windows PPTP server on my vista machine via Network Connections > File > New Incoming Connectionsand connection was failed evey time with Failed To Connect from another Vista MachineI tried using pptpclnt and I get this =================================Connectivity test to TCP Port 1723 was successful!!!Closing down socket...================================= Creating a socket to test GRE protocol traffic... WSASocket() failed: 10013 *** NOTE: Firewall is off and there is not a firewall between the 2 machines.Any ideas, I have tried everything :(Also I did try running it local usingpptpclnt localhost, but same result, and I also setup the pptpsrv and same result.Thanks, GenCode
January 21st, 2009 9:45am

Hi GenCode, Thank you for your post.I understand that the error WSASocket() failed: 10013 was received when testing GRE protocol traffic. Regarding this, I suspect that the GRP protocol is disabled or occupied. Based on my research, I would like to suggest the following: 1. Check the router settings to ensure the GRE 47 protocol enabled. You can also by pass the router and set a direct connection to see if it works. 2. Check the security software. 1) Stop Windows Firewall service. 2) If you have some third party firewall, please uninstall it. 3) Please also temporarily remove the anti-virus software. Please check the results. 3. If the issue persists, please perform a Clean Boot to check the issue. Clean boot ================1) Click the Start Button type "msconfig" (without quotation marks) in the Search box, and then press Enter. Note: If prompted, please click Continue on the User Account Control (UAC) window. 2) Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray). 3) Click the "Startup" tab, click "Disable All" and click "OK". Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK. NOTE: we can go back to normal boot by running msconfig again and checking on Normal Startup in the General tab. In the Clean Boot Environment, the third party services and applications are disabled, please monitor if the issue reoccurs. If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit. Hope this helps.Thanks.
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2009 1:35pm

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

Other recent topics Other recent topics