Unsolved

This post is more than 5 years old

12 Posts

20109

January 7th, 2005 14:00

2 separate subnets??

Hi I have a question of how we can connect two servers, one is Win 2003 Standard (I'm going to give you IP example: 192.168.1.126) and Linux Enterprise server (192.168.1.110), and we have two separate 3324 switches, (192.168.1.100 and 192.168.1.101) also we have Watchguard Soho 6tc firebox (192.168.1.1).
 
Now, The Firebox is connected to two separate 3324 switches, on port 1, and the Win2003 server is connected to switch 1 g1, and Linux server connected to switch 2 g1.
 
Now, I don't have any problem at all for users and servers accessing to the internet.
 
Now, our goal is that we like to have two separate subnets, the Win 2003 server currently the same, 192.168.1.126 and the linux server will change to 192.168.2.126. And switch 1 will be the same, 192.168.1.100 and switch 2 will change to 192.168.2.100.
Now the problem is that the gateway is 192.168.1.1, and the switch 2 will not accept the gateway IP because it's a different subnet (192.168.2.x). Is there a way to have switch 2 to communicate to firebox (192.168.1.1)??
Any help greatly appreaciated! Or any better way or idea?
RSM

2 Intern

 • 

812 Posts

January 7th, 2005 14:00

You would need a router or Layer 3 switch to provide a separate gateways for each subnet. If the firebox provides routing, you should be able to configure it to route between the subnets and provide a gateway for your internet connection.

12 Posts

January 10th, 2005 12:00

Ok.. I'll check that on WatchGuard Soho 6tc... I'm not sure if it is supported.

Thanks!

RSM

12 Posts

January 10th, 2005 15:00

I set the WatchGuard Soho 6tc route table, address is 192.168.2.0/24 and gateway 192.168.1.1. Now when I got on PowerConnect 3324 (IP: 192.168.2.100)  to be sure the gateway IP address is correct but apparently the gateway ip address will not accept 192.168.1.1.
 
Did I do something wrong here?
 
RSM

2 Intern

 • 

812 Posts

January 10th, 2005 16:00

The switch will not allow you to configure a default gateway for a network it does not know about. If the switch has been configured with an IP address in the 192.168.2.x /24 network, the gateway would need to be in the same network (ex. 192.168.2.1).
 
For the Watchguard to route between these networks, you would need to configure an IP address (either on a VLAN interface or physical port) that will serve as the gateway for the 192.168.2.x network.

0 events found

No Events found!

Top