My selfhosted WCF wervice works fine with any browser on the domain, and also with a WinForm client. In a Windows Phone 8 app I can create Service References OK. Trying to consume the service from within the app running in the emulator it causes the System.Net.WebException: The remote server returned an error: NotFound.
What I have done:
allowed URL registration
firewall inbound rule for the specified port
enabled WCF Services, HTTP Activation (Windows Features)
In the Hyper-V settings for the Emulator it lists 4 network adapters: Windows Phone Emulator Internal Switch, Intel...Gigabit Network Connection Virtual Switch and 2 VMware related switches.
Can the presence of VMware cause this problem? (I have stopped the (4) VMware related services.)
What else can I check or do?
After a full day of working on the issue (not knowing anything about Hyper-V didn't help) I (we) worked out the problem:
In this particular, but quite common setup, both Ethernet and Wireless Network Adapters were enabled, and Ethernet ranked above Wireless, as you do to give the cable connection precedence over wireless when both are available.
Even though the Ethernet cable was disconnected at the time the Emulator was started/created, Hyper-V created Ethernet as the only external Network adapter to use. But the because there was no cable, the adapter was physically disabled and the local WCF service (which was running on the wireless network) could not be found.
Disabling the Ethernet (hardware) adapter (Control Panel), then deleting the emulator, and reconstructing it by launching a phone app in VS fixed the connection issue. On inspection the Wireless adapter is then assigned as the external adapter ("Virtual Switch") to use.
Hope that helps someone.
Related
I have connected to the internet through a modem named QUBEE which shows as the connection 'Ethernet 2'. However, I have a tab and kindle fire. so, I decided to create a virtual network or hosted network in my laptop. So, I created a hosted network with a numeric pass key (8-digits). The authentication type is WPA2-Personal. I shared the net of Ethernet 2 with it. However, i tried with both my tab and kindle fire, but it shows 'Authentication problem'.
Both of the kindle fire and tab remains in 'Obtaining IP address...' state a lot of time.
One thing I noticed that, when the device is not connected to the virtual network, its network strength remains strong. but it tries to connect, it becomes poor.
Another thing is that the authentication type of that recognize by both tab and kindle fire is WPA2 PSK. where the laptop has WPA2-Personal.
My laptop configuration is i5#2.5GHz, Windows 8.1, RAM: 6.00GB, Lenovo G480.
Thanks in advance for trying to help me.
I have been trying to setup a Win7 VM on Hyper-v that connects to the internet through my Win 8 host machine.
I can't seem to figure out why the VM can't ever get passed limited connectivity. Any ideas?
NO sure why but all I had to do was Disable/enable the vEthernet adapter and everything worked great!
Check that you have a Virtual Switch with an "External Network" using the Virtual Switch Manager.
The other network types offer VM isolation. If your VM is on an "Private Network" it can only talk to other VMs on the server. The "Internal Network" allows VMs can talk to other VMs and to the host.
In contrast, an External Network allows the VM to contact machines on the network that the host is attached to.
I worked on this issue for a while myself after upgrading to Windows 8.1 and losing connectivity. Added and removed the adapter to no avail. The solution was to upgrade the VM's Integration Services.
I had the same issue because my DHCP settings on my guest VM was setup wrong.
So check the DHCP setting if they are on obtain automatically.
Control Panel\Network and Internet\Network Connections
Network adapter properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties ->
Obtain DNS server address automatically
I have had great success with Hyper-V and windows 8 and windows 10 virtuals using external switches with a Windows 8.1 host. Unfortunately I could not get the external switch to ever work on windows xp virtual running under Hyper-V. Instead, after reading a lot of sites/suggestions, I followed this guide to bridge an internal virtual switch (with Hyper-V legacy network adapter for XP) to the host wifi. I hope this saves someone else some time when working on an XP virtual.
Using Hyper-V with a Wireless Network Adapter
I'm trying to develop an interface to an application that doesn't run on Windows 8. Hence, I've created a VM with Windows 7 running the integration service and another service running on the Windows 8 host.
I have three Virtual Network scenarios configured for Hyper-V: Wireless, Shared and Internal. Where Wireless allows all VMs and the host to connect to a wireless network (External), Shared let's the VMs connect through the host via a VPN (Internal) and Internal creates a network within the host where the VMs don't have network access (Private).
When I'm in Wireless (External) mode and there's a wireless network to connect to, everything works fine as if I were testing using to physical PCs on a wireless network. However, today I had a situation where I wasn't connected to a network but still wanted to do some testing and I could not get the VM to see the host and vice-versa. This scenario was quite straight forward to create on VMware which I used before switching to Hyper-V...
Has anyone managed to make Client Hyper-V VMs and the host communicate without a network? Can you guide me how to set it up?
Wireless networking under Windows 8 Hyper V can not communicate with multiple VM the Wireless NIC is assign to only one Hyper V internet connection,
Meaning only one Hyper V can connect to the Internet preventing others from connecting unless you use multiple Nic's Wireless Network Cards or USB Wireless Network.
It is only after you restart or shut down your computer that Hyper-V problems start.
So if you can not connect any of your Hyper VMs then you problem could be due to a shutdown error that Hyper-v in counted Try restarting the whole computer then Hyper- VMs your problem should fix itself.
Might want to try this. I am having similar problems as you and all signs point to this particular solution working, but for me it is not. Might help you, though.
http://blogs.technet.com/b/doxley/archive/2008/07/07/disconnecting-hyper-v.aspx
The solution that DID end up working for me was this:
http://www.elmajdal.net/Win2k8/Enabling_Wireless_Network_For_Hyper_V_Virtual_Machine.aspx
How do I access a Windows Azure WCF Services on a Windows Phone 7 Device on a local development machine. I've tried my local IP and also switched off my firewall. Nothing helps. Do we have any cool hacks for that?
Ok so you're trying to access the emulator on your development machine with a real Windows Phone device? Officially this isn't supported, since the emulator only accepts local connections. But you can use the port forwarding features available in Windows to bypass this limitation:
netsh interface portproxy add v4tov4 listenport=8081 connectport=81 connectaddress=127.0.0.1
Now, instead of having your WP7 connect to yourip:81 you should configure the device to connect to yourip:8081.
I'm working with a PocketPC vm for development over here.
I can get the virtual device to connect to the internet, but I can't get it to connect to a web service on my local (host) machine.
I've tried the machine name and my IP address, different ports, but no luck.
Anyone else have this issue?
EDIT: I have an actual device at my machine as well. When docked I don't have this problem with the real device, just the emulated one.
I have not had the specific issue. But, the best way I've found to deal with these issues when using WCF is to enable tracing and see what the error messages are.
If you are connected via ActiveSync, you can connect to the name "ppp_peer".
This name will always resolve to the machine connected via active sync.
Figured it out when I read this article:
http://www.betterthaneveryone.com/archive/2008/08/31/getting-network-access-on-the-windows-mobile-emulator.aspx
The device has to be docked. You need to use the Device Emulator Manager to dock the device. Also note: you can only have one device docked at a given time.
Once the device is docked, you should see the Windows Mobile Device Center display. Find the running device (look for the green arrow), right-click and select Cradle. Remember, only one device can be cradled/docked at a time. If you have a real device that is cradled already, you cannot cradle an emulator.
In Windows Mobile Device Center -> Mobile Device Settings -> Connection Settings: Check "Allow connections to one of the following:" and select DMA in the dropdown.
On the emulator: File->Configure->Network. Make sure a valid network device is selected.
From the emulated OS: Start Menu -> Settings -> Connections -> Connections -> Advanced -> Select Networks. Make both drop-downs My ISP.
That should be it. To test, load Internet Explorer, browse to StackOverflow.com. Next, browse to a web page on your local machine.