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.
Related
How to enable Hyper-V to connect VPN for external internet access in Windows 8?
I'm trying to run Windows phone 8 app using emulator, and while see app in emulator it doesn't connect the VPN to access internet.
Please advice.
Thanks.
MSDN has a troubleshooting page for the Windows Phone 8 emulator. Perhaps you can find related info there. Something like this might help:
Cannot connect to Internet destinations
The Windows Phone 8 Emulator uses the HTTP proxy settings from the host computer. If you can’t access Internet resources from the emulator, check with your IT administrator to make sure that your proxy settings will work with the emulator.
If your network’s proxy servers are unavailable or malfunctioning, it might be possible to restore connectivity for the emulator by disabling automatic proxy detection on the host computer. However this only works in certain network configurations.
To disable automatic proxy detection on the host computer
On the host computer, open Internet Options from the Control Panel. The Internet Properties dialog box opens.
In the Internet Properties dialog box, click the Connections tab.
On the Connections page, click the LAN settings button. The Local Area Network (LAN) Settings dialog box opens.
In the Local Area Network (LAN) Settings dialog box, deselect all the check boxes. Click OK twice to close both dialog boxes.
Restart the emulator and retry the connection.
Also this MSDN blog-post can be helpful: Why can’t the Windows Phone Emulator go online?. Useful part of the article:
As you see, clicking the “>>” on the bar parallel to the Emulator will open a small window with 4 tabs. The last tab is for “Network”. To explain in simpler terms, there are two adapters here – one is for internal use by Emulator and other is for external network connectivity. Each adapter will have an IP address (IPv4) associated with itself. The one of our interest is under Adapter #2.
I have erased out the IPv4 address that is assigned to Adapter #2 (Yellow box), but you find that the IP assigned here starts with 169.254.x.x…., then Bingo! - we have figured out the problem. How?
The IP addresses starting with 169.254.x.x …. Are usually the self-assigned default addresses to a device and not really helpful to get the device to go online. This IP should either be a static IP or the one assigned by the DHCP server (if you have one in the environment) for the device to be able to connect to external networks.
Hope this helps.
When I click the send button for sending my app in Application Loader, it is waiting for a response (sent API usage to iTunes Connect, waiting for response) and waiting without error. I am getting a message "the network connection was lost" after a couple minutes. I tried another network connection but the issue was not resolved. Could the issue be on iTunes network?
It should just work if you quit Application Loader, then re-open it.
To submit an application to iTunes Connect, your Mac always need to be up to date, or you will be able to get errors. To do this click on Apple's logo > Software Update. I was having the same problem, and it solved for me. Cheers =)
I had to force quit and the re-open to make it work.
A normal restart did not work, nor did a restart of my Mac. Very weird.
Make sure your iTunes Connect user has admin privileges. I had it set at Technician and everything looked like it was working but it would hang on the "Sending API Usage to iTunes".
None of the above suggestions work for me. Likely the real cause is physical and related how Application Loader is using the internet. I have ADSL connection with a Netgear modem/router assigning each device at home a fixed IP address according to the mac address of the network interface of each device. I had noticed that when Application Loader is uploading, my Windows PC could not connect to the internet. However, if in Mac mini I use Safari doing various things like watching video, my Windows PC can access internet.
Even stranger, when Application Loader is uploading, the modem/router could easily lost connection to the internet, as I could see from the LED lights of the modem. The connection is lost randomly at any progress of uploading the 20 MB file.
So I had turned off Windows PCs, iPads, iPhones and Android device at home, so Mac mini is the only device using the Internet, the Application Loading has finally been able to upload the app successfully in one go.
My guess is, my home phone line has some noise, and Application Loader is using the internet aggressively particularly the up link, so stressing out the modem, then causing other devices like my Windows PC lost connection, not even able to resolve host.
So my working solution is to make Mac be the only device using the Internet, given that the internet connection is already in poor condition with noise, near the edge of losing connection.
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.
I don't know why? Whenever I install AOL desktop (9.5, 9.6, 10.0) on my computer and I'm connected to the internet using cable, every thing is ok. I can browse websites and sign in to AOL.
But whenever I connect to the internet using my wireless network at home, I can not sign in to AOL, but I can still browse the web.
My wireless network uses WPA2-Personal with AES encryption type.
I always get the AC-3000 error message whenever I want to sign into AOL. None of AOL solutions could be useful to solve this.
What do I have to do ?
You didn't mention what version of windows you are using but my suspicion would be that if you are on Windows Vista/7 then the cable connection is identified as "home" or private and that the wireless connection is identified as public and the AOL connection (which used to be on port 5190 IIRC) is getting blocked as a result.
If I am right, to change what apps have access on which network types, you can follow the instructions here:
http://www.addictivetips.com/windows-tips/how-to-stop-a-program-from-gaining-unsolicited-internet-access-in-windows-7/
Although it is about how to stop a program from accessing the internet, it works just as well the other way around ;)
You could use netstat to determine what the successful connection to AOL is on the cable set up in terms of destination and IP and then attempt a simple telnet connection to the same address/port on the wireless set up to verify if this is blocked at the network/port level or if it is blocking the application (usually referred to as ACS). If the telnet connection succeeds and does not timeout, then it is an application level restriction which you will need to fix .
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.