| Author |
Message |
phatguy29
New Forum Member


Joined: Feb 15, 2006
Posts: 6
|
Here is my setup:
Linksys BEFCMU10 cable modem (internal IP 192.168.100.1) Linksys RTP300 Voip (internal IP 192.168.100.2) Linksys BEFW11S4 (connected to RTP300 with static internal IP 192.168.100.3 - awesome wireless acess as well) Connected to the RTP300 I have two workstations that work great (IP comes from RTP300 - also show RTP300 as gateway) Linksys EZXS55W with no devices attached (yet)
My only issue is that I can no longer get to my cable modem using IE @ 192.168.100.1. I also can not ping this address via the Administration | Diagnotics tab on the RTP300.
I used to have the RTP300 as a downstream device from the BEFW11S4 and had it cabled such that it was getting IP from the BEFW11S4's DHCP server. I changed it around such that the RTP300 is first to ensure that QOS is being used properly. In doing so, I shut off the BEFW11S4's DHCP server and changed its functionality into that of a router.
Any ideas to look for? Any thing I could try? |
|
|
|
|
 |
taylor2767
Vonage Forum Evangelist


Joined: May 05, 2005
Posts: 400
|
I would try to enable the DHCP again and assign your DNS addresses to your router and see if you can ping at that point.The DNS address can be found by typing on the command line"IPconfig/all". This will give you a primary and a secondary DNS addresses. Write those down and then put them in your routers DNS address. |
|
|
|
|
 |
sinceMay2004
Vonage Forum Master


Joined: Feb 28, 2005
Posts: 193
|
BEFCMU10 modem setup page: 192.168.100.1
RTP300 Router setup page: 192.168.15.1 Obtain IP, DNS and Gateway Automatically from ISP
Obtain automatically from RTP300=> Computers below RTP300: 192.168.15.10_ IP is whatever the RTP300 assigns
BEFW11S4 Router setup page: 192.168.0.1 Obtain automatically from RTP300=> 192.168.15.10_ IP is whatever the RTP300 assigns 192.168.15.1 Gateway should be RTP300 IP
Computers below the BEFW11S4 should have IP =>192.168.0.10_ |
|
|
|
|
 |
phatguy29
New Forum Member


Joined: Feb 15, 2006
Posts: 6
|
There's something strange going on here. 192.168.100.2 is the RTP300 router.
ipconfig from my workstation:
Physical Address. . . . . . . . . : 00-C0-A8-7C-BB-18 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.100.102 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.100.2 DHCP Server . . . . . . . . . . . : 192.168.100.2 DNS Servers . . . . . . . . . . . : 192.168.100.2
From the status page on my RTP300 router:
Login Type: DHCP Internet IP Address: 68.68.70.183 Subnet Mask: 255.255.255.0 Default Gateway: 68.68.70.1 DNS 1: 68.168.160.5 DNS 2: 68.168.160.2 DNS 3: 68.168.160.5 MTU: 1500
Why don't I see the same DNS servers resolved at my workstation? |
|
|
|
|
 |
sinceMay2004
Vonage Forum Master


Joined: Feb 28, 2005
Posts: 193
|
192.168.100.2 I don't believe is the router unless you statically set it
factory reset
also try the addresses on your pc aren't right. start/run/cmd/ipconfig/renew |
|
|
|
|
 |
phatguy29
New Forum Member


Joined: Feb 15, 2006
Posts: 6
|
Finally got everything working. These three devices can not share the same subnet. I have the RTP300 and the BEFW11S4 on the 192.168.15 subnet and the BEFCMU10 on the 192.168.100 subnet. I can now get to all three using IE. |
|
|
|
|
 |
phatguy29
New Forum Member


Joined: Feb 15, 2006
Posts: 6
|
Wanted to add as well, that the DNS addresses on my PC were correct. The RTP300 has a "feature" called a DNS Proxy. This will use the RTP300 to resolve DNS first rather than the DNS servers defined by DHCP. It caused some serious delays on my client side. Lots of latency as the DNS lookup was never resolving at the router (two seconds latency for each lookup.) I shut this off and DNS lookups were almost instantaneous. |
|
|
|
|
 |
NateHoy
Vonage Forum MVM


Joined: Nov 01, 2005
Posts: 2257
Location: New England
|
| phatguy29 wrote: | | Wanted to add as well, that the DNS addresses on my PC were correct. The RTP300 has a "feature" called a DNS Proxy. This will use the RTP300 to resolve DNS first rather than the DNS servers defined by DHCP. It caused some serious delays on my client side. Lots of latency as the DNS lookup was never resolving at the router (two seconds latency for each lookup.) I shut this off and DNS lookups were almost instantaneous. |
Yup, this is a big problem with the WRTP54G and RTP300 routers. Vonage should just ship 'em with the DNS Proxy off.
http://vonage.nmhoy.net/dnsproxy.html |
_________________ Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04) My Vonage Self-Help Guides: http://vonage.nmhoy.net |
|
|
|
 |
|
|