Bug 30138 - User can’t access client SAP box via VPN after installing Xamarin
Summary: User can’t access client SAP box via VPN after installing Xamarin
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-05-15 13:30 UTC by Brian Keene
Modified: 2016-12-22 22:17 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Brian Keene 2015-05-15 13:30:47 UTC
User installed Xamarin and was the unable to access client's SAP box via VPN. Would get the following SAP error: wsaewouldblock : resource temporarily unavailable

From user:

"I can’t tell you which module of the Xamarin installs caused the problem as I’ve uninstalled everything that was installed (Xamarin Studio, Android SDK, Java, Virtual Box, etc). 
It was one of these.  After I’m finished with the current work for the client I will try installing Xamarin again bit-by-bit to see if I can isolate the program that causes it.
But my guess is that something are closing a comm port that SAP wants to use.  One guess is port 3202 or 3602."
Comment 1 vga 2016-12-22 19:30:38 UTC
We don't really have any code blocking the ports you listed. I've seen similar issues with software like Virtual Box which you mention you have installed.

Please let us know if you have any extra information/repros that may help relating this to Xamarin bits.

Comment 2 Jose Gallardo 2016-12-22 22:17:50 UTC
I'll tentatively resolve this bug as fixed, as it might be some issue with the old Build Host. Currently we only require an open port for SSH (22 by default).
But please feel free to reopen the issue if you're still facing it with latest bits.