Drive life WiFi sharing open failure resolution

With the release of WiFi sharing, a large number of users have been removed from the mobile terminal traffic is not enough to worry about things, but also a small number of users feel very depressed is the emergence of a small number of users mobile terminals can connect their shared WiFi hotspot but do not normally online, This article collates the most complete drive life WiFi sharing open failure problem solution, hoping to help you better use the drive life of WiFi sharing function.

To resolve the problem:

Mobile terminals can normally connect to their own shared WiFi hotspot, but the mobile terminal is not normal access to the Internet, or mobile terminals always get no IP address;

Network environment: (If your network environment does not meet any of the following conditions, please google)

The name of the network card is defined beforehand so that you can't tell each card function: (notebook wired network card is defined as "local connection", wireless network card is defined as "Wireless Internet connection", PPPoE broadband dial-up Virtual NIC is defined as "broadband connection", WiFi virtual network card is defined as "Wireless network Connection 2"

1, the notebook through the local connection, the use of DHCP or manually configured IP Internet access; "Multiple rental or dormitory sharing network"

2, the notebook through the broadband dial-up Internet access; "More and more of their own specialized from the operator to apply for broadband"

3, notebook through wireless/wifi hotspot, but wireless/wifi hotspot at the same time can only have a terminal access; "Many occur in the use of wireless router/cmcc/3g, etc."

Solution Rollup:

1, notebook through the local connection, the use of DHCP or manually configured IP address directly to the Internet, open the drive life WiFi function, mobile terminals can connect their open WiFi hotspot, but the mobile terminal is not normal access to the Internet;

Solution:

I right-click the network----properties----Change the adapter settings, open the Network Configuration dialog box (if you are an XP system, right-click the Network Neighborhood---"Properties") This is the author's web configurator option;

II Right-click the "Local Area Connection"---"Properties"---Select the corresponding shared network card specific configuration see screenshot;

III quit driving life, and then reopen drive life, turn on WiFi and confirm the WiFi status that drives life;

Then you can test the network of the mobile terminal is normal!!!!!!!!!!!

Do not know if you have not noticed, set the network card share after the icon state of the network card will be changed, let us look at!

The local connection icon appears with a "shared";

2, notebook through the broadband dial-up network, open the drive life WiFi function, mobile terminals can connect their open WiFi hotspot, but the mobile terminal is not normal internet;

Attached: For a lot of broadband dial-up and that is, PPPoE dial-up Internet access, because all of his data is still connected through the local, different operators settings may vary, some users will get a local connection to an address, some users may get to a 169.254.0.0/16 address , you do not need to take care of him, as long as your notebook Internet must first broadband dial-up, then your internet can be understood as a broadband dial-up

Solution:

I right-click the network----properties----Change the adapter settings, open the Network Configuration dialog box (if you are an XP system, right-click the Network Neighborhood---"Properties") This is the author's web configurator option;

Obviously if in this state, drive life sharing WiFi function in mobile terminals is not normal internet, and so-called mobile terminals can connect their definition of WiFi hotspot but not normal internet, now need to make a change;

II Remove the network share from the local connection; (because the NIC share is wrong)

Right-click Local Area Connection---Properties-remove Internet Connection Sharing options specific configuration see screenshot

III manually configure the shared network card, right click on the "Broadband dial-up"---"Properties"---"sharing" to choose the corresponding shared network card, here to remind, configure the network card sharing after the proposed disconnect broadband dialing, and then dial again;

IV quit driving life, then reopen drive life, turn on WiFi and confirm the WiFi status that drives life;

Then you can test the network of the mobile terminal is normal!!!!!!!!!!!

Do not know if you have not noticed, set the network card share after the icon state of the network card will be changed, let us look at!

The broadband connection icon appears with a "shared";

3, notebook through wireless/wifi hotspot, but wireless/wifi hotspot can only have a terminal access, mobile terminals can connect their open WiFi hotspot, but the mobile terminal is not normal internet;

Attached: The author here is through the wireless router sharing the Internet, using 3G may also be another virtual out of a network card, configuration a little different is the need to configure the network card, choose 3G Virtual network card to configure it, because I do not have 3G environment, so did not simulate this test, Use CMCC mode Internet and wireless router no difference;

Solution:

I right-click the network----properties----Change the adapter settings, open the Network Configuration dialog box (if you are an XP system, right-click the Network Neighborhood---"Properties") This is the author's web configurator option;

Obviously if in this state, drive life sharing WiFi function in mobile terminals is not normal internet, and so-called mobile terminals can connect their definition of WiFi hotspot but not normal internet, now need to make a change;

II Remove the network share from the local connection; (because the NIC share is wrong)

Right-click "Broadband Connection"---"Properties"-Remove Internet Connection Sharing options specific configuration see screenshot

III re-configure the shared network card manually, right-click the wireless network connection---properties---"Share" to select the corresponding shared network card;

IV quit driving life, then reopen drive life, turn on WiFi and confirm the WiFi status that drives life;

Then you can test the network of the mobile terminal is normal!!!!!!!!!!!

Do not know if you have not noticed, set the network card share after the icon state of the network card will be changed, let us look at!

The Wireless network connection icon appears with a "shared";

Important Reminders:

1, some users are reflected in the education Network or campus network to open the drive life WiFi function, the notebook network directly disconnected, dial-up unsuccessful

This phenomenon I do not understand the real principle, here is just a guess, is like those operators, in order to make an account can only give a terminal or limited number of terminals to provide services, on their devices have integrated third-party software or additional inspection system, such as the telecommunications of many cats an account can only use several terminal number, more than the number of terminals to break the network for a few minutes or can not open the Web page. They are generally through these third-party software to monitor the access to limit the user's shared Internet behavior such as the use of proxy or NAT Internet, such as the domestic have "network Vanguard" is to do this work, and then drive life WiFi function just using NAT technology, This led to his above monitoring software to monitor the following users have to use a shared machine, directly shut down the user's network, resulting in the user to open the drive life WiFi function on the network can not be used normally. If there is any knowledge of this situation and know its exact principle, I hope you can share it! Thank you first!

2, since most of the WiFi sharing software is charged, before the drive Life WiFi feature has not been released

The author has always opened the WiFi share through a bat script, which also shares the author's WiFi sharing script, but the stability of this script does not drive the life of the reliable, often appear to get the IP address, here recommended to use the drive life WiFi function;

3, the user opens the drive life WiFi sharing, but the mobile terminal has not obtained the IP address for a long time;

(the author also found that many times when the mobile terminal did not get the IP address is due to WiFi open successfully but the network card sharing enabled failed!)

Here's how the user in the drive life client confirms that the mobile terminal has not obtained the IP address;

If the user opens the drive life WiFi share, the display status is as follows, then on behalf of the mobile terminal to obtain the IP address, but the temporary IP address has not been successful; If you keep this state, the IP address on behalf of the mobile terminal fails, and you need to manually configure the IP address.

Solution:

I first open the WiFi virtual network card to view its IP address configuration information;

Right-click "Wireless network Connection 2"---"Status"---"Details" see screenshots

The IP address and subnet mask are recorded;

II then manually set the IP address at your mobile terminal under the name of your wifi hotspot;

IP address configuration: 192.168.1.137.2-192.168.1.137.254, in fact, as long as not 192.168.137.1 can, if you have multiple mobile terminals each mobile terminal IP must be unique;

Gateway Configuration: 192.168.137.1

Subnet Mask: 255.255.255.0 is consistent with the subnet mask of the laptop WiFi virtual network card;

Domain Name server: Recommended settings: 8.8.8.8, if you know the other more stable DNS can also configure other!

4, a small number of users regardless of the use of driving life WiFi sharing or scripting is sharing unsuccessful;

(Drive life WiFi sharing prompts WiFi share to open failed; script "netsh wlan start hostednetwork" says the network cannot be hosted and the device is not functioning.) )

Solution:

1 First verify that your wireless network card supports WiFi sharing; "Some of the early wireless cards didn't support WiFi sharing, for example, one of my ThinkPad T61 doesn't support WiFi sharing, but it's not a big problem to support WiFi in 2012 and beyond. can go to Google or official technical support to confirm "

2 Disable the wireless card, and then enable the wireless network card;

3 Quit driving life, and end driving life DTLService.exe process, (preferably restart the computer) and then open the drive life try!;

4 Restart the Wireless WiFi service and reboot the computer, the wireless service name that needs to be restarted is: WLAN AutoConfig; Restart Service steps: Start----Run---Enter "services.msc", Open the Service dialog box, and find the name WLAN AutoConfig Service, right click on this service, choose Reboot!

5 temporarily shut down all anti-virus software of the computer and try again!

5, Drive Life WiFi function open, all normal, mobile terminals can also be normal access to IP, but is not on the network;

Solution:

1 first confirm that the network card sharing is normal, all normal to enter the next step; (See the above section for specific details)

2 Check the installation of anti-virus software, shut down the local computer anti-virus software, there are users to reflect the 360 traffic firewall LAN protection module may lead to this situation;

Note: Drive Life 6 Remove the WiFi sharing module, add 160wifi to the tool encyclopedia, and turn on the WiFi hotspot more simply.