805 routing woes

[kirkfreeport1]

Hi all

I have 2 cisco 805s connceted by leased line using PPP.

I can telnet into each of them no problem, but cannot do anything else!

No ping, no network connection on my user PCs nothing.

Anybody want to have a look at these 2 confs and see where Im going wrong.

Home:

version 12.0

no service pad

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname KFRouterA

!

enable password 7 0215114B0E140D

!

!

!

!

!

ip subnet-zero

no ip source-route

!

no ip domain-lookup

cns event-service server

!

!

!

!

!

interface Ethernet0

description connected to KF Network

ip address 192.168.91.199 255.255.255.0

ip access-group 121 in

no ip directed-broadcast

no ip proxy-arp

!

interface Serial0

description connected to AWAY

bandwidth 64

ip address 192.168.200.1 255.255.255.252

no ip directed-broadcast

encapsulation ppp

fair-queue 64 128 0

!

router rip

version 2

network 192.168.91.0

network 192.168.200.0

no auto-summary

!

no ip http server

ip classless

ip route 0.0.0.0 0.0.0.0 Serial0

!

access-list 121 permit ip any any

access-list 900 permit any

snmp-server engineID local 00000009020000024B7D62CA

!

line con 0

exec-timeout 0 0

password 7 071C345C4B1B1B

login

transport input none

stopbits 1

line vty 0 4

password 7 071C345C4B1B1B

login

!

end

Away:

Current configuration:

!

version 12.0

no service pad

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname WH1Router

!

enable password 7 06151A31495C0B

!

!

!

!

!

ip subnet-zero

!

no ip domain-lookup

cns event-service server

!

!

!

!

!

interface Ethernet0

description connected to EthernetLAN

ip address 192.168.199.1 255.255.255.0

no ip directed-broadcast

!

interface Serial0

description connected to KFRouterA

ip address 192.168.200.2 255.255.255.0

no ip directed-broadcast

encapsulation ppp

no ip mroute-cache

!

router rip

version 2

network 192.168.199.0

network 192.168.200.0

no auto-summary

!

no ip http server

ip classless

!

snmp-server engineID local 00000009020000024B7D6307

snmp-server community public RO

!

line con 0

exec-timeout 0 0

password 7 111A0C15120009

login

transport input none

stopbits 1

line vty 0 4

password 7 111A0C15120009

login

!

end

Many thanks

[thisisshanky]

Did you check the gateway settings on your PCs ?? are they able to also ping their default gateways on their respective lans?

[kirkfreeport1]

Thanks for the prompt reply.

Yes (though I can't check it now). However we are trying to ping from home admin PCs through to away. Gateway on home PCs surely shouldn't matter?

Note there's a typo in the conf for home's serial network mask, .0, not .252!

This was all set up and working a few months ago in a test environment, but for IPX as well. We removed IPX (and obviously something else too), can't see any other differences, but the new line gets installed in the next week, so the 805s have to start earning a living.

To recap. If we telnet into 'home' we can ping or telnet out to anywhere. Ditto if we telnet into away. From a PC on the same network as home's e0 we can ping home's e0, but not s0 or anything over that port.

I suppose the question is 'what is missing from the 'home' conf?

[bcbvale]

Can you post the output from show ip route?

bcbv

[bena]

Im no expert here but.

Would it matter that you dont have the line

ip route 0.0.0.0 0.0.0.0 Serial0

on the Away router ? Thats all i can think of.

Also you might want to have a look at NAT.

[dnagarajachary]

On the away router as in the previous mail, you need to give ip route command, it doesnt know where to send the return traffic.

Also instead of specifying the outgoing interface, give the next hop ip address.

coz you are using a point to point link with static ip address. In this case, the next hop ip address need to be used in the ip rotue command. The outgoing interface is specified when the interface which is connected to outside has ip unnumbered.

Please try giving the next hop ip address in ip route command instead of serial 0

-Deepu

[kirkfreeport1]

As requested

(Home - KFRouter)

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C 192.168.91.0/24 is directly connected, Ethernet0

R 192.168.199.0/24 [120/1] via 192.168.200.2, 00:00:26, Serial0

192.168.200.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.200.0/24 is directly connected, Serial0

C 192.168.200.2/32 is directly connected, Serial0

S* 0.0.0.0/0 is directly connected, Serial0

(Away - WH1Router)

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

R 192.168.91.0/24 [120/1] via 192.168.200.1, 00:00:12, Serial0

C 192.168.199.0/24 is directly connected, Ethernet0

192.168.200.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.200.0/24 is directly connected, Serial0

C 192.168.200.1/32 is directly connected, Serial0

S* 0.0.0.0/0 is directly connected, Serial0 (added as per Bena's suggestion)

Network Diagram (if it clarifies anything)

network & servers 192.168.91.x

||

||

Home e0: 192.168.91.199

Home s0: 192.168.200.1

||

|| Leased Line

||

Away s0: 192.168.200.2

Away e0: 192.168.199.1

||

||

Switch and Wyse boxes on 192.168.199.x

On the other response:-

If we replace the ip route command 0.0.0.0 0.0.0.0 serial0

in home with a 'next hop' variation will we be referring to the leased line network or the literal next destination?

ie:

ip route 192.168.200.1 0.0.0.0 192.168.200.0

or

ip route 192.168.200.1 0.0.0.0 192.168.199.0

Isn't the biggest clue here that a home pc cannot ping (or ping past) the s0 interface on the home router? (ie I can't ping 192.168.200.1 or anything past that)

[rjackson]

All the talk about the static routes is irrelevent. RIP should be giving full connectivity to the far end. The fact that you cant ping the S0 interface on the same router whose ethernet you can ping makes it sound like the pc doesn't have its gateway or mask defined properly. Or that access-list 121 is not what it appears.

[thisisshanky]

I agree with Richard's post.

As I posted before, check your gateway settings on the PC.

[bcbvale]

As priviously posted, the static routes don't need to be there because of RIP. You may want to remove them to minimize the confusion. If you are confident that the default gateway on the pc's is set correctly to the ip address of the ethernet port on the local router then take a look at your netwask, especially on the serial interfaces. According to the sh ip route you have /32 mask on those interfaces. Doesn't look right to me.

bcbv

[kirkfreeport1]

Thanks for all the help so far guys, I really appreciate it.

As I understand you...I had the gateways incorrect. I have changed them accordingly.

I can remove the - ip route 0.0.0.0 0.0.0.0 serial0 statements from both routers.

I then setup my WYSE boxes gateway to the e0 address of the router its attached to (WH1Router/192.168.199.1)

The mask used is 255.255.255.0 throughout. (Cant figure out why its listing /32 there)

Then try it...

On a side note, is there a command to reboot the router from within telnet ?

[rjackson]

yes RELOAD

[9mmurphy]

Don't forget to "Write Mem" before you reload! ;=0

[thisisshanky]

Before reloading, make sure you save your configs.

[kirkfreeport1]

Thanks all.

This noob is learning stacks.

I seem to be getting somewhere at last. Have taken all suggestions into account, but have 1 small item that I still can't figure out.

Here is a ping list from configmaker.

KFRouterA, Ethernet 0 (192.168.91.199)... okay

KFRouterA, Async/Sync 0 (192.168.200.1)... okay

WH1Router, Ethernet 0 (192.168.199.1)... no response

WH1Router, Async/Sync 0 (192.168.200.2)... okay

Citrix Box, 10/100 Ethernet 0 (192.168.91.3)... okay

KF5, 10/100 Ethernet 0 (192.168.91.5)... okay

WYSE, 10/100 Ethernet 0 (192.168.199.2)... no response

Ping was partially successful.

Seems I now have access over the leased line, but thats where it stops. The Ethernet side and the WYSE box connected to it, I can't access.

I can confirm that the WYSE box has its gateway set at 192.168.199.1 and it can talk to the router. It doesn't seem to be able to hop over to the 192.168.200.x part to access our main network at 192.168.91.x

Any suggestions on what to try next.