 |
 | Vonage Forum Menu |
| | |
| Vonage Forums |
|
|
| | | |
| Vonage In The News |
| | |
| Vonage Customer Reviews |
| | |
| |
Vonage OK. Here's my latest theory on why some people have succeeded in getting the vt1005
OK. Here's my latest theory on why some people have succeeded in getting the vt1005 to work in front, when DHCP/NAT is turned off, and others (like me) haven't been able to get it to work:
In passthrough mode, the vt1005 and the device behind it are both going to ask for an ip address from a dhcp server, and both requests are going to be passed to your broadband provider's dhcp server. If your broadband provider only gives you one ip address to work with however, then only 1 device can succeed in using dhcp. If the other device tries to use dhcp it will end up not having an ip address assigned. I called Comcast and asked about this. They said in my area with my service, Comcast strictly limits a user to 1 ip address, though a second address could be had for about $7.00/month. According to the Comcast tech, if two devices on my network make dhcp requests, then in short order they will both lose their connection to the internet. Indeed, that is exactly what happens to me when I place the vt1005 in front and turn NAT off. (Note a comment from Lauren way back at the start of this thread: "Troy, my buddy in support, and I chatted about it. He said it works okay as long as I don't have two devices trying to pull IPs.")
My guess is that anyone who has gotten the no NAT mode to work with the vt1005 in front is grabbing two different ip addresses from their broadband provider's dhcp server. They may not realize this however, because once the vt1005 is in no NAT mode, there is no longer any direct way to access the vt1005's web page and see what address it is using. (To do that you have to turn off the pc's dhcp and set its static ip address to 192.168.102.2.)
I was confused about this at the start of this thread. I thought that in no-NAT mode the vt1005 was "passing-through" all non-voip traffic to a second device which had the *same* ip address as the vt1005. But two devices both using dhcp to obtain dynamic ip's are not going to share the same address! That's why you need two ip addresses to get the VT1005 to work in no NAT mode with a dhcp client behind it.
Read The Full Thread: My setup: Cable modem -> VT1000 with QoS -> Linksys BE
• I thought I would share my setup with others in case they ran into the same problem
• Keep us posted on the reliability (if you have any reboots) of the VT1005 using
• I will be watching this too since it's almost the same hardware I have. I admit I
• I've been doing some external port scans to see if having the vt1000 in front causes
• that last post was by me.
• Justpaul:
Hmm, that's very interesting. I think I could figure out what you've
• Could you give me a few more details?
Is the Netgear a hub or a NAT router?
If
• JustPaul:
Sorry about that. The netgear is - well, WAS - a router. I decided
• JustPaul:
Holy Cow! I decided to experiment with turning the MTA into a bridge.
• wow, sorry for the mess-up.
If you were to experiment again, I would try this:
[Before
DanG posted "OK. Here's my latest theory on why some people have succeeded in getting the vt1005" on 02/13/2004 |
|
|
| |
| Vonage Service Plans |
| | |
| Vonage VoIP Members |
| | |
| Vonage Stock Price |
|
Value: 1.70
Change:  -0.03
Up to 15 Minute Delay | | | |
| Site Search |
| | |
|
|
Vonage VoIP Phone Service is redefining communications by offering consumers
& small business VoIP Internet phones, an affordable alternative to traditional phone service.
The Vonage VoIP Forum Generated This Page In: 0.33 Seconds and 223 Pages In The Last 60 Seconds
The Vonage VoIP Forum
|
Members
New 
New Today 1
Yesterday 3
Total 64292
Who Is On Site
Visitors 119
Members 1
Total 120