Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hosted Wifi Network (through laptop) suddenly not working


  • Please log in to reply
6 replies to this topic

#1 defianthermit

defianthermit

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:12 AM

Posted 24 August 2016 - 04:05 PM

Hey guys,

I've been having a problem for a few days and have been looking everywhere for a solution with no luck thus far. I recently moved in with my girlfriend and my internet plan didn't include a router. Since she's not going to stay here for long (just til the end of the year), I've been routing the net from the cable modem through my laptop so all of our devices can be connected.
Problem started happening when she had to plug the cable on her laptop one day as I was away for uni and we simply cannot take the damn cable out of it. I'm working on getting a replacement one before I can try bruteforcing it, but I'm also worried that it might break the port.

In any case, we've been using her laptop as the router for the last few weeks, but somehow Virtual Router Manager doesn't work here (it fails to recognize the virtual mini port), so I'm manually routing it using the netsh wlan script. The problem is that it simply stopped working last week and I have no idea why.
The network is still being set succesfully and all devices can connect to it, but they can't connect to the internet. Doing a adapter troubleshooting, windows says it's because it doesn't have a valid IP connection. I've since looked for solutions for this online, but none of them fit my problem.

I've tried the netsh reset log commands with to no avail. The computer connected to the wired modem has perfect connection (I'm currently writing from it), it's just the hosted wifi that doesn't work.

Thoughts?
Thank you so much in advance!



BC AdBot (Login to Remove)

 


#2 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:12:12 AM

Posted 24 August 2016 - 05:45 PM

What modem/router is the laptop connected to? Do you have the port configured to used the old IP?



#3 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:10:12 PM

Posted 25 August 2016 - 12:10 AM

Please post the results of a ipconfig /all from this laptop for review



#4 defianthermit

defianthermit
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:12 AM

Posted 25 August 2016 - 07:18 AM

What modem/router is the laptop connected to? Do you have the port configured to used the old IP?

 

The laptop is connected to a Motorola BZE modem (I can't make the specific make, but I'll try figuring it out). It is, unfortunately, not a router. 

 

 

Please post the results of a ipconfig /all from this laptop for review

 (Sorry it's in portuguese :/) The hosted network is Adaptador de Rede sem Fio Conexão Local* 3:

 

Microsoft Windows [versão 6.3.9600]
© 2013 Microsoft Corporation. Todos os direitos reservados.

C:\Windows\system32>ipconfig /all

Configuração de IP do Windows

Nome do host. . . . . . . . . . . . . . . . : Luara
Sufixo DNS primário . . . . . . . . . . . . :
Tipo de nó . . . . . . . . . . . . . . . . : misto
Roteamento de IP ativado. . . . . . . . . . : não
Proxy WINS ativado. . . . . . . . . . . . . : não

v

Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Adaptador Virtual de Rede Hospe
dada da Microsoft
Endereço Físico . . . . . . . . . . . . . . : 52-08-B1-88-29-E7
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim
Endereço IPv6 . . . . . . . . . . : 2804:14d:8087:dad:c4ef:a8f7:55ec:e7fc(Pre
ferencial)
Endereço IPv6 Temporário. . . . . . . . : 2804:14d:8087:dad:9934:c7e6:5cb3:e3
5a(Preferencial)
Endereço IPv6 de link local . . . . . . . . : fe80::c4ef:a8f7:55ec:e7fc%10(Pr
eferencial)
Endereço IPv4 de Configuração Automática. . : 169.254.231.252(Preferencial)
Máscara de Sub-rede . . . . . . . . . . . . : 255.255.0.0
Gateway Padrão. . . . . . . . . . . . . . . :
IAID de DHCPv6. . . . . . . . . . . . . . . : 491915441
DUID de Cliente DHCPv6. . . . . . . . . . . : 00-01-00-01-1B-BF-36-48-EC-F4-B
B-F9-2A-CA
Servidores DNS. . . . . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS em Tcpip. . . . . . . . . . . . . . : Habilitado

Adaptador Ethernet Conexão de Rede Bluetooth:

Estado da mídia. . . . . . . . . . . . . . : mídia desconectada
Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Dispositivo Bluetooth (Rede Pes
soal)
Endereço Físico . . . . . . . . . . . . . . : 10-08-B1-88-29-E8
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim

Adaptador de Rede sem Fio Conexão Local* 2:

Estado da mídia. . . . . . . . . . . . . . : mídia desconectada
Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Adaptador Virtual Direto Wi-Fi
da Microsoft
Endereço Físico . . . . . . . . . . . . . . : 12-08-B1-88-29-E7
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim

Adaptador Ethernet Ethernet:

Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Realtek PCIe FE Family Controll
er
Endereço Físico . . . . . . . . . . . . . . : EC-F4-BB-F9-2A-CA
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim
Endereço IPv6 . . . . . . . . . . : 2804:14d:8087:1000:25e1:f19f:f015:3268(Pr
eferencial)
Concessão Obtida. . . . . . . . . . . . . . : quinta-feira, 25 de agosto de 2
016 09:11:32
Concessão Expira. . . . . . . . . . . . . . : sexta-feira, 23 de setembro de
2016 18:10:09
Endereço IPv6 de link local . . . . . . . . : fe80::8426:43b6:4cd1:6968%4(Pre
ferencial)
Endereço IPv4. . . . . . . . . . . . . . . : 186.223.215.60(Preferencial)
Máscara de Sub-rede . . . . . . . . . . . . : 255.255.252.0
Concessão Obtida. . . . . . . . . . . . . . : quinta-feira, 25 de agosto de 2
016 09:12:58
Concessão Expira. . . . . . . . . . . . . . : quinta-feira, 25 de agosto de 2
016 12:12:57
Gateway Padrão. . . . . . . . . . . . . . . : 186.223.212.1
Servidor DHCP . . . . . . . . . . . . . . . : 189.7.80.20
IAID de DHCPv6. . . . . . . . . . . . . . . : 166524091
DUID de Cliente DHCPv6. . . . . . . . . . . : 00-01-00-01-1B-BF-36-48-EC-F4-B
B-F9-2A-CA
Servidores DNS. . . . . . . . . . . . . . . : 2804:14d:8012:672:189:7:80:22
2804:14d:8011:672:189:7:80:42
189.7.80.22
189.7.80.42
NetBIOS em Tcpip. . . . . . . . . . . . . . : Habilitado

Adaptador de Rede sem Fio Wi-Fi:

Estado da mídia. . . . . . . . . . . . . . : mídia desconectada
Sufixo DNS específico de conexão. . . . . . : mshome.net
Descrição . . . . . . . . . . . . . . . . . : Dell Wireless 1705 802.11b/g/n
(2.4GHZ)
Endereço Físico . . . . . . . . . . . . . . : 10-08-B1-88-29-E7
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim

Adaptador Ethernet VirtualBox Host-Only Network:

Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet A
dapter
Endereço Físico . . . . . . . . . . . . . . : 0A-00-27-00-00-00
DHCP Habilitado . . . . . . . . . . . . . . : Não
Configuração Automática Habilitada. . . . . : Sim
Endereço IPv6 de link local . . . . . . . . : fe80::41f0:db66:d3e7:bdd3%9(Pre
ferencial)
Endereço IPv4 de Configuração Automática. . : 169.254.189.211(Preferencial)
Máscara de Sub-rede . . . . . . . . . . . . : 255.255.0.0
Gateway Padrão. . . . . . . . . . . . . . . :
IAID de DHCPv6. . . . . . . . . . . . . . . : 352976935
DUID de Cliente DHCPv6. . . . . . . . . . . : 00-01-00-01-1B-BF-36-48-EC-F4-B
B-F9-2A-CA
Servidores DNS. . . . . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS em Tcpip. . . . . . . . . . . . . . : Habilitado

C:\Windows\system32>


Edited by defianthermit, 25 August 2016 - 07:19 AM.


#5 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:12:12 AM

Posted 25 August 2016 - 04:09 PM

To clarify, you had modem (probably SB6120) connected to your laptop(1) and using it as a wireless AP. Girlfriend unplugged ethernet from laptop 1 and connected to laptop 2. It got stuck in laptop 2 so you are using that laptop as AP. 

 

First thing I would do is disable the Virtual Router Manager(VRM) on laptop 2 then reboot the modem. See if you get a valid public IP. If you don't, try pinging 192.168.100.1 or bringing that IP up in a browser. If you do get a good IP, try re-enabling the VRM and see if that fixes it. Also, is the netsh wlan script to renew the DHCP lease because you can't enabled it on VRM?

 

Spoiler

 

I think this is some how connected to the public IP changing and it breaking the VRM connection. Does your ISP happen to allow static IPs? Last, I would disable IPv6 routing. No good way to firewall it and it increases traffic.



#6 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:10:12 PM

Posted 26 August 2016 - 09:13 AM

from the ipconfig

Roteamento de IP ativado. . . . . . . . . . : não

 

this should be set to sim (yes)

 

Basically your settings are wrong.  There is no routing between the interfaces.  The virtual/wifi interface is set to dhcp [which it should be static] and since there is not dhcp server you are getting a apipa ip address.

 

I would suggest setting this up again from scratch using some of the online tutorials

http://www.windowscentral.com/how-turn-your-windows-10-pc-wireless-hotspot

 

BTW its ok if your public ip changes as it should since you are set to dhcp for that interface



#7 defianthermit

defianthermit
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:12 AM

Posted 27 August 2016 - 08:11 AM

To clarify, you had modem (probably SB6120) connected to your laptop(1) and using it as a wireless AP. Girlfriend unplugged ethernet from laptop 1 and connected to laptop 2. It got stuck in laptop 2 so you are using that laptop as AP. 

That's it. I can't get the cable out of her laptop, even with pliers and a screwdriver on the plastic lid.

 

 

 

First thing I would do is disable the Virtual Router Manager(VRM) on laptop 2 then reboot the modem. See if you get a valid public IP. If you don't, try pinging 192.168.100.1 or bringing that IP up in a browser. If you do get a good IP, try re-enabling the VRM and see if that fixes it. Also, is the netsh wlan script to renew the DHCP lease because you can't enabled it on VRM?

I'm getting a valid public IP (I believe) and I can ping the modem just fine. The issue with VRM is that when I select the network I'm going to route, it gives me the following warning http://imgur.com/a/0TAqk

It then "starts", but without a hosted network in the shared connection tab.

 

The DHCP option you quoted from the ipconfig is from the virtualbox host-only net. I don't believe that has anything to do with me trying to route, does it?

 

 

from the ipconfig

Roteamento de IP ativado. . . . . . . . . . : não

 

this should be set to sim (yes)

 

Basically your settings are wrong.  There is no routing between the interfaces.  The virtual/wifi interface is set to dhcp [which it should be static] and since there is not dhcp server you are getting a apipa ip address.

 

I would suggest setting this up again from scratch using some of the online tutorials

http://www.windowscentral.com/how-turn-your-windows-10-pc-wireless-hotspot

 

BTW its ok if your public ip changes as it should since you are set to dhcp for that interface

Got it. However, retracing everything I've done and following the tutorial (which is 100% exactly what I've been doing thus far) still gives me the same result. Any idea about what's causing the IP routing to be turned off? There aren't really many settings I can temper with using the netsh commands :/






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users