Discussion Locked

PPP config of cisco 1721's

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am setting up a point-to-point over a full T1 line between 2 offices I can communicate via the serial interfaces between the 2 routers. From the host router I can ping the Remote Ethernet side of the remote router and PC's on the remote network. I cannot ping the server or other PC's on the host network from the remote router or remote PC's. All the interfaces and line protocols are showing as up. I can ping the ethernet side of both routers and I can ping each router from it's respective network and vice versa. Below are the router configs. Any help would be greatly appreciated. Thanks.

version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Host
!
no logging console
enable secret 5 ***************************
enable password *********
!
ip subnet-zero
!
!
!
!
!
!
!
interface FastEthernet0
ip address 192.168.100.1 255.255.255.0
speed auto
full-duplex
!
interface Serial0
ip address 192.168.1.1 255.255.255.0
encapsulation ppp
no fair-queue

!
ip classless
ip route 192.168.101 255.255.255.0 192.168.1.2
ip http server
!
!
line con 0
line aux 0
line vty 0 4
password **********
login
!
no scheduler allocate
!
end

version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Remote
!
no logging console
enable secret 5 *********************
enable password ******
!
ip subnet-zero
!
!
!
!
!
!
!
interface FastEthernet0
ip address 192.168.101.1 255.255.255.0
speed auto
full-duplex
!
interface Serial0
ip address 192.168.1.2 255.255.255.0
encapsulation ppp
no fair-queue
!
!
ip classless
ip route 192.168.100.0 255.255.255.0 192.168.1.1
ip http server
!
!
line con 0
line aux 0
line vty 0 4
password ********
login
!
no scheduler allocate
!
end

4 replies

by aj_arunkumar

going by the info provided by you i understand that problem is with the default gateway on the host network & the host server. 1)either the default gateway has been wrongly specified on the host networks pc's and server. 2)or there is no default gateway specified on the host network. try specifiying the default gateway as 192.168.100.1 on the host n/w. hope this should solve your problem.

by cw

Well from your configuration your problem is obvious.

Your route statement on the first router
ip route 192.168.101 255.255.255.0 192.168.1.2
is wrong.

Look at the destination network address. 192.168.101 ???

This is not even a complete IP address. You are missing the fourth octet.

Secondly you are running the same network address on both remote subnets. This is bad routing. Your first network, should be 192.168.100.0 /24, and your second network should be 192.168.200.0 /24.

Then make your route statement on the first router as follows.

ip route 192.168.200.0 255.255.255.0 192.168.1.2

On the second router the route statement is as follows

ip route 192.168.100.0 255.255.255.0 192.168.1.1

Now your two networks will talk.

Also since you are doing a point to point DS1 circuit, I would change your subnet mask on the serial interfaces of your routers to a 30 bit mask, or 255.255.255.252.

This is just a good routing and security practice, as you will never use more than 2 addresses on that subnet.

Good question. Thanks for the router configuration.

Have fun

Chris Weber CCDP

and

by cw

Sorry, I was mistaken with my second point. You do have two different subnets, 192.168.100.0 and 192.168.101.0. My bad.

But my first answer still sticks, and is the source of your problem

by dplewis

Previous answers v. good - only thing i'll add is that incorrecly defined subnet masks on hosts / clients in question can also create similar symptoms. Although when using 192.168.x.x this doesn't usually happen (as it's a native Class C subnet). This often occurs when using 10.x.x.x, as the subnet mask in client software usually defaults to 255.0.0.0 unless specified otherwise.

This discussion is closed to new replies.