Cisco Packet Tracer - Troubleshooting Assessment

[TRAWP]

Hey everyone,
Just wondering if anyone has any advice for me, currently doing a troubleshooting assessment and at wits end of what else can be done.

Basically there is 4 routers in the system, 3 all on the same network on a 192.168.x.x network. Bar one which is on a 63.122.x.x network. The rest of the network talks with each other and can even talk to this router, but cant talk to anything passed this router.

It's obviously something inside this router which is causing the issue, i've looked twice and three times at the configuration and nothing springs to mind that could be causing the issue.

MELB#show run
Building configuration...
 
Current configuration : 623 bytes
!
version 12.4
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname MELB
!
!
!
!
!
!
!
!
!
!
!
!
!
!
spanning-tree mode pvst
!
!
!
!
interface FastEthernet0/0
description To Server0
ip address 63.122.12.5 255.255.255.252
duplex auto
speed auto
!
interface FastEthernet0/1
description To RHOMS Eng
ip address 63.122.12.2 255.255.255.252
duplex auto
speed auto
!
interface Vlan1
no ip address
shutdown
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/1
!
!
!
!
!
!
!
line con 0
!
line aux 0
!
line vty 0 4
login
!
!
!
end

Like I said I can send packets to this router and back, but cannot do so passed this router which has a web server connected to it. I've double checked all IP addresses and everything, I've already fixed 4-5 issues with this configuration for this router already. Any help would be fantastic.

 

[TRAWP]

Moments after posting this, after troubleshooting this for a day I figured it out.

 

[dylan123]

You currently studying CCNA?

 

[TRAWP]

Yep, only a week left haha.

 

[dylan123]

I take it you're doing CCNA 3/4? Got my CCNA Security exam next week.

 

[TRAWP]

Haha, I dont envy you. And you hit the nail on the head. Glad when this years over though and get back to work haha

 

[dylan123]

Haha, I dont envy you. And you hit the nail on the head. Glad when this years over though and get back to work haha

Can't wait to never touch cisco again either.

 

[TRAWP]

Can't wait to never touch cisco again either.

I was about to say "Sadly i'll be using it again soon" but thinking of what you said. I probably wont use it again whilst working haha

 

[Chief]

Moments after posting this, after troubleshooting this for a day I figured it out.

 

[TRAWP]

Good point Chief

Basically I resolved this through going back to the router before the router in question and placed an ip route in. This then allowed traffic to move through the troublesome router to its network within. Pretty basic thinking back now, but at the time it seemed like an issue with the MELB router and not before it as traffic could still reach that router.

 

[NetworkNerd]

I'm shocked I wasnt tagged in this thread