I and Jane use Verizon via 4g LTE jetpack mobile hotspot. On both laptops, we have each been experiencing the same problem from time to time. When it happens, it affects both devices. We use: (nearest house and roadway are over 1/4 mile away so I know no one is sitting out in the woods 'borrowing' my signal.)
I turn the jetpack on, it finds signal, shows connections available and normal signal strength and I connect as usual with the laptop. Icon shows that I am connected, but within 5 seconds the hated yellow exclamation point shows up on the connection icon. A click opens the connection dialog box and show I am still connected but no internet access. "Details" shows I am not. Lease expires. I took these screenshots within seconds of connecting. Cycling the jetpack on/off does not help. Note the time and dates on computer clock and the 'expires' time. What is going on?
[This message has been edited by maryjane (edited 07-27-2016).]
I am no expert by any means, but I don't think it is your problem. When you have no internet, it looks like your hotspot is not getting an IPv6 address. I think that should be assigned upstream. The lease time you are seeing is for your local network. It should not be a problem. My Win10 machine shows lease obtained yesterday evening and expires tomorrow morning.
IPv6 is the relatively new addressing protocol used because the internet is running out of addresses on the old IPv4 (xxx.xxx.xxx.xxx). It looks like IPv6 is used from your hotspot outward.
[This message has been edited by williegoat (edited 07-27-2016).]
All I know is both the lease expiration and ipv4/ipv6 problems happen at the same time. It may only last 10-30 minutes or it may stay problematic a couple hours, but when it 'fixes itself' it works fine for hours or for days till it will suddenly occur again. Not a problem for me, but Jane has nursing school tests she has to take on line and they are sometimes only offered for an hour and only at certain hours. (No--I am not anywhere near exceeding our data usage limit) I dunno--we have a choice here of Verizon from a cell tower or HughesNet dish and no one I have talked to is happy with HughesNet. (No fiber optic phone cable out here and ATT says there never will be--Nat Forest won't let them do any more installation)
Should I assume that the hotspot shows a good signal from the tower (on the display on the hotspot) during the times it has no internet access? And that you can access the hotspot's admin page?
[This message has been edited by williegoat (edited 07-27-2016).]
Yes, the jetpack does show signal strength (bars) , as well as the number of towers detected (almost always just 1) and that it is 3g or 4g. "good" is relative--almost always 2, maybe '3bars' at most but the problem happens regardless of how many bars it may show. Menu options are: wifi/password connected devices messages (let ya know if an update is available or if you are nearing data limit) network settings (options=global mode-LTE/CDMA mode-GSM/UMTS mode) Wi-Fi settings (options=Start WPS-wifi band select--some other junk I don't know what is)
[This message has been edited by maryjane (edited 07-27-2016).]
I would have to go to the admin page to access most of that but yeah the device does show some of that right now in 'about jetpack' but no option for internet status there or sig strength except for: 88 dBm
[This message has been edited by maryjane (edited 07-27-2016).]
Next time it drops, go to the admin page and I'll bet it will say not connected and will have no IP address. That will tell you that the problem is on Verizon's end.
You may have good signal to nearest tower but 3G/4G network can still have problems at Verizon and little or nothing you can do to fix it.
You can see DHCP for old IPv4 because "non route" addresses, like 10.x.x.x or 192.168.x.x, are local to your router. DHCP for IPv6 is push by the ISP and All addresses are rout-able.
Is funny, the sad kind, that you blackout v4 but not v6 addresses because v6 is more threat/privacy problems then 192.168.x.x. In a nutshell, Everyone that uses v4 w/ a local router uses 10.x.x.x or 192.168.x.x because Local router used the 1 "real" v4 address from the ISP. (Some exceptions but you need a Business account or other to get ISP to give more "real" v4 address.) ISP and everyone else have direct connection to your machine w/ IPv6 enabled.
------------------ Dr. Ian Malcolm: Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should. (Jurassic Park)
That will give you a list of every IP you touch between your PC and Google. It will start with your laptop's IP, then your switch/hub IP, then the Jetpack, etc. all the way to whatever IP "Google.com" resolves to. When it starts timing out, that will tell you where the break in your connection is. If you can communicate all the way to the Jetpack and no further, the Jetpack isn't getting an Internet connection. That could be a problem on the Internet side, or your Jetpack is faulty. I'd power off and unplug the Jetpack for 30 minutes, then power it back up and see if that changes anything. If it doesn't, report the outage to your ISP. If they don't have a problem on their end, the next step would likely be replacing the Jetpack. I've had my cable modem go bad and it did just what you're experiencing. I had a find local connection to the network - just no internet access. Any devices connected in my home could all see one another, but none could see the internet.
Originally posted by Formula88: Open up a command prompt and type:
tracert google.com <RETURN>
That will give you a list of every IP you touch between your PC and Google. It will start with your laptop's IP, then your switch/hub IP, then the Jetpack, etc. all the way to whatever IP "Google.com" resolves to. When it starts timing out, that will tell you where the break in your connection is. If you can communicate all the way to the Jetpack and no further, the Jetpack isn't getting an Internet connection. That could be a problem on the Internet side, or your Jetpack is faulty. I'd power off and unplug the Jetpack for 30 minutes, then power it back up and see if that changes anything. If it doesn't, report the outage to your ISP. If they don't have a problem on their end, the next step would likely be replacing the Jetpack. I've had my cable modem go bad and it did just what you're experiencing. I had a find local connection to the network - just no internet access. Any devices connected in my home could all see one another, but none could see the internet.
Not quite. Many routers will not send ping/tracert answer and will timeout even tho they work. If Tracert get to Google etc then trace is good.
In his case.... Tracert won't help because Jetpack like has no network or it's WiFi have problems. If you get to Admin page thru Jetpack WiFi then WiFi is not the problem.
quote
Originally posted by 2.5: In the meantime can you get around this problem with some sort of a actual line connection when she needs to do a test, instead of wireless?
Isn't a WiFi issue when Jetpack has no network. If Jetpack see the network, Most doesn't have wired Ethernet.
[This message has been edited by theogre (edited 07-27-2016).]
We have Version here and it is the worst cell phone service and internet service as far as almost everyone I have talked to who uses their phones or internet.
We have trouble all the time and our is a so called high speed land line.
Good luck, it's not you, it is them.
Steve
------------------ Technology is great when it works, and one big pain in the ass when it doesn't
, or your Jetpack is faulty. I'd power off and unplug the Jetpack for 30 minutes, then power it back up and see if that changes anything. If it doesn't, report the outage to your ISP. If they don't have a problem on their end, the next step would likely be replacing the Jetpack. I've had my cable modem go bad and it did just what you're experiencing.
I at first thought it was the jetpack, but loaded my laptop and jetpack in the truck and went toward town. (they use a different tower and the towers are closer) About 3 miles from town, internet access was restored and I could not replicate the problem. Drove back toward home and the internet access again disappeared. It's an intermittent problem, doesn't happen often and it doesn't matter if the jetpack has been on for a long time or just turned on after being off for half a day. Once, I went all the way to the local Verizon store without it working correctly and inside their store, it worked fine--walk out in the parking lot, the problem reappeared. Verizon folks don't have any idea what the problem is. Doesn't happen daily or even weekly but when it does, it is aggravating. btw--our phones are 'dumb phones' and the jetpack of course is not needed to use them, but we can send pics and connect to the internet tho we never try to use internet via phone-screen too small. When the problem is present on laptops, our phones still work fine and I did attempt to send a pic from my phone, and it was sent with no problem.
[This message has been edited by maryjane (edited 07-27-2016).]
I at first thought it was the jetpack, but loaded my laptop and jetpack in the truck and went toward town. (they use a different tower and the towers are closer) About 3 miles from town, internet access was restored and I could not replicate the problem. Drove back toward home and the internet access again disappeared. It's an intermittent problem, doesn't happen often and it doesn't matter if the jetpack has been on for a long time or just turned on after being off for half a day. Once, I went all the way to the local Verizon store without it working correctly and inside their store, it worked fine--walk out in the parking lot, the problem reappeared. Verizon folks don't have any idea what the problem is. Doesn't happen daily or even weekly but when it does, it is aggravating. btw--our phones are 'dumb phones' and the jetpack of course is not needed to use them, but we can send pics and connect to the internet tho we never try to use internet via phone-screen too small. When the problem is present on laptops, our phones still work fine and I did attempt to send a pic from my phone, and it was sent with no problem.
Happens when the Romulan ship is sitting cloaked, blocking the signal.
[This message has been edited by 2.5 (edited 07-27-2016).]
