Amazon EC2 "PING: Transmit Failed, error code 1232."

[deleted]

Hi All,

I am having a bit of a problem with seting up OpenVPN 2.2.2 on a Windows 2008 Server (32bit) on Amazon EC2 (AMI: Windows-2008-SP2-i386-Base-2012.01.12 (ami-9983dddc)).

It is connecting to another Amazon EC2 instance running Linux and OpenVPN 2.1.4 (openvpn-2.1.4-1.2.amzn1.i686). Several other clients also connect to this server running various types of Linux and Windows.

On this new instance when I start the connection it seems to come up correctly but after a few seconds it then fail's to ping another server on the network. It just stops. Below is a snip of it;-

Reply from 10.10.10.11: bytes=32 time=157ms TTL=64
Reply from 10.10.10.11: bytes=32 time=156ms TTL=64
Reply from 10.10.10.11: bytes=32 time=158ms TTL=64
Reply from 10.10.10.11: bytes=32 time=158ms TTL=64
Reply from 10.10.10.11: bytes=32 time=158ms TTL=64
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.

If I restart the service, it works for a few seconds and then stops again with the same error. I have done a few searches here and on the Internet and found a few threads dealing with this problem ( https://forums.openvpn.net/topic8172.html in particular) and have tried all sorts of things but as of yet I still cannot create a stable connection.

I am hopeing that someone knows exactly how to fix this and will just give it to me as a one liner.

Mimiko

Problem:

C:\Users\Tan>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:

PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.
PING: transmit failed, error code 1232.

Solution:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Tan>netsh winsock reset

After which, just do a restart and your network will be back to normal.

Hope this helps someone out there…

jason404

I have the same problem. I've spent hours looking for a fix, and I have tried various things, but nothing has worked.

Starting the OpenVPN service manually after bootup does not work.
Resetting winsock and tcp/ip stack does not work
Disabling APIPA seems to be difficult, but when I appeared to defeat it to get the intended IP address on the TAP interface, it didn't work.
A couple of other registry edits did not work.
Doing various mixtures of all of the above does not work.

It appears that Windows Server 2008/R2 + Amazon EC2 + OpenVPN == FAIL

I feel sick with frustration.

[deleted]

To add to this a "sort" of solution.

This problem only seems to affect the 32bit version of Windows Server 2008, the Windows Server 2008 R2 x64 EC2 seems to work correctly.

The problem with that was that Amazon did not offer a 64 bit option m1.small and c1.medium instances. Earlier this week Amazon announced and put into operation 64 bit m1.small and c1.medium instances.

Since then I have set up a little test and fired up two m1.small instances with the standard Windows Server 2008 R2 x64 install, installed OpenVPN 2.2, connected them to my server (AMI Linux x64, OpenVPN 2.2).

The first instance has been running continuously for 2 days now with very little packet loss (nothing above normal, under 0.1%).

The other server I have rebooted more times than I can count, every time the OpenVPN connection has come up without issue.

I know that this is more of a workaround than a solution, and I have only been at it for a few days but it is looking good and I suggest anyone that is having issues to try the 64bit AMI Images (now that it is possible).