Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ASAP Help!!! Basic Route for WAN in 1720

Status
Not open for further replies.

underzen

MIS
Mar 5, 2002
20
US
Here is my situation. The guy from Sprint left because a dispute with my boss. Our 56k leased line is up and functioning. When I am inside router A i can ping router B and vice versa. The problem that I am having is that non of the pc's on the network for router A can see the pc's in router B. I am able to ping router A and B from a pc on the network on router A or B, I just can't ping any of the pc's from network A to network B. Here is the configuration that the Sprint guys started. I am not a Cisco guy but have a little bit of router expierence. The Sprint guy was in the middle of configuring the routers and then got into an argument and walked out. So any help here would be appreciated.

Using 1014 out of 29688 bytes
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Cisco1720
!
enable password 7 09414304
!
memory-size iomem 25
ip subnet-zero
no ip domain-lookup
!
!
!
!
interface Serial0

description connected to CorporateNetwork
ip unnumbered FastEthernet0
no ip directed-broadcast
encapsulation ppp
!
interface Serial1
no ip address
no ip directed-broadcast
shutdown
!
interface FastEthernet0
description connected to EthernetLAN
ip address 10.1.1.100 255.255.255.0
no ip directed-broadcast
no keepalive
!
router rip
version 2
passive-interface Serial0
network 10.0.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0
ip route 10.1.1.0 255.255.255.0 FastEthernet0
no ip http server
!
snmp-server engineID local 00000009020000B064C761D9
snmp-server community public RO
!
line con 0
exec-timeout 0 0
password 7 07022C41
login
transport input none
line aux 0
line vty 0 4
password 7 07022C41
login
!
no scheduler allocate
end
 
Scott- dont misunderstand my *original* post.. which was just a idea of something I had done before to why you *might* want to have packets go out the interface they came in on.. I never said that is what the tech was wanting to do.. I was making the slightly muddled point that something that appears to be crazy might in fact be a very rational way of doing something in an extreme case(or political)

I intentional left it vague to as to how it might apply if at all. I do that alot if I dont have alot of hard data in front of me or the time to tear into the config file. It's an idea.. or an experience and generally not much more then that unless pressed.. like this ;-)

MikeS
Find me at
"The trouble with giving up civil rights is that you never get them back"
 
MikeS,

Well I never dismiss anything just because I don't immediately see the use/functionality. That was my reason for pressing. And you are very correct about wild and seemingly ridiculous configs having a perfectly good reason for being. Thanks for taking the time to explain your experiences. As someone who mostly works in the WAN environment, I don't get to see some of these crazy things that you guys do. Thats a big part of why I hang around these forums. You learn something new every day.

Regards,

Scott
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top