2514 with 2 subnets

[mikefairbanks]

I am trying to setup a Cisco 2514 with 2 subnets on eth0 & eth1, but I can't get them to see each other. This certainly seems simple, but I can't find any information that has helped.

Here's the setup, Eth0 is 192.168.0.252/24, and Eth1 is 192.168.1.1/24... I want PCs on one subnet to be able to see the other. All PCs on both subnets can see both router ports, ie, PC 192.168.1.2 can ping router Eth1 @ 192.168.1.1,and router Eth0 @ 192.168.0.252... but it can't ping any of the hosts on the 192.168.0.0 subnet, it is configured with a default gateway of 192.168.1.1.

Here's my current configuration...

Current configuration : 924 bytes
!
version 12.1
service config
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname router
!
enable secret 5 $1$X3Od$ZLUj4AdPG1chg2IoI4E.S.
enable password xxxxxxxx
!
ip subnet-zero
ip name-server 192.168.0.2
!
interface Ethernet0
ip address 192.168.0.252 255.255.255.0
no ip mroute-cache
no cdp enable
!
interface Ethernet1
ip address 192.168.1.1 255.255.255.0
no ip mroute-cache
no cdp enable
!
interface Serial0
no ip address
no ip mroute-cache
shutdown
no cdp enable
!
interface Serial1
no ip address
no ip mroute-cache
shutdown
no cdp enable
!
ip classless
ip route 192.168.0.0 255.255.255.0 Ethernet0
ip route 192.168.1.0 255.255.255.0 Ethernet1
no ip http server
!
no cdp run
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password xxxxxxxx
login
!
end

 

[mikefairbanks]

Never mind, I figured it out... the problem wasn't with the router config, but with the PC's on the 192.168.0.0 subnet still being configured for a different default gateway. I added a route for the 192.168.1.0 subnet and everything is working now.

Mike

 

[ROUTERKID1]

Looks good you could have used a routing protocol like Rip as well...

 

[plshlpme]

u don't need those static routes...
they are configured on the interfaces
so if you do a sho ip route
youll see they are their via connected since connected are better routes then static....

the problem the whole time was the default gateway error on your pc..

 

[jneiberger]

Routing protocols and static raoutes are irrelevant in this situation since both networks are directly attached to the same router. When you see symptoms like this it's almost always caused by a bad default gateway or subnet mask.