Posted: 9/22/2009 2:14:03 PM EDT
|
Hello-
I just went from optonline to verizon FIOS. The Linksys I was running with opt could easily be configured to a default 192.168.2.1 address to support the wife's work VPN connection. A 192.168.1.x address seems to be incompatible with VPN as it never connects; the 192.168.2.1 does. When I go into the verizon router GUI to change the router address from 192.168.1.1 it never applies the change, no matter how long I wait, to 192.168.2.1 and needs to be reset as neither router address of 192.168.1.1. or 192.168.2.1 allows me to access the router. Any clue as to what I am doing wrong? Thanks. |
|
The first thing you should do is change the DHCP scope to hand out 192.168.2.x addresses.
Then change the internal ip of the router to 192.168.2.1 If you don't see any DHCP scope settings it's likely they are updated automatically depending on the internal ip of the router you set. Restart your computer to get new IP address settings. Post back here if it works. |
|
Quoted:
The first thing you should do is change the DHCP scope to hand out 192.168.2.x addresses. Then change the internal ip of the router to 192.168.2.1 If you don't see any DHCP scope settings it's likely they are updated automatically depending on the internal ip of the router you set. Restart your computer to get new IP address settings. Post back here if it works. How do I change the DHCP Scope? edit: i'm on with support now. the 192.168.2.1 may be used by other device. |
|
Quoted:
Quoted:
The first thing you should do is change the DHCP scope to hand out 192.168.2.x addresses. Then change the internal ip of the router to 192.168.2.1 If you don't see any DHCP scope settings it's likely they are updated automatically depending on the internal ip of the router you set. Restart your computer to get new IP address settings. Post back here if it works. How do I change the DHCP Scope? edit: i'm on with support now. the 192.168.2.1 may be used by other device. I'm not familiar with the verizon FIOS router. But look for "DHCP server settings" or "internal IP addresses" or something of that nature. Instead of using 192.168.1.x you could use the 10.0.0.x range. |
|
Quoted:
I do believe your TV set top boxes also require a specific IP address. Maybe its just mine since I have the multi-room DVR but something to keep in mind. You are correct - as I was told the same thing from Verizon Tech Support. They say without certain IP address the "Guides" may not feed properly. A tech is due here soon after being on 4 different support calls and 7 hours worth o my time. They don't resolve this today OUT GOES VERIZON and we will live with the BS of optimum. OPT may not be a Mercedes but they get my stuff done without too much issue. |
|
Quoted:
Quoted:
Quoted:
The first thing you should do is change the DHCP scope to hand out 192.168.2.x addresses. Then change the internal ip of the router to 192.168.2.1 If you don't see any DHCP scope settings it's likely they are updated automatically depending on the internal ip of the router you set. Restart your computer to get new IP address settings. Post back here if it works. How do I change the DHCP Scope? edit: i'm on with support now. the 192.168.2.1 may be used by other device. I'm not familiar with the verizon FIOS router. But look for "DHCP server settings" or "internal IP addresses" or something of that nature. Instead of using 192.168.1.x you could use the 10.0.0.x range. Thank you- Support and I tried that - was like reinventing the wheel and then failed to allow wireless support!! 
Today is the last day my business and my wife's work will suffer - no fix OUT they go! |
|
Update - Vtech is here.
Since my wife is not here to test her machine the best we cold do is get the linksys to work through the Verizon router now gateway. I am posting this through my 192.168.2.1 laptop wireless connection. We'll see how this works out when she returns this evening and I will post back. Thank you all. |
|
Verizon Tech set up my Linksys to as act the Verizon's switch so I retain what I believed to be the solution to get the 192.168.2.1 address for the VPN. Well it doesn't work.
LAN and internet connectivity is there but no VPN connection. 
If I don't get this working tomorrow morning ... I'll be singing soprano. 
|
|
Quoted:
Have you talked to anyone at your wifes work about the problem? They have to have seen this before if the problem is originating on their side. WOW - there is SOME story here. This solution took me 20+ personal hours (during and after work), 2.5 days of my personal sales making down time and 2 days of non-sales productivity for my wife AND including a extra 90 mile trip for her to get some work done in her business offices. My wife's VPN needed a NAT of 192.168.2.x - we (Lion_dog and Verizon) took the Linksys (previous successful with VPN connection while using Optimum.net) and made that a switch to the Verizon modem to get around the difficulties of assigning the Verizon router with that NAT address. My wife's in-house support guy kept telling me AND my wife that it was Verizon's fault, that Verizon had a block on our IP address. I performed a ping on her VPN IP and her company's DNS name - no joy (100% loss of packet return) ... I did a tracert on my wife's VPN IP address and the trace timed out at this one particular router. I found this router to be my wife's company's ISP carrier. Verizon, when testing with same tracert command spoofing my 173.x.x.x address, got stopped at the same tracert router address as my test produced. Now almost from the beginning I kept asking Verizon for a new IP. Verizon made it sound like I needed a Business static address - my response was "why I am not to be VPN to but from". As I escalated over the first 5-6 Verizon tech yesterday, I get this one FIOS tech who would listen to me (one out of 12 Verizon technicians over a 3 day period, btw). This Verizon tech performs all of his basic and advanced troubleshooting and finds NO problematic Verizon router configuration here in my home - I should be able to VPN in. When he experiences the failure doing the tracert on the wife's VPN address, he take a long hard looks at the our home 173.x.x.x IP address and says, "I don' like this." He then performs a release/renew on our home Verizon modem and IMMEDIATELY my wife's VPN connects, as it was on auto-dial into her office VPN during this entire period.
As for her company's tech - he is a hair away from me calling and complaining to my wife's SVP. I have a strong vendor relationship with this SVP. REASON: My wife's company tech did not call their ISP with the following information, KNOWN by HIM: Verizon had recently purchased a block of private IP addresses and and that these were now available to the public. The "block", which we were told by him to be a Verizon problem, was actually a block in place by their ISP/vendor. I'm not a scumbag but my wife's company tech cost me and my wife dearly. Maybe I should take a POLL here. 
Edited for clarity. Better???? |