Why does my network adapter have to be reset so often?

[Naio]

I'm running windows 7 starter.

Most times, not every time, when I connect to a wifi network (say, at a campground), and then later I connect to my phone's hotspot, the computer connects to the hotspot ok but then says 'no internet access'. I run the troubleshooter, and it almost always finds the same problem: It needs to reset the wireless network adapter. It does that, and then it's fine. But the whole process takes about 10 minutes.

This has happened with two different model phones and numerous wifi systems.

Anybody have any ideas for a more permanent solution?

[Ourhomeonwheels]

I had that problem with Win7. Try opening the Network Sharing Center. Open change adapter settings and then open the properties screen. If you see 2 Internet Protocol Versions selected (IVP4, IVP6) try unselecting the IVP6. You will probably see several different adapters you may want to do this for all.

What is likely happening is that initially the system is trying to connect using IVP6 but some piece of equipment is not compliant with that protocol so the connection fails until you run the trouble shooter.

This same fix may also work if you are getting the annoying "Windows has detected an IP conflict" message.

Ron

[Naio]

mrgrim007 wrote:
Do the IP config commands work or not? I'm not saying it's a long-term solution, but knowing this part is another piece of the puzzle. You need to try the commands while you're having trouble connecting.

Alright, I FINALLY got a chance to try this, and it works.

(For the past few days, my system has been on unprecedented good behaviour and connected easily no matter how many times I swapped networks.)

SO, now what does this tell y'all?

[mrgrim007]

Typing "ipconfig" alone into a command prompt will show you your IP address. If it's successfully getting one from the phone, it'll most likely be "192.168.1.x" or "192.168.0.x". If it starts with "169." then you're not getting an IP address. You should get an IP address regardless if the phone has internet access.

This is something you can easily check even if the WiFi is down. Just connect to your phone's hotspot and check your IP address.

[Naio]

hawkeye-08 wrote:
I noticed that my Galaxy S5 on ATT takes much longer now (than 6 months ago) to be ready for connections. If I try to connect too soon after activating the hotspot feature, my pc will not get an IP address.

I watch the indicator, so I know when it is ready.. And, of course, I have had this problem with two different model phones.

[hawkeye-08]

I noticed that my Galaxy S5 on ATT takes much longer now (than 6 months ago) to be ready for connections. If I try to connect too soon after activating the hotspot feature, my pc will not get an IP address.

[Naio]

mrgrim007 wrote:

bcsdguy wrote:
I second the post about the problem being in the phone and not the pc. If it is an Iphone it may just be the phone's antenna as they did have some issues with their antennas not being strong enough or so I read awhile back.

One way to test this is to see if the phone can access the internet while the PC is having connection problems. If the phone can access the internet, but the PC can't, there's something going on with the local network (PC IP address, DNS, etc.), not the WAN connection.

Yes, I can and do access the net directly on my phone when the computer won't connect through the phone.

[mrgrim007]

bcsdguy wrote:
I second the post about the problem being in the phone and not the pc. If it is an Iphone it may just be the phone's antenna as they did have some issues with their antennas not being strong enough or so I read awhile back.

One way to test this is to see if the phone can access the internet while the PC is having connection problems. If the phone can access the internet, but the PC can't, there's something going on with the local network (PC IP address, DNS, etc.), not the WAN connection.

[bcsdguy]

I second the post about the problem being in the phone and not the pc. If it is an Iphone it may just be the phone's antenna as they did have some issues with their antennas not being strong enough or so I read awhile back.

[Naio]

Thanks, folks!

I am terribly sorry, I misunderstood the intend of the config commands. I will try them and report back.

Of course NOW, the non-phone wifi is down, so I can't test it :).

[mrgrim007]

On the hot spot, you can try turning off your security (WPA2?) and see if that helps.

You can also try changing the channel it's broadcasting on. Try each troubleshooting step separately.

[magicbus]

Naio wrote:
The problem only occurs when connecting to my phone hotspot, which is normally inches away from the laptop. Would antenna strength really be a factor?

Why do I have this problem with multiple phone hotspots but not with regular wifi's?

My wife sees this often when using her iphone 5s hotspot. So often that she usually asks me to turn on my android hotspot.

On occasion I see this message but within 10 seconds it resolves itself.

Based on my experience I would be looking at the phone as an issue rather than the pc.

Dave

[mrgrim007]

Do the IP config commands work or not? I'm not saying it's a long-term solution, but knowing this part is another piece of the puzzle. You need to try the commands while you're having trouble connecting.

[Naio]

FrankShore, you may be interested to see the results of that test, a few posts up on this page.

mrgrim007 wrote:

Naio wrote:
Bumping this in case anyone has a new idea.

I am kind of surprised to learn that this is not a common problem.

Did the OP try updating the drivers?

Yes, before I started the thread :).

Does renewing the IP address via the IPConfig commands speed up the 10 minute process?

If these don't work we can move on to a different possible solution.

I'm looking for a solution that I don't have to re-implement each time I connect... if possible.

What is next to try?

[FrankShore]

1492 wrote:
What happens when you do the following in WIN 7?

• Hold down Windows Key+R and type CMD and click OK.
  
• Type or copy and paste PING 127.0.0.1 and press your ENTER key.

Does it look like this?

Or are there other characters present? If so, your TCP/IP stack may be corrupt and should be reset by using netsh winsock reset at the Command Prompt. Needs to be run as administrator.

+1

[mrgrim007]

Naio wrote:
Bumping this in case anyone has a new idea.

I am kind of surprised to learn that this is not a common problem.

Did the OP try updating the drivers? Does renewing the IP address via the IPConfig commands speed up the 10 minute process?

If these don't work we can move on to a different possible solution.