Problem networking between two LANs
I am having some trouble getting a computer on one LAN segment to talk to a NAS or another computer on a different LAN segment. Here is a quick diagram of what I have: Segment A Segment B 10.0.0.1 10.0.0.2 192.168.1.1 (INTERNET)-----<10.0.0.0/24>---------------<192.168.1.0/24>-----------[192.168.1.252] |___[10.0.0.6] I want 0.6 to talk to 1.252 and I thought I could do that by making a static route in 0.6's routing table with the route command. Either I have not been doing it correctly or it was not working. All the devices on segment B can use the internet and can ping segment A, but computers on segment A cannot ping computers on B. The 10.0.0.0 network is a Comcast Digital Voice Router and the 192.168.1.0 network is a linksys router. Thank you for your time.
May 4th, 2012 1:57pm

So the most likely issue here is that your linksys router has NAT enabled. I believe this is so based on the fact that you indicated that SegmentB computers can already communicate with A and the internet. For all Segment A computers to speak with all B computers, NAT will need to be disabled on Linksys. However, if NAT is disabled, now you have to manage the routing tables for the Comcast router. This is because when traffic leaves the 192.168.1.0 network outbound to the internet, it will no longer be NAT'd by linksys, reach the Comcast go out, but when it returns, the Comcast will not have any routing information about the 192.168.1.0 segement. This is not a big deal to turn off NAT'ing on the linksys, but you do need to know how to set up one static route on the comcast router for the 192.168.1.0 network. You do not need to create a static route on the linksys. The linksys just needs to have a gateway, which will be the comcast router (10.0.0.2) so it knows how to send packets out. As far as the computers on SEgment A to get to segment B, you do not need to have any static routes on those computers. Once you add the static route on the comcast router, when Segment A computers need to get to 192.168.1.0 network, they will send their packets to the gateway (comcast router), then the comcast router will send the packets to the linksys router. Generally in a real world scenario, you would consolidate both the comcast router and linksys router into one router with two ethernet interfaces (10.0.0.x & 192.168.1.x) hope this helps, let me know if you need further clarification. Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 2:28pm

Hello, I agree with Jorge about what the problem is. Two NAT routers are not going to cut it. My question is WHY do you have two subnets? If it's to reduce broadcasts, you can use VLAN's more simplistically. The easiest fix is to get rid of the two subnets and move the NAS into Segment A. Otherwise, you will need a router to route traffic between the two subnets ( i.e. a Cisco with two LAN WIC's or a Windows Server with two NIC's and RRAS) or Bridge Comcast and get a router (such as a Sonicwall) where you can use the OPT port as your second subnet. Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog
May 4th, 2012 9:24pm

I have it setup like this because of the locations of my devices and I am forced to use the the Comcast router because I subscribe to their digital voice service. The Comcast comes in from one part of the house (I have a computer next to it), and I have a USB printer plugged into the linksys router as well as other devices on the other side of the house. I only have one cable long enough to reach from the Comcast router to the other router and since I am using the linksys as a print server I need both networks. I also don't like security options on the Comcast router because the firmware on it will only let you do very basic configuration; I would prefer to have my devices on the linksys network. I guess my problem is with the Comcast router, since it only has very basic configuration options, I can't do something like set a static route... That is why I was trying to use a static route on the 0.6 computer, to get around that. Perhaps I can setup a VPN from the 192.168.1.0 side of the network... Since I can do things like remote desktop and ping the 0.6 computer from the 192.168.1.0 network, that might allow me to keep my current setup... But it is not ideal... Thoughts?
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 11:57pm

The VPN idea that I had did not really workout. I can however map my NAS and remote desktop into the 0.6 computer and copy what I need off of the NAS onto the harddrive of the 0.6 computer.
May 5th, 2012 1:24am

Hello, If you want to use your own router, you should bridge the Comcast router so that you don't double NAT. I would suggest you set up the Linksys in swicth mode and use it as a wireless access point and print server. Otherwise, use a switch at the far end oif the house. This will allow you access and gets rid of having two subnets.Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 10:59am

If I use the Comcast router in a bridge mode I would be able to have the 10.0.0.6 connected to the network (The computer closest to the Comcast router). If I move the linksys router I would have to move the printer as well.
May 5th, 2012 12:21pm

If you do not have the ability to reconfigure the Comcast router, another suggestion is to disable NAT on the linksys, and just let it route between both subnets. Then add static routes on each workstation on the 10.0.0.x subnet. Help on how to use the Route command.Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 12:31pm

If I use the Comcast router in a bridge mode I would be able to have the 10.0.0.6 connected to the network (The computer closest to the Comcast router). If I move the linksys router I would have to move the printer as well. If that's the case then leave the comcast router as it is (providing the NAT) and set up the linksys at the far edge as a switch. If you want more conbtrol over the NAT, then just bridge the comcast router, buy another router and set it up in front of the comcast router and leave the other linksys at the far edge working as a switch. This will provide you wireless coverage at the far end of the house and you will not have to move the printer.Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog
May 5th, 2012 5:24pm

I missed the part of that you have each router in a different part of the house. Now I understand what your design is about. If there is no requirement for two subnets, Miguel's suggestion regarding just turning the linksys into a plain switch (bridge the wan and switch ports) is a much better option. The best design option is always simplification. Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 6:24pm

Thank you for your responses and ideas, I think what I will do is get a USB print server that I can plug into a switch and moving my linksys router. I was trying to find a solution that I did not have to spend money and could use what I had already, that is why I set it up the way I did. I think it would work if I had more control over the comcast router but I guess moving the linksys router would be my best solution.
May 5th, 2012 10:50pm

hello Brian, Again, after review of this thread, the last suggestions about configuring your linksys router into a bridge is a no cost option. If you remove the routing config from your linksys and configure it a a switch (all ports are bridged), then you can create one logical subnet on your network. The IP scheme for you entire network will be 10.0.0.x. You do not have to touch the comcast router for this to work. Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2012 12:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics