- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I had a MIFI working great on my Win 7 notebook, but while the upgrade to the LG modem went smoothly, the VPN only sporadically works now. By sporadically, I mean that sometimes it will connect after many minutes. Also, when it is connected, the throughput to the VPN resource (my company's corporate network) seems very slow.
We pretty much use the standard Micorosft VPN out of the box so there is no third-party VPN involved.
I've tried all sorts of VPN settings and none of them work.
I'm wondering if there is a Verizon issue or if anyone knows of any testing programs, etc. The modem is pretty much useless without the VPN for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same issue. Super annoying ...
PREVIOUSLY WORKING;
- windows 7 professional
- verizon mifi 3G
- Microsoft PPTP VPN
- OpenVPN
- pfSense PPTP VPN
*All VPNs were managed OUTSIDE of the Verizon VZAccess Manager
CURRENTLY NOT WORKING:
- windows 7 professional
- verizon LG VL600 4G LTE
- Microsoft PPTP VPN (sometimes works within Verizon VZAccess Manager)
- OpenVPN (does NOT work within Verizon VZAccess Manager)
- pfSense PPTP VPN (sometimes works within Verizon VZAccess Manager)
*All VPNs do NOT work OUTSIDE of the Verizon VZAccess Manager.
I spoke to verizon support for an hour and this is what they recommended:
1) Wait till a new version of VZAccess Manager comes that includes a fix that may work
2) Try the other 4G LTE device that is avaialble and see if that may work (I am going to test this next week)
3) Go back to the mifi device (not acceptible in my opinion)
What I do not understand is what is different NOW versus when the VPNs did work outside of the Verizon VZAccess Manager. The verizon support said it had to do with IPv6 support but that did not sit well with me.
Could it be the device driver for the LG unit?
Could it be the VZAccess Manager Software?
I am stumped ... anyone find a solution?
Cheers,
-Will
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a problem that also sounds similar
Window XP on Thinkpad
Verizon USB727 3G card
Solid VPN connectivity into a Northern Virginia corporate network for several years until late November / early December. Then unable to connect to VPN on a sporadic basis
Testing today with a VPN in Northern Illinois also showed sporadic connectivity
When connection fails MS PPTP dialog shows “Connecting” and then times out after some time. When connection is made the “Connecting” screen disappears very quickly or doesn’t show
Using “telnet [target address] 25” to telnet to the SMTP port always works
Using “telnet [target address] 1723” to telnet to initial VPN port works or fails just like connecting though the MS PPTP dialog
Another company employee is having similar problems with both a different Verizon 3G card and a MIFI mobile hub.
Have been working with Verizon tech on the problem. He says the initial packet is leaving the Verizon network by no response is being received back into the Verizon network when the connection fails.
He has asked that we try to trap the initial packet coming into the Northern Virginia VPN. Will do that - hopefully during the week of 12/20
The tech was monitoring only the node that provides the interface to the wider internet
Using “tracert [target address]” I can see that there seem to always be 6 nodes between my laptop machine and the monitored node. Those node ids vary. But, because “tracert” is slow, I cannot say that failure occurs on a specific path within the Verizon network.
Speculation – Something in the Verizon network (or on my PC) is corrupting the initial packet, such that is not recognized (or is rejected) by the target VPN. Trapping the initial packet coming into one of the VPNs (if the packet gets that far) might resolve this speculation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This LTE problem with VPN access is happening for me. I called Verizon on 12/23 and they acknowledged it is a configuration problem on their end. They said they are working on it.. and they would get back to me in 48 hours to update me on progress. 120 hours later.. no call from them. Calling them tomorrow.. but I have a feeling they will give me the run around.
Anyone have any info on fix date?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It usually takes up to 10 minutes of trying, but I can get it to connect and stay connected. VERY ANNOYING. But the fact that they acknowledged the problem means some sort of fix is probably close.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a suggestion for a quicker way to make a connection until this problem is fixed -
(1) If you don't have a shortcut on your desktop to open the Microsoft PPTP login dialog, create one.
(2) Open the dialog box and make sure that your user name and password are set and saved
(3) Close the dialog box
(4) Double click the shortcut to open the dialog box.
(5) Press Connect in the dialog box
(6) Wait a few seconds for the "Connecting" popup to change to "Verifying User and and Password"
(7) If the "Connecting" popup doesn't change, press the Enter key to cancel the attempt
(8) Double-click the shortcut to open a new dialog box and go back to step 5.
Using this technique I can make repeated sign on attempt very quickly. And I can usually connect within 5 - 10 tries.
Also, I have not received any word back from the Verizon tech who I have been working with since he acknowledged the results of my testing on December 22. I will try to contact him again during the week of January 3 if I don't hear back from him before then.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great directions... I have my 15 remote sales / service reps doing the same procedure currently while in the field throughout the Wash DC area, only difference is we are long time users of VZW and are still using various models of rev0 and revA aircards experiencing the same MS VPN connectivity issues which started over a week ago.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, I called tech support again. They now say that VPN is not supported but they are looking at it. It sounded like they have fielded a lot of complaints and there is no ETA for any kind of fix.
They did say to avoid PPTP/TFTP. I don't know what TFTP is but one of the choices under the Microsoft VPN is PPTP. The problem is when it does intermitantly connect, it seems that it uses PPTP! Agrh.
This needs to be fixed soon.
It's remarkable how they are able to claim it is not their problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have communicates with the Verizon tech that I have been working with several times since my last post. First he said that a problem had been identified that that a fix was expected by January 3. Then said that they had not made that fix date. Last night I successfully connected several time and sent him a note asking if they had applied a fix. He replied that an update had been made. During the day today I successfully connected several times while a different location so I know the cell tower I was hitting was different. Then, this evening, from last night's location, I again connected successfully several times.
So, based on my experence over the past 24 hours, I'm ready to say the problem is solved, at least for me.
I have received no feedback regarding what the problem is, so I don't know if the fix would apply to 4G users.
My suggestion, if you are still having the problem, is that you insist on getting past the first tier support, which means the Verizon tech who answers the phone will create a trouble ticket, give you a number, and pass the problem on the someone with more technical knowledge. Although it took me some time and effort to convince Verizon that the problem was theirs, the tech I was working with did not try to belittle me or convince me that the problem was mine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hmm, it's still not working for me. I wonder if the problem is geographic? I'm in the Chicago area mostly (Downtown. Arlington Heights, O'Hare areas). JonnieR, where are you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am in Vienna, VA, just outside of Washington, DC. My successful connections have been from home and from my office, which is about a mile away.
When this problem first started, I speculated that it had something to do with Verizon's 4G rollout, which they had just started pushing in this area. I wonder if it is 4G related and if they are making updates based on geographic areas.
One other note - I was traveling just after Christmas and used the network from Spartanburg, SC, an unlikley early 4G rollout area. I had the same connection problems from there, so that might blow my theory apart.
I am honestly surprised that there isn't more noise on the Internet about this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been to three places today and it hasn't worked at all. The last time I was able to connect was Thursday moirning.
I really need this to work. I had the impression from VZW tech support that they have a lot of calls on it. She didn't write a ticket but she did take my number down to call me back.
I'm at my office today and I'm going to have the IT people check the VPN at our end again, but it should just work. We're using the right-out-of-the-box Microsoft stuff. I can ping the VPN and I can telnet into it...it's VZW doing something still.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still not working.
We found a Microsoft testing tool for VPN
http://technet.microsoft.com/en-us/library/bb877965.aspx
...and it shows that the GRE traffic for VPN doesn't make it through Verizon's LTE system. VPN would seem to be an important system for business!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too have done extensive testing with this and it seems that the modem itself is doing NAT (probably to conserve the number of IP addresses Verizon has to buy). This can be semonstrated by going to VZAccess and seeing what ip address you have then going to http://www.whatsmyip.org/ and seeing that they are not the same. The issue really lays to the fact that the VPN server cant route back to the modem.
Another thing noted is that with the 4g cards it acts like a Network card and not like a modem reson being that 4G data speeds are higher than the baud rate of any modem. This is done because you are only as fast as the slowest link ( which would be the modem)
I use to have a USB720 3G card that I will be switching back to. Obviously because of my need for VPN access but also so I won't be at the mercy of VZAccess managaer while it is better than Sprint's I'd rather go without it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@hp300guy, I was just playing with it and I see the two different IP addresses. What concerns me is the 10.x.y.z range used. Isn't that a private address space? Maybe Verzion dug itself a big hole.
I'm not sure how they can market this for business use without having support for VPN's. I hope they can address this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@ChicagoVZUser You would be correct in saying that the 10.x.x.x is a private ip range. If you look on Windows and look at the subnet mask its a 255.255.255.252 which only allows for two hosts one being the computer and the other being the gateway. I don't know if this was done intentionally but it really is a hinderance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spoke to Verizon Level 2 Tech Support today.
They confirmed that there is a known problem with VPN's on their LTE network, and that they did not intentionally block VPN access. They said that their vendors are working on a solution.
I can confirm that PPTP does not work reliably on their LTE (though I'm pretty sure I've made it work once or twice). It seems that the GRE protocol is what is being blocked on their network. (This would affect PPTP VPN's, but not necessarily other types of VPN's)
FYI, you can switch back to a 3G device and plan, but will need to talk to support or customer service. Additionally, note that switching back to 3G will invalidate your 4G SIM card! So have customer service order you a replacement SIM card BEFORE they switch you off the 4G plan, otherwise you will be stuck paying for a new SIM card when you decide to go back on a 4G plan.
(My support agent was very helpful in identifying this problem, and in proactively ordering me a replacement SIM card.)
There is no ETA for resolution of the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for looking into this drueter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, I was able to connect today in the Chicago area....anyone else?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems like it's working fine now.....I'm going to give until the end of next week to be sure, but it looks like this issue is closed.