PAP2T vs RT31P2

[voip123]

I've been talking with VOIPo support about this. I think it's a bad RT. Earlier today I put the RT directly connected to the cable modem (I first made the WAN on the RT DHCP so the cable modem could assign it a public IP). I unplugged both, plugged in the cable modem, waited for the 4 lights, plugged in the VOIPo. The Internet light on the VOIPo blinked like crazy (which is normal). But never got a Phone light to light up. Then after waiting for 30 mins, I tried to get back into the RT admin screen, and the password was changed and I can no longer get in. I then tried the Reset button for 30 seconds, and it didn't work. Connecting an XP laptop to the RT, getting a 192.168.15.100 IP, I could see the internet fine.

Thanks to all of you for the continued suggestions.

-Craig

Since you mentioned you connected the RT to modem directly. Can we do one more check?

After hookup everything, run the ipconfig /all

Post the output here.

[ctaranto]

Since you mentioned you connected the RT to modem directly. Can we do one more check?

After hookup everything, run the ipconfig /all

Post the output here.

Well, I put the RT directly on the cable modem to eliminate everything else. After getting Phone 1 lit up, I moved it back behind the WRT router, and it still works fine.

I have the WRT give the RT WAN a 172.20.0.101 address (using Static DHCP on the WRT, Obtain IP on the RT). The RT LAN is 192.168.15.1. I have turned DHCP off on the RT because I'm not going to be connecting anything to it and don't want unnecessary things running on it.

When I did have a laptop connected to the RT (and DHCP was enabled), I believe it provided:

IP: 192.168.15.100
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1

With that, I was able to see the RT, WRT, and internet.

I have unplugged the VoicePulse PAP2T, configured VoicePulse to always call my virtual number on VOIPo, and all is well.

/c

[voip123]

Well, I put the RT directly on the cable modem to eliminate everything else. After getting Phone 1 lit up, I moved it back behind the WRT router, and it still works fine.

I have the WRT give the RT WAN a 172.20.0.101 address (using Static DHCP on the WRT, Obtain IP on the RT). The RT LAN is 192.168.15.1. I have turned DHCP off on the RT because I'm not going to be connecting anything to it and don't want unnecessary things running on it.

When I did have a laptop connected to the RT (and DHCP was enabled), I believe it provided:

IP: 192.168.15.100
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1

With that, I was able to see the RT, WRT, and internet.

I have unplugged the VoicePulse PAP2T, configured VoicePulse to always call my virtual number on VOIPo, and all is well.

/c

OK. I can see your setting as below:
#1 comcast modem (correct?). The default gateway on the device is 172.20.0.1. Now leave the DHCP enable on this device.

#2 your RT. When you connect the RT to the #1 in any port. But you must connect the other end on RT into the <B>Internet</B> port.

#3 A XP machine that connects to the RT.

If you run the ipconfig /all on the XP, you should get something like this:
IP: 172.20.0.1XX
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1 <- I am not sure about this one. Did you assign this?

Now open a browser,and type: http://172.20.0.1XX, the one you got from the command ipconfig /all. You might try: http://172.20.0.1XX:8080 or http://172.20.0.1XX:9999, it depends on the port VOIPo sets for you.

See if you can access.