Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 27273 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 9954 [details]
If i have my VPN activated (which I need since I'm accessing internal data) the Android Player won't fully start up.
It works when i'm not connected via a VPN, but don't have access to the data I need, so kind of pointless.
further note - I can no longer start the Android Player at all now, regardless of whether the VPN is active or not. it Loads indefinitely.
There are some known issues with VirtualBox networking and certain VPN software (eg. Cisco AnyConnect), could you let me know what VPN client you're using?
I am using Cisco AnyConnect.
I have access to another VPN provider, let me uninstall CISCO AnyConnect and see if it works with the other one.
I'll report back.
Uninstalling CISCO AnyConnect didn't resolve the issue.
I do have IBM Mobility Client installed.
Next i'll try re-installing Xamarin Android Player.
Same issue with IBM Mobility Client.
I experience this same issue. I'm using the builtin VPN client on OS X 10.10.2. No other VPN clients installed.
Does this help?
I have the same issue using Cisco AnyConnect. I am required by my employer to use that VPN software so I can't use something else.
I looked at Nate Cook's suggestion, but IPFW and PF are both way out of my league. I tried finding instructions for how to remove the "deny ip from any to any" rule but didn't come up with anything that I could figure out (either with IPFW or PF).
I'm at an impasse because I need to be connected to the VPN to access internal servers so I need to use the emulator instead of an actual device.
Hi Justin. There are more detailed instructions at the bottom of the blog post:
See if that helps. But I agree that I would like to see an easier workaround, or a real fix of some sort.
Is there a way to do this with PF instead of IPFW? Searching for IPFW online everyone suggests switching to PF since that is what Apple did starting with Yosemite...
My understanding is that AnyConnect uses IPFW internally and that there is no way to modify IPFW rules using PF.
Even though this post is a few years old. I'd like to say that I'm having a similar issues using the F5 Access VPN client.
I am required to use the VPN client because my PC is on a local, secure network, and access to the network is granted only after VPNing into the network using the F5 Access client. I have been able to successfully access my machine using this VPN connection in the past, using Remote Desktop for instance, but I am unsuccessful in completing the connection to the PC from the Android test device.
Here's the output of the connection:
Start (Scann.Android, PANASONIC FZ-X1 Player, )
Attempting connection to debug address: xxx.xxx.xxx.182:37847
Error while trying to connect directly to the device: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at Xamarin.Player.Remote.DeviceDeployer.<>c__DisplayClass30_0.<ConnectAsync>b__0() in C:\d\lanes\5156\34c1b6c2\source\xamarinvs\External\Xamarin.Player.Remote\Source\Xamarin.Player.Remote\DeviceDeployer.cs:line 431
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Xamarin.Player.Remote.DeviceDeployer.<ConnectAsync>d__30.MoveNext() in C:\d\lanes\5156\34c1b6c2\source\xamarinvs\External\Xamarin.Player.Remote\Source\Xamarin.Player.Remote\DeviceDeployer.cs:line 419
Connected to: xxx.xxx.xxx.105:47867
Got device info: PANASONIC FZ-X1 Player (Android) @ xxx.xxx.xxx.182:37847
Building and running...
Built with 0 messages
Could not connect to the debugger.
Could not connect to the debugger.
A note that the IP address reported by the log output shows an IP address ending in 182, which is the proper IP address for the Android device. The VPN tunnel IP address ends with 157, which doesn't appear in the logs anywhere, and I think that this is the IP address that it should actually be connecting with.