dougr37
asked on
Router config question on point to point setup
Hi we have a new T1 Point to point setup with Cisco 1841s on each end, I can ping from one side to the other via the desktops/servers but when I try to ping from the router on my side to anything on the other routers network it will not ping, email, file transfers and other network functions seem to work great other than any type of SQL connections it can take 10 mins to make SQL connections the following is the setup on the router on my end
Current configuration : 1160 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
!
boot-start-marker
boot-end-marker
!
no aaa new-model
ip cef
!
!
!
!!
!
!
!
interface FastEthernet0/0
ip address 192.168.201.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/1
description $ES_LAN$
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
ip address 172.*.*.1 255.255.255.252
service-module t1 timeslots 1-24
!
interface Serial0/1/0
no ip address
shutdown
!
router rip
network 192.168.201.0
network 192.168.204.0
network 192.168.205.0
no auto-summary
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 172.*.*.1
ip route 192.168.204.0 255.255.255.0 192.168.205.1
ip route 192.168.205.0 255.255.255.0 172.*.*.2
!
ip http server
!
!
control-plane
!
!
line con 0
line aux 0
line vty 0 4
login local
line vty 5 15
login
transport input all
!
scheduler allocate 20000 1000
end
Current configuration : 1160 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
!
boot-start-marker
boot-end-marker
!
no aaa new-model
ip cef
!
!
!
!!
!
!
!
interface FastEthernet0/0
ip address 192.168.201.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/1
description $ES_LAN$
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
ip address 172.*.*.1 255.255.255.252
service-module t1 timeslots 1-24
!
interface Serial0/1/0
no ip address
shutdown
!
router rip
network 192.168.201.0
network 192.168.204.0
network 192.168.205.0
no auto-summary
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 172.*.*.1
ip route 192.168.204.0 255.255.255.0 192.168.205.1
ip route 192.168.205.0 255.255.255.0 172.*.*.2
!
ip http server
!
!
control-plane
!
!
line con 0
line aux 0
line vty 0 4
login local
line vty 5 15
login
transport input all
!
scheduler allocate 20000 1000
end
What is the clients default gateway on each end of the T1? The 1841 or a local Firewall for Internet access?
ASKER
On my side the Kentucky side my default gateway is 192.168.201.1 the default gateway in Salem is 192.168.205.1
On the Salem side, is 192.168.205.1 the LAN interface of the 1841? or a different device?
ASKER
yes my side gateway 192.168.201.1 is my 1841 and the salem side 192.168.205.1 is the 1841 on their side.
That is interesting, you say you can't ping from your router to the 192.168.205.x hosts? You should be able to as long as the gateways are the 1841's.
Where does the 192.168.204.x subnet come into play? Is that part of the equation?
Where does the 192.168.204.x subnet come into play? Is that part of the equation?
The routers I'm sure connect to a switch...we experienced this type issue when there was a speed/duplex mismatch between the router switch or the switch server. The fact that any traffic is being passed may indicate the issue may not be on the routers. Something else may be breaking the transmissions.
Can you ping 192.168.201.1 from the Kentucky router?
ASKER
The .204 subnet is another network on the Salem end of the T1
Is that the subnet you can't ping from your router?
Add a route for it and remove the invalid route:
no ip route 192.168.204.0 255.255.255.0 192.168.205.1
ip route 192.168.204.0 255.255.255.0 172.*.*.2
Add a route for it and remove the invalid route:
no ip route 192.168.204.0 255.255.255.0 192.168.205.1
ip route 192.168.204.0 255.255.255.0 172.*.*.2
ASKER
Yes I can ping the 192.168.201.1 and the 192.168.205.1 from either router
Couple things:
1) The static route statement "ip route 192.168.204.0 255.255.255.0 192.168.205.1" is incorrect. It should (probably) be "ip route 192.168.204.0 255.255.255.0 172.x.x.2"
2) There's no need to mask inside private addresses. Nobody can access them anyway, especially on a point-to-point T1 link.
3) You've got RIP and static routes. Can you post the routing table for both routers.
1) The static route statement "ip route 192.168.204.0 255.255.255.0 192.168.205.1" is incorrect. It should (probably) be "ip route 192.168.204.0 255.255.255.0 172.x.x.2"
2) There's no need to mask inside private addresses. Nobody can access them anyway, especially on a point-to-point T1 link.
3) You've got RIP and static routes. Can you post the routing table for both routers.
ASKER
Ky side
East-Bernstadt#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 172.*.*.2 to network 0.0.0.0
172.30.0.0/30 is subnetted, 1 subnets
C 172.30.1.0 is directly connected, Serial0/0/0
C 192.168.201.0/24 is directly connected, FastEthernet0/0
S 192.168.204.0/24 [1/0] via 192.168.205.1
S 192.168.205.0/24 [1/0] via 172.30.1.2
S* 0.0.0.0/0 [1/0] via 172.*.*.2
Salem Side
Salem#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
level-2
ia - IS-IS inter area, * - candidate default, U - per-user
static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 192.168.205.101 to network 0.0.0.0
172.*.*0/30 is subnetted, 1 subnets
C 172.*.*.0 is directly connected, Serial0/0/0
S 192.168.201.0/24 [1/0] via 172.*.*.1
S 192.168.204.0/24 [1/0] via 192.168.205.101
C 192.168.205.0/24 is directly connected, FastEthernet0/0
R 192.168.206.0/24 [120/1] via 192.168.205.101, 00:00:25,
FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 192.168.205.101
East-Bernstadt#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 172.*.*.2 to network 0.0.0.0
172.30.0.0/30 is subnetted, 1 subnets
C 172.30.1.0 is directly connected, Serial0/0/0
C 192.168.201.0/24 is directly connected, FastEthernet0/0
S 192.168.204.0/24 [1/0] via 192.168.205.1
S 192.168.205.0/24 [1/0] via 172.30.1.2
S* 0.0.0.0/0 [1/0] via 172.*.*.2
Salem Side
Salem#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter
area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type
2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
level-2
ia - IS-IS inter area, * - candidate default, U - per-user
static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 192.168.205.101 to network 0.0.0.0
172.*.*0/30 is subnetted, 1 subnets
C 172.*.*.0 is directly connected, Serial0/0/0
S 192.168.201.0/24 [1/0] via 172.*.*.1
S 192.168.204.0/24 [1/0] via 192.168.205.101
C 192.168.205.0/24 is directly connected, FastEthernet0/0
R 192.168.206.0/24 [120/1] via 192.168.205.101, 00:00:25,
FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 192.168.205.101
So, what exactly is the problem? From what to what doesn't work?
Since you are running RIP and you have more subnets than first let on, fix the RIP config on the 1841's:
router rip
network 172.x.x.x <--the serial subnet
Also, make sure you remove this route:
no ip route 192.168.204.0 255.255.255.0 192.168.205.1
Since you are running RIP and you have more subnets than first let on, fix the RIP config on the 1841's:
router rip
network 172.x.x.x <--the serial subnet
Also, make sure you remove this route:
no ip route 192.168.204.0 255.255.255.0 192.168.205.1
Can the 192.168.205.0 PC's ping the 172.30.1.1 address?
If they can and the Kentucky router can't ping them back, then it's probably the firewall on the PC's blocking ICMP requests.
If they can and the Kentucky router can't ping them back, then it's probably the firewall on the PC's blocking ICMP requests.
ASKER
The only real issue is any connections to our SQL server on the 192.168.205.* network takes about 10 mins to connect, and can't ping from the Ky router to andy Salem Hosts
For the SQL slowness, I assume this slowness isn't present on the 192.168.205.x subnet, right? I would double check speed/duplex settings on the router and switch ports on the Kentucky side. What is the bandwidth utilization on the T1 when SQL is slow?
ASKER
No SQL is fine on the Salem end the 192.168.205.* all the switches are running full duplex gig copper, the routers are set to auto speed auto duplex, will have to check on the utilization, and thanks to everyone for all the help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.