Solved How Can I Access Computers On A Different Network

Ultimate Office 2007 ultimate
March 11, 2014 at 07:54:14
Specs: Windows 8.1, I3/8GB
I am on domain network of 192.168.23.254 255.255.255.0 with dhcp server. a router on my domain obtain ip from the dhcp server and as we know creates its another network of 192.168.1.1 255.255.255.0. users on the routers network are able to access the domain network but users on the domain network are NOT able to access the routers network

See More: How Can I Access Computers On A Different Network

Report •


#1
March 11, 2014 at 08:41:23
✔ Best Answer
You would need to create a static route on the router that allows the 192.168.23.0 network into the 192.168.1.0 network

Actually, if this is a small network and that's a SOHO Router. The sensible thing would be to connect the uplink to a LAN port on the SOHO Router and give it an IP in the 192.168.23.0 network and shut it's DHCP service off. This would make it all one big network and give all clients access to each other.

For more info on how to do this simply click on my name above in this response and read my “how-to” guide titled, “Add a second Router to your LAN

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
March 11, 2014 at 09:40:23
Thanks so much Curt,

I would like to go for the version 2 of your procedure. But how do i do static route on cisco asa which is my ROUTER1 and or server 2008 which serves as dhcp server

message edited by thedzaho


Report •

#3
March 11, 2014 at 10:50:17
You would need to put a static route from 192.168.23.0 to 192.168.1.0 on whichever network appliance is between the two networks. I'm guessing that's the cisco asa.

As to how, that info should be in the manual.

I might be able to give you a little more help on how to add the route but in order to do so, I'd need to know the exact model of your cisco unit (again, if it's the device between the two networks).

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
March 11, 2014 at 19:05:21
Sounds like what was once called a "Trust" relationship in NT days?.

Report •

#5
March 12, 2014 at 01:43:01
Ok Curt,
Its Cisco ASA 5510 which has the public IP and the Router2(Dlink) obtains ip from the domain server.

Report •

#6
March 13, 2014 at 06:05:35
Ok, you're going to have to either add the route to the Dlink (it's the network appliance between the two networks), or as I said above, put it in the same network.

I would recommend the same network. There are only two reasons I can think off of the top of my head for adding a second, separate, network to your LAN:
1) Security
2) you've run out of IP's in the first network.

Since neither seems to apply to you, plug the uplink cable from the ASA into a LAN port on the Dlink. Give the Dlink a LAN IP in the same subnet as your ASA using the ASA's LAN facing IP as it's default gateway address.

If you already have a DHCP server running, disable the DHCP service on the Dlink.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question