I'm having a fritzbox with vpn and fritznas set up. From inside the local network as expected there is no problem, I can access the user interface as well as mounting the samba share.
But now I'm trying this from another network (but connected to the firtzbox via the built in vpn service) and I've got a situation which is very weird.
From my laptop I can connect via vpn and bring the user interface up, but I cannot login in the user interface (with the normal user interface password) neither can I mount my samba share.
But I'm sure that the vpn connection is set up properly since ssh to machines connected to the remote fritzbox works.
And now I've tried this too from my smartphone (connecting via vpn, log into the user interface and access the samba share) and there everything is quite fine.
Any suggestions what might cause these problems on the laptop (I'd say that something in the fritzbox is set up falsely but since it works on the smartphone, it has to be something on my laptop I think)? (I have tried everything I can think of but nothing works)
With best regards and thanks in advance
PS: My OS is Arch Linux
EDIT: It gets even stranger: If I change my setup from
Laptop -> WLAN -> VPN to
Laptop -> Hotspot of my Smartphone -> VPN it works again (but slow of course since now it is over the mobilenet of the smartphone)
I have a virtual machine that i run with rdp in my local pc. I'm developing a xamarin forms app in visual studio in that virtual machine. So I would debug the app in my psysical device. I tried with adb but it don't work cause I can't connect my device via usb to virtual machine. Any ideas??
Google just updated this from Android 11 onwards, so for any one using a newer device, you can follow these steps to setup your device to build and debug wirelessly using your wifi connection:
On your Android 11 device, go to your Settings -> Tap on Advanced and go to the Developer options.
Then tap on Wireless Debugging switch, and always allow wireless debugging for your personal wireless network in the popup dialog
Then tap on the Wireless Debugging option and select “Pair device with pairing code” and it will give you a 6 digit code and IP address as you can see in the image
There are many ways of doing pairing the phone to your computer. For the simplest one, inside Visual Studio, go to Tools -> SDK Command Prompt and type the IP address and port from your phone above into the terminaladb pair {ipaddress}:{port}.
Then take the IP Address and port from the last screen and enter the following command adb connect {ipaddress}:{port}.
There’s a lot more details in this article Including limitations and a comparison with the iphone wireless debug feature
The ADB port forwarder can be used to connect your local adb client with a remote adb server.
This can help you solve your problem: https://bitbucket.org/chabernac/adbportforward/wiki/Home
I had installed WSO2 Identity Server V5.2 on a VirtualBox machine, and it was working fine.
Then, I was doing some network testing/reconfiguration on my home network, where I was trying to separate my development (virtual) machines from my main in-home LAN by having the machine that was hosting VirtualBox connect wirelessly to a small router (a TPLink TL-WR702N) in a Bridge configuration, where the TPLink is connecting to my main WIFI network and then also exposing itself as a different WIFI network).
I was doing this testing because I am going to be working from a different location for awhile, and I wanted to isolate my dev machines while I was there and I only will have WIFI, and no hardwired connection, so I wanted to see if I could bridge wirelessly.
That machine hosting VBox started up ok and actually, the WSO2 machine also came up ok, but then when I tried to start the WSO2 IS (./wso2server.sh), it would output the 1st 3 lines and then hang on the 3rd line which was "User Java memory...".
If I move the hosting machine back to my normal LAN (i.e., not on the "bridged" network), everything works fine.
I noticed that when the hosting machine was on the bridged network, I couldn't ping the network gateway (192.168.0.1) from the VBox guest machines.
Would that cause the WSO2 to hang during startup? What else might be causing this problem?
Thanks,
Jim
I think that the problem was that WSO2 IS seems to need to be able to resolve the hostname during startup, and that was combined with needing to (apparently) bounce the machine to get the networking working. After the bounce, the networking seemed to get straightened out and then the WSO2 IS was able start ok.
I can't seem to figure this out and hoping someone can give me some pointers. I'm unable to open a port on a Azure VM. After a fresh provision of a Windows 2008 VM I've disabled the Windows Software Firewall for all networks. Next i went to the azure management portal and added a TCP endpoint for port 9090 (both public and private).
While connected to the server via RDP i visit http://www.canyouseeme.org/ to test if port 9090 is open. But it comes back as error cannot see the port 9090.
As far as I can tell this is a standalone VM not connected to any domains or special networks.
Any ideas what is missing?
This was a strange problem that i "fixed" by changing the VM size from extra small > small and back again. For some reason something was reset and i could open the port again.
I have Windows 8 installed inside of an emulator, and the new WP8 SDK installed on it. My problem is that the emulator can't connect to the internet. I don't have any proxy, and even disabled the firewall. It still doesn't seem to work though. When I look at the Network Connections sections I can see the new connections the hyper-v manager created for the emulator, and also the automatic bridge created, but even there the network status is "No Internet Connection".
Are there some properties I can manually change in Hyper-V or for the network to make everything work?
Update: I've done everything suggested including create my own switch and delete all others. It still doesn't work however. It doesn't work on cable and not on wifi. Maybe I'm missing something with how to set this up?
Also the WP emulator keeps offering me to connect to the internet every time. It always erases all of the definitions I've set up, replacing it with it's own definitions.
I think I've finally found the answer, but you're probably not going to like it. It would appear that the phone emulator requires you to have a second network adapter to dedicate to this purpose. Personally, I run Windows 8 in VMWare, and so a second network adapter is free for me.
Anyway, after you get the second network adapter that you can dedicate for the phone emulator(must have internet)
Start from scratch. Go to the Hyper-V manager and delete the emulator along with all of the virtual switches
Start the emulator from Visual Studio; this will recreate it with all default settings(select yes you want to configure it to connect to the internet)
Shut it down
Now, go back to the Hyper-V manager
Delete the snapshot that was just created for the emulator. This will prevent your changes from disappearing
Find the virtual switch for your second network adapter in the Network Adapter settings(under control panel)
Disable TCP/IPv4, 6 and all other services. This prevents your host machine from trying to use the connection. While you're there, get the MAC(Physical) address of this adapter
Find the virtual-switch for your second network adapter under the Hyper-V settings for the emulator
Change the MAC type to static and paste in the MAC address of the adapter
Enable MAC spoofing (not sure if required, but just in case)
Then, find your virtual switch under "Virtual Switch Manager".
Ensure "Allow management operating system to share this network adapter" is unchecked and that all extensions are disabled
Click OK and then start the emulator from Visual Studio!
Basically, it appears that for some odd reason it won't properly work unless the phone has the same MAC address as the network adapter. However, we can't just set it to use the same MAC address because address conflicts are very very bad. So, we need a second adapter that we can dedicate to the Phone emulator. The reason we disable TCP/IP on this adapter is so our host machine doesn't use it and cause these conflicts.
Other things to try:
The emulator keeps randomly breaking for me. I'll list a few other things I messed with this last time that got it to work(not sure if related, so only try these if the steps above aren't working
"Reordering" of network adapters for the emulator so that the external virtual switch is at the top (make sure to copy over the MAC address for the internal adapter)
Removing unrelated network adapters
Restarting your machine after recongiguring virtual switches
Praying to your local Microsoft evangilist
Seriously. Everytime I stop phone work for a while and come back, the emulator is always magically broken without me changing anything. No idea how to get it to work "permanently".
I had the same issue as well. However as someone else pointed out on the official forums it didn't work if you had a static IP for your PC set up in your router. Removing it and let the DHCP assign my PC an IP solved the issue for me.
Source
Here's what worked for me:
Go into the internal network connection created by hyper-v in network connections on the host computer. Go to TCP/IP V4 and go to advanced. Change the metric from automatic to 10.
Go to the external network connection, do the same but set the metric to 1.
Volia, internet in the emulator.
I tried following steps , Not sure if it will work for you
1> Delete All emulators in Hyper-v
2> Remove all virtual switches from virtual switch manager
3> Go to Network connections in control panel and manually disable (right click and click disable) all the connection except the one which provides internet.
4> Start the emulator from Visual studio
Something else that seems to also cause an issue is Fiddler.
I had Fiddler open and running (as I was monitoring other HTTP requests), and it was stopping the emulator from connecting.
As soon as I closed Fiddler, the emulator starting connecting perfectly.
Start Hyper-V Manager
Open Virtual Switch Manager
Remove the Windows Phone Emulator Internal Switch from the list and apply changes
After installing Windows Phone Emulator on my Yoga laptop, I immediately had the following problems:
emulator apps cannot reach the internet
host computer internet connection is terribly slow and almost unusable
I was discouraged and thought I would have to do some drastic and desperate acts to fix things, but got lucky with the following steps which completely solved my problems (for now). The steps are verbose (intended for the readers' benefit), but are actually very simple in practice.
....0: Unplugged ethernet cable (to remove it from the equation) but stayed connected to WiFi. Problems still remain but at least there is less complexity now.
....1: In Control Panel / Network Connections / Change Adapter Settings, deleted Network Bridge (required for Step 2 to work).
....2: Opened Hyper-V Manager, right-clicked on the emulator VM item and selected Virtual Switch Manager. Selected "Windows Phone Emulator Internal Switch" and changed the radio button from Internal to External (this was only possible after deleting the Network Bridge (Step 1)).
At this point, the emulator can now connect to the internet (and Control Panel shows WPEIS finally 'has internet access'); however deployment of WP build binary from VS to emulator fails - it just hangs when I try to build-and-deploy from Visual Studio (so a new problem has surfaced (temporarily)).
....3: Returned to HyperV Manager, went back to Emulator VM's Virtual Switch Manager and reverted Windows Phone Emulator Internal Switch from External back to Internal.
I can now successfully build-and-deploy WP build from Visual Studio to emulator. And emulator retains its networking ability. Also the host machine's network connection also returned to healthy.
I hope this helps someone. Good luck!
I went through many of the suggested solutions, also with no luck. What finally worked for me was to fix a vmware warning about guest OS trying to set promiscuous mode for ethernet adapter (http://kb.vmware.com/kb/287).
Try this solution, it works for me (no need of DHCP)
Step 1 - using Hyper-V start the server, once started u can see the two new network adapters added in the (network sharing) page.
Step 2 - go to your visual studio IDE where your application runs, using Emulator run your application, once started try to open IE, it will not connect to internet.
Step 3 - now again come back to network sharing page right click on external adapter which was created newly select properties, hit on sharing tab, now check the two options to have tick mark if not tick that two options and click on OK.
Step 4 - internal adapter which was created newly will be changing the domain name from Unidentified network to your shared Domain name, once changed try to access the IE again in emulator which runs already. now i hope the internet connection works.
Thanks,
Baskar
After spending about 3 days on this i finally got it working. (on Windows 8 using WiFi)
Start Fresh, Remove HyperV, Restart, Install Hyper V, Restart
Open your VS solution and run the emulator.
When prompted for letting the emulator access the internet say yes.
Let the emulator and your project fully load
Shut down the emulator and VS
Open Network and Sharing Centre
Click change Adapter Settings (on the left hand side)
You should have some new adapter created by HyperV, they should be called "vEthernet(...)"
The ones you are interested in are the vEthernet( Virtual Switch) and vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)
Open the properties on your vEthernet( Virtual Switch) and navigate to the sharing tab.
Choose Allow other Network users to connect and choose the vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) as the adapter
Ok the changes, and then open the properties on vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)
Disable Internet Protocol Version 6 and double click on Internet Protocol Version 4
Use the following IP address: 169.254.169.177 Subnet mask:255.255.0.0
Click advanced, under the IP settings tab, assign an interface metric: 1
Open VS and re run your project under and emulator, wait a few minutes for it to load.
Try and open IE within the emulator and confirm you have internet access.
Good luck
After 3 days we have finally solved it. We had to make ip address dynamic. After making it dynamic emulator could reach internet. We didn't have to change anything else.
Good article: http://blogs.msdn.com/b/wsdevsol/archive/2013/10/01/why-can-t-the-windows-phone-emulator-go-online.aspx
I had DHCP reservation on my router, like #robertftw said. I configured a static IP for vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) adapter and everything works.
Disabling the Wifi, and Virtual Wifi inside "Network Connections" worked for me.
My Windows Phone emulator had been assigned an IP address by DHCP on a different Subnet to the one I am using.
Manually assigning an IP address on the same subnet as my PC to the vEthernet port created by Hyper-V resolved this issue.