cisco 3600 routing woes

[rasczak]

fe0/0 and fe0/1 are supposed to be able to pass traffic back and forth. currently this is not happening and i am lost as far as fixing it. (i am the only sys admin/network guy here but i rarely work on the network side of things.)

pc 192.168.2.2 -> generic switch > fe0/1 192.168.2.1 on cisco 3600 > cisco 3600

cisco 3600 < fe0/0 192.10.200.1 < generic switch < pc 192.10.200.2

this is at its simplest. if you need more clarification i'll try to provide it.

i just need a push in the right direction as far as what to look at first. i am REAL new to router/switch configuration and barely if ever touched IOS.

 

[spidey07]

make sure the PCs have the correct mask and gateway (which would be the 3600 interface on their local network). Make sure the router interfaces aren't shutdown, "show int f0/1" will show you if they are up or administrately shut down.

Also make sure the command "ip routing" is enabled on the 3600 and that it has routes to those networks "show ip route"

 

[RadiclDreamer]

If this is going to stay a simple network just follow spideys suggestion and if the show ip route comes up blank, throw in a static route or use eigrp/rip/etc here

 

[spidey07]

If this is going to stay a simple network just follow spideys suggestion and if the show ip route comes up blank, throw in a static route or use eigrp/rip/etc here

Also remember the routes won't show be in the table unless those interfaces have physical link.

 

[RadiclDreamer]

Also remember the routes won't show be in the table unless those interfaces have physical link.

I thought statics would, but to be honest I've never tried

 

[Cooky]

I don't think you even need to have static routes defined, since the two networks would show up as connected routes for fa0/0 & fa0/1.

Can PC's from each side ping their respective default gateways (the router interfaces)?
This should verify if the interfaces are up & functional. (also the generic switches)

 

[drebo]

Some configs might be helpful, too.

 

[spidey07]

I don't think you even need to have static routes defined, since the two networks would show up as connected routes for fa0/0 & fa0/1.

Can PC's from each side ping their respective default gateways (the router interfaces)?
This should verify if the interfaces are up & functional. (also the generic switches)

no route to next hop means it's removed from the routing table (technically forwarding table). But we're getting too deep for the OP.

 

[rasczak]

I don't think you even need to have static routes defined, since the two networks would show up as connected routes for fa0/0 & fa0/1.

Can PC's from each side ping their respective default gateways (the router interfaces)?
This should verify if the interfaces are up & functional. (also the generic switches)

yes. I have been able to ping both gateways with success from within their respective networks, even going so far as to be able to ping pc 192.10.200.2 > fe0/1 192.168.2.1, however, it's traffic going through this gateway that seems to really be the issue here. from pc 192.168.2.2 to fe0/1 192.168.2.1 pinging is fine, yet trying to ping fe0/0 192.10.200.1 times out.

as for configs I'll try to get what i can, however due do "security" I may be unable to comply with this request.

 

[drebo]

yes. I have been able to ping both gateways with success from within their respective networks, even going so far as to be able to ping pc 192.10.200.2 > fe0/1 192.168.2.1, however, it's traffic going through this gateway that seems to really be the issue here. from pc 192.168.2.2 to fe0/1 192.168.2.1 pinging is fine, yet trying to ping fe0/0 192.10.200.1 times out.

as for configs I'll try to get what i can, however due do "security" I may be unable to comply with this request.

Just obfuscate the passwords and remove any telephony and crypto information. There's no other "sensitive" information in a router config.

Without configs, we cannot tell you why this may not be working. We have no guarantee that you've configured this thing correctly for the scenario you paint in the OP.

 

[rasczak]

Just obfuscate the passwords and remove any telephony and crypto information. There's no other "sensitive" information in a router config.

Without configs, we cannot tell you why this may not be working. We have no guarantee that you've configured this thing correctly for the scenario you paint in the OP.

will do.

 

[spidey07]

The only part of the config that is needed is the respective interfaces - "show run int f0/1", etc. I want to see if there are any ACLs on there as well. Also again make sure the masks on the PC match the router. It is the routers that define what the subnet mask is, they define the network.

No routing protocols would be used because they're both directly connected routes. show ip route would help.

 

[Pablito74]

Are ip redirects on in the interface? Try it with "no ip redirect" under both fa0/0 and fa0/1. Since they are in the same switch, the pc might be getting a redirect and trying to talk directly at layer2. I would second a "show run int fa0/0" and "show run int fa0/1" at the least.

 

[rasczak]

figured it out guys. i'm such a dumbass.

traffic was going through it's the device (not a workstation) that sits behind fe0/1 192.168.2.1 which doesnt respond to ping requests. the way i figured it out, i setup another workstation on that same network, and was able to ping back and for to and from the workstation. i apologize that i didn't give you the correct information earlier and thanks for your assistance.

 

[drebo]

Layer 8 is often the most problematic.