Day 2, and the frustrations are still here

Posts: 16 · Vonage Forum Associate Joined: Feb 27, 2005 Posts: 16

ToddlerTN wrote:

Ok, here you go:

- Write down all the forwarding rules you're currently using.
- Turn off the DHCP server on your WRT54GS and also make sure it's configured to get it's IP address from DHCP
- Turn off your entire network (PCs, cable modem, everything)
- Plug the Vonage RT31P2 into your cable modem
- Plug your PCs and phone line into the RT32P1
- Turn on the cable modem and wait for the connect light to glow solid
- Turn on the RT31P2 and wait for the phone light to glow solid
- Check for dial tone
- Turn on your PC and you should get a new address (probably 192.168.15.100)
- Check for internet connectivity
- Login to the RT31P2 and setup your port forwarding (note that the subnet is different now, not 192.168.1.x but 192.168.15.x, so make changes as necessary)
- Test your port forwarding
- Plug your WRT54GS by connecting its uplink port (not the WAN port) to the RT31P2 (you probably won't be able to manage it in this configuration, but that's not a problem...it's just passing traffic to your wireless devices, which will get their IP addresses via DHCP from the RT31P2)

Hopefully all that makes sense and works for you as it does for me. Good luck.

P.S. - I use static IP addresses for anything I don't want to change, like my FTP server, Exchange server, etc. When a DHCP lease expires, that device will probably grab the same IP address that it had before, which has been working for you for eight months. But if you have a power outage at your house (or change devices like you're doing here), it's a crap shoot. DHCP isn't wrong exactly, but it's not best. Just realize that if one day it isn't working, you might need to check your IP addresses and update your forwarding rules to reflect the changes.

i'm gonna do it right now. thank you in advance Very Happy

Posts: 482 · Posted: Sun Feb 27, 2005 11:07 pm Post subject:

I only see three possibilities:

1) You haven't had time to do it
2) You did it and it worked and you moved on with life
3) You tried it and can't connect to the internet at all and were never heard from again

I'm just curious how it turned out for you...?

Posts: 16 · Vonage Forum Associate Joined: Feb 27, 2005 Posts: 16

ToddlerTN wrote:

I only see three possibilities:

1) You haven't had time to do it
2) You did it and it worked and you moved on with life
3) You tried it and can't connect to the internet at all and were never heard from again

I'm just curious how it turned out for you...?

#! is the correct answer. if it works, i will be sure to come back and praise you!!! Very Happy

i'm actually about to try it in the next 10 minutes. i'll let you know what happenes

Posts: 82 · Posted: Mon Feb 28, 2005 6:40 pm Post subject:

is it day 365 yet ?

LOL

Posts: 482 · Posted: Mon Feb 28, 2005 6:51 pm Post subject:

What's funny is he hasn't even got it working yet, and already he's considered a "Vonage Guru" now.

Posts: 16 · Vonage Forum Associate Joined: Feb 27, 2005 Posts: 16

ToddlerTN wrote:

What's funny is he hasn't even got it working yet, and already he's considered a "Vonage Guru" now.

'

haha..i probably will be when this is all said and done.

ok..so i did what you said, although i can't check out whether the port forwarding has worked yet or not (until i get my wireless laptop up...story below..)

internet works, phone works.

i hook up the second router (wireless), and then the connection (wired one) and phone stops working. i tried looking on the back of the router (wireless), and i don't see an uplink port.

what to do now?

Posts: 16 · Vonage Forum Associate Joined: Feb 27, 2005 Posts: 16

i take that back. now its dropping both the net and the phone, where as before it would only affect the phone. so far, so bad. DAY 3

Posts: 482 · Posted: Mon Feb 28, 2005 7:20 pm Post subject:

You may not have an uplink port. Mine has one, but yours may not.

However, in looking at the Linksys support article, I noticed that the LAN address is always static and will never come from DHCP. So here's the deal...follow the steps in this article to configure your WRT54GS, and when you get to the part about assigning it an IP address on your subnet, set the IP address for the WRT54GS to 192.168.15.2 (your RT31P2 will be 192.168.1.1 and it only starts handing out DHCP at 192.168.1.100 so you won't have any IP conflicts).

http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?
p_faqid=358&p_created=1084209764&p_sid=7xErQfzh&p_lva=&p_sp=cF9
zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTcwJn
BfcHJvZHM9MSwxOSZwX2NhdHM9JnBfcHY9Mi4xOSZwX2N2PSZwX3NlYXJja
F90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfc2NmX2xhbmc9MSZwX3BhZ2U9
MQ**&p_li=&p_topview=1

*edit 1* Sorry, I had to put in line breaks so that the thread would still display correctly. Just paste that into Notepad, take out the line breaks and then paste it into your IE Address Bar.

*edit 2* I PM'ed it to you also just in case that helps.

Posts: 482 · Posted: Mon Feb 28, 2005 7:29 pm Post subject:

jrairden wrote:

i take that back. now its dropping both the net and the phone, where as before it would only affect the phone. so far, so bad. DAY 3

Well, ok...now here's the bad news...that's exactly what my first RT31P2 did. Network and phone would both disconnect randomly at the same time, at least once every couple of hours and sometimes 2-3 times an hour. I called and they tried firmware updates, blah blah blah...they finally sent me a replacement (overnight FedEx, but only after I asked them to). The good news is that the replacement hasn't rebooted once. So...sounds like maybe you have a bad router on your hands...not what you wanted to hear, but resolvable with some patience. And, apparently, you do have plenty of patience.

Posts: 16 · Vonage Forum Associate Joined: Feb 27, 2005 Posts: 16

ToddlerTN wrote:

jrairden wrote:

i take that back. now its dropping both the net and the phone, where as before it would only affect the phone. so far, so bad. DAY 3

Well, ok...now here's the bad news...that's exactly what my first RT31P2 did. Network and phone would both disconnect randomly at the same time, at least once every couple of hours and sometimes 2-3 times an hour. I called and they tried firmware updates, blah blah blah...they finally sent me a replacement (overnight FedEx, but only after I asked them to). The good news is that the replacement hasn't rebooted once. So...sounds like maybe you have a bad router on your hands...not what you wanted to hear, but resolvable with some patience. And, apparently, you do have plenty of patience.

the patience is going down a bit. i couldn't get it reconnected, until i reset my wireless router and put it back the way it was. is there any way i can expedite this procedure of them having to replace it (preferably overnight)? from what i've heard, calling the customer service could fit into one of the layers of hell, and having to use my cell phone (and minutes) waiting on hold is not worth the 24.95 a month to me. any ideas??