Two Networks unable to communicate

[echz]

Hello all! I've got a LAN set up as follows:

-Comcast Cable internet connected fed into a switch

-Switch feeds into 2 different routers to pick up two separate Internet IP addresses

-Router 1 which is the production environment is operating off of a 10.0.0.x IP address environment with a subnet mask of 255.255.255.0, using DHCP to distribute IP addresses to all of my daily users.

-Router 2 is designed to be operating the test environment. This router is configured as 192.168.0.1 with a subnet mask of 255.255.255.0, and using NO DHCP - I want to statically assign all addresses on this network.

My problem now is this -- I am able to do everything I want to with the two separate environments and connections, EXCEPT, I can't communicate between the two environments.

If I am a client on Network 1, (the 10.x) network, and I try to ping the opposite router (the 192.168 net), I get:

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 10.81.72.1: Destination net unreachable.

Also, if I try to type \\server.domain.local from Network B, I can't access any of the resources on this server.

Anybody have any clues as to why I can't get these two networks to talk locally? I am at a loss as of right now...Any help is greatly appreciated -- Thanks!

 

[ShackDaddy]

You need to add a route to the routing table of each of your routers that says "If you want to get to the other network, use this IP, and to get there you have to use my external interface." The IP that you provide should be the ISP-provided IP of the other router in each case. Then you should be able to route back and forth.

Hopefully the IP's that the ISP is providing you are static, otherwise this will be a very problematic arrangement.

ShackDaddy

 

[echz]

ShackDaddy:

That's just the problem, they're not static IPs and I'm using DYNDns which is built into the routers to keep maintenance of the IP address.

I'm thinking there's an easier way I can do this, I'm just looking into it too hard I think.

I just basically want the Test environment separated from the Production environment, and have them both accessable from the Internet - However, the Remote Desktop port can only be forwarded to one address... I need it to be accessable to both. Any suggestions anyone can provide will keep me from banging my head into the wall even further Thanks!!

 

[djtech2k]

You may be able to make it work by setting up the routing between subnets....I am thinking back and I remember some stuff about RIP and bootp. Play with your router with the RIP and bootp settings. I would venture to say that the biggest problem is that both environments have a dynamic internet IP. What kind of swicth do you have? Can you program it to assign static IP's?

This is just a guess, but since you do not have static public IP's from comcast, maybe try plugging router 2 into router 1. This way, they both get internet conections, but the subnets are isolated from one another. Otherwise you may have to get static IP's or get a 3rd router instead of the switch.

-DJ

 

[ShackDaddy]

You can't route between IP networks by having DNS help you out. You are trying to apply a layer-7 solution to a layer-3 problem.

Even when you set up VPNs, which may be a solution here, you typically set them up with IP addresses, not FQDNs.

If I were you, I'd designate a computer on the inside as the router and put two NICs into it. Make it the default gateway for both subnets and tell it to send non-local traffic to the outside routers. That would make things a lot simpler and less likely to break every day.

DJ's second solution might also be a good one: it's essentially the same solution I'm suggesting, with a different way of going about it.

ShackDaddy

 

[djtech2k]

Agree with ShackDaddy completely. Using a machine to route traffic between 2 NIC's would also be a good way to go. I guess this depends on how much $$ or time you want to spend. If you are using personal routers and not business class routers, most can be bout for under $100 and configured easily.

 

[echz]

Like I said, I was thinking too hard for a solution (I kicked myself for not thinking of it - The 2 NIC idea is the way I went...

I put 2 nics in the test server and assigned it a static IP to the router that I'm using for the test environment dyndns.

Then I assigned the other NIC to receive by DHCP, and it grabs the DHCP from the production router, and I am able to work with everything as if I was on that network as well.

I guess in a sense, I'm basically just using the test server as a bridge at this point...but hey, it solves my problems

Thanks for all your tips and advice guys!