Getting two subnets to see each other

J

jtetterton

n00b
Joined
May 11, 2005
Messages
41
Hey all... This may be a silly question, but I can't seem to figure it out.

This is what I have right now.

Surfboard Modem (Comcast Cable)

Primary Router -- WRT54G as DHCP SERVER for .1 subnet 192.168.1.1 (Running DD-WRT)
Several DHCP Clients on .1 subnet

Secondary Router -- WRT54G as DHCP SERVER for .2 subnet 192.168.2.1 (Standard Linksys firmware)
Several STATIC Clients on the .2 subnet
Several DHCP Clients on the .2 subnet

Currently, anything on the .2 subnet can ping 192.168.1.1 and 192.168.2.1

What do I need to do so that 192.168.2.20 can share resources and ping 191.268.1.200 and vice versa ?

Any help is appreciated, thanks.
 
I forgot to mention, a LAN port on 192.168.1.1 is connected to the Internet port on 192.168.2.1 and 192.168.2.1 gets it's "Internet" IP from the primary DHCP router.
 
Changing the subnet to 255.255.252.0 will make it so that you'll be able to see any 192.168.1-3.x.
 
ok, so just to verify, change the subnet mask of the 192.168.1.1 router from 255.255.255.0 to 255.255.252.0 ?

Thanks
 
Gott said:
The subnet would have to be 255.255.252.0 on both routers.
Click to expand...

Nope, it should only be set on the primary router. You want to have a smaller mask for your secondary subnet, or else you'll get scope issues.
 
Keiichi said:
Nope, it should only be set on the primary router. You want to have a smaller mask for your secondary subnet, or else you'll get scope issues.
Click to expand...

If he has devices connected to his network that are being connected/disconnected and his DHCP lease is set for a long time, he'd run into DHCP scope issues.

Not knowing his physical setup and the more I think about it, setting the subnet to .252.0 on his primary will be a better alternative for scalability purposes.
 
Here's another stumper... I have switched the subnet mask of the primary router to 255.255.252.0 as well as all the static devices on the 192.168.1.1 subnet.. Now here is one snag i've hit... I can access 192.168.1.201 from 192.168.2.20 but I cannot access 192.168.2.20 from 192.168.1.201. 192.168.2.20 has windows firewall OFF and has no third party security software installed.

Also, how can I use hostnames instead of IP addressing? I can ping certain machines by IP but not by hostname.

Thanks again for the quick replies.

Jason
 
Oops forgot to mention all of the devices/comps that have a static IP address connected to that segment would also need their subnet mask changed to 255.255.252.0 as well.

Also, how can I use hostnames instead of IP addressing? I can ping certain machines by IP but not by hostname.
Click to expand...
That's normal. Basically you're gonna need to first enable Netbios over TCP/IP or NetBT on the comps, then you're going to need either a WINS or a DNS server. It may be possible to do it in your routers, but I'm not familiar with them at all. You can always do the poor man's method and edit each computer's LMHOSTS file.
 
OK, Thanks.. any idea on why I can see one way but not the other? all firewalls are off.. The one that CAN be seen is vista business.. vista business cannot see xp pro on .2 subnet
 
jtetterton said:
OK, Thanks.. any idea on why I can see one way but not the other? all firewalls are off.. The one that CAN be seen is vista business.. vista business cannot see xp pro on .2 subnet
Click to expand...

The vista box is on the .1 subnet, with a static IP correct?
If it is, then it's a subnetting issue. Without getting overly technical, the subnet mask defines the boundaries on the range of IPs that a device can talk/listen freely to in it's segment.
 
You must log in or register to reply here.
Back
Top