Wifi hotspot connected successfully but my phone could not access the Internet

I've created the Hotspot named "20140329" (shown in the picture below) using the "netsh" commands. My phone is connected successfully, but it could not broswe or have access to the internet. I downloaded a ping tool on my phone. It could not ping any websites.I did the same operation on my windows 7 system, it works well.

What I've done for the question:

  1. google 'win8.1 hotspot connected no internet connection', I could not get useful webpages.
  2. find a similar question asked before:wifi hotspot connected successfully but no internet connection .I tried the way described in the answer(shown in the second picture), it didn't work.

I've no idea what I should do now. What could I do to make my phone have access to the internet? Could you help me please? Thanks a lot.

second picture



  • Edited by Xinzhen Sunday, March 30, 2014 2:13 AM
March 29th, 2014 4:08pm

Hi

According to your description,I think we need to check your setting for wifi hotspot.

First,We need to run the following command to verify that your network interface supports virtualization.

netsh wlan show drivers

If Hosted network supported says Yes,please follow the steps as mentioned in the article below.

http://www.redmondpie.com/how-to-set-up-wireless-ad-hoc-internet-connection-in-windows-8/

Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Re

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2014 9:37am

Thank you for your answer.

I've tried the command "netsh wlan show drivers", and the result is "Hosted network supported : Yes".I've also tried the way described in the article, and it doesn't work.

Thanks! I've decided to give up..

April 2nd, 2014 5:21am

Hi Xinzhen,

I found a issue about your setting.


As the above picture ,we should select the ad hoc connection under Home networking connection.

In general,it is a wireless card(Microsoft Virtual Wifi Miniport Adapter).

Please follow the step below to check the result.

1.Press Win+R,and type ncpa.cpl,press enter.

2.In the pop-up window,right-click Vnet-PPoe5,and select Propertices.

3.Then,click sharing Tab,and check "Allow other network users to connect through this computer's Internet connection".

4.On the home networking connection,select your Microsoft Virtual Wifi Miniport Adapter.

If the issue persists,please use ipconfig /all command to list the detail IP information.
And then,post this information here so that we can help me analyze them.

Keep post.

Regards,


Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2014 3:39pm

Thank you so much for discovering the minutest detail.

 I've checked "Allow other network users to connect through this computer's Internet connection". I found that the "Microsoft Virtual Wifi Miniport Adapter" was selected.  :-(

I think the issue you found is the point in high probability. I noticed that everytime I used the command"netsh wlan start hostednetwork", the "Network and Sharing center" showed the picture below at first, while after four or five seconds, the  state of "20140329" returned to the picture I've shown in my original question before.

I typed the command "ipconfig/all >initial.txt" as soon as I used the command "netsh wlan satrt hostednetwork", and typed the command "ipconfig/all >returnState.txt" as soon as I found the state of "20140329" returned.

To my disappointment, the content of "initial.txt" is the same as "returnState.txt",as shown below.Hope it helps.


Windows IP Configuration

   Host Name . . . . . . . . . . . . : XinOfTheWorld-PC
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

PPP adapter Vnet_PPPoE:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Vnet_PPPoE
   Physical Address. . . . . . . . . : 
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 240e:ec:111:655c:f8a8:2eb7:2539:5d9e(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::f8a8:2eb7:2539:5d9e%62(Preferred) 
   IPv4 Address. . . . . . . . . . . : 180.111.99.63(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : fe80::a19:a6ff:fece:57ad%62
                                       0.0.0.0
   DHCPv6 IAID . . . . . . . . . . . : 937967858
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-C5-09-06-E8-40-F2-EE-A1-2A
   DNS Servers . . . . . . . . . . . : 240e:5a::6666
                                       240e:5a::8888
                                       218.2.2.2
                                       218.4.4.4
   NetBIOS over Tcpip. . . . . . . . : Disabled

Wireless LAN adapter * 12:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft
   Physical Address. . . . . . . . . : 52-12-7B-70-DB-DC
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::795d:eaf2:f6d:846d%25(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 374477435
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-C5-09-06-E8-40-F2-EE-A1-2A
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter :

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : TAP-Win32 Adapter V9
   Physical Address. . . . . . . . . : 00-FF-BE-8B-14-5E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter * 1:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct
   Physical Address. . . . . . . . . : 12-12-7B-70-DB-DC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter :

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek PCIe GBE
   Physical Address. . . . . . . . . : E8-40-F2-EE-A1-2A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a993:d42b:d13f:7566%4(Preferred) 
   Autoconfiguration IPv4 Address. . : 169.254.117.102(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 166215922
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-C5-09-06-E8-40-F2-EE-A1-2A
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter WLAN:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Qualcomm Atheros AR9285 Wireless Network Adapter
   Physical Address. . . . . . . . . : 00-12-7B-70-DB-DC
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{3AB30B7C-A0BA-43D3-899C-03A162E1EF44}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{2B9DCB00-F5DB-4706-9663-F54BCC393152}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{38566462-D3F6-4C83-AAE5-B807CD870272}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Thank you. Keep post.

Regards,

April 4th, 2014 10:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics