What's new

Two DHCP routers interconected networks

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I just figured out the small top picture is router1. I had to blow up the picture to 200% to kind of read. So what does not work? I need a list of ping tests. If you are connected to the 192.168.1.0 network with a machine can you 192.168.1.52? If you are connected to network 192.168.2.0 can you ping 192.168.1.1? This would be a start.

Network 1 / PC on Network 1:

C:\>ping 192.168.1.1 "ROUTER 1"

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>ping 192.168.1.6 "LOOP to same PC"

Pinging 192.168.1.6 with 32 bytes of data:
Reply from 192.168.1.6: bytes=32 time<1ms TTL=128
Reply from 192.168.1.6: bytes=32 time<1ms TTL=128
Reply from 192.168.1.6: bytes=32 time<1ms TTL=128
Reply from 192.168.1.6: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.1.52 "ROUTER 2"

Pinging 192.168.1.52 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.52:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Network 2 / PC on Network 2:

C:\>ping 192.168.2.1 "ROUTER 2"

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>ping 192.168.2.121 "LOOP to same PC"

Pinging 192.168.2.121 with 32 bytes of data:
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.1.1 "ROUTER 1"

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
You need to figure out why you cannot ping 192.168.1.52 which is the WAN IP address for router2 from the network 192.168.1.0. A machine connected to 192.168.1.0 network should be able to ping an address in its own network. I would assume the firewall is still on or you have a cable or connection problem. Did you try letting router1 assign the IP address with DHCP to router2 WAN interface?

Reagarding cabling issues, is not cable i can plug that cable to ani pc and works ok.

Now, yes i have tried dhcp on router 1 assign automatically ip to router 2 on wan and router 2 get dinamically wan ip. still cant ping the router 2.

and as right now assigned the static ip, router 1 reserve the ip for that router with mac address, and router 2 assigend manually.
 
I don't have answer for you but you should be able to ping the WAN port from the same network providing the firewall is off. Can you check for a new firmware? Maybe check outstanding issues and see if this is a problem with this router.
 
I don't have answer for you but you should be able to ping the WAN port from the same network providing the firewall is off. Can you check for a new firmware? Maybe check outstanding issues and see if this is a problem with this router.

Darn... Let me check for router issues.. Ill try with diferrent routers also and ge tback

Firewall is not on as i understand nothing configured on the parental controls/ service block/ port block or schedule in router 1 nor on router 2...
 
You might post on the E1200 router forum and see if you can turn off the firewall and NAT as and the router as a router. You might also post on the DD-WRT the same thing. I think there is a DD-WRT flash for that router. Cisco would be my preferred way to do this. I would check it first.
 
You might post on the E1200 router forum and see if you can turn off the firewall and NAT as and the router as a router. You might also post on the DD-WRT the same thing. I think there is a DD-WRT flash for that router. Cisco would be my preferred way to do this. I would check it first.

Coxhaus, do the net mask have to do anything with this, iam using 255.255.255.0 shouldn't I be using 255.255.252.0

--Never mind.. could not help with anything :p
 
Last edited:
I guess you figured it out but 255.255.252.0 is wrong. There are several masks which will work and 255.255.255.0 is one of them. The mask defines how big your network is and how many IP addresses are contained in the network.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top