1720 Routing IP Configuration Needed.

[matt21]

1720 Routing IP Configuration Needed.

I have two 1720's connected via Leased Line and I'm having trouble getting IP to route correctly. I thought I had everything working properly yesterday, but when I came in today, I could not route Internet traffic across to the remote location.

Here's my setup:

Western Office:

ISP DSL--NetGear FVS318 (192.168.1.1)---------|
HUB-----NT Server(192.168.1.11)
Cisco 1720 (LAN IP192.168.1.2)-------------------|
|
|
T-1
|
|
|
| Augustine Office:

Cisco 1720 (LAN IP 192.168.2.2)

------------------------------------------------------------------------------
If I put a static route of 192.168.2.0 to 192.168.1.2 on the NetGear then I can ping from Augustine to my NT Server on Western. But no internet access.

Western Cisco IP Route:

Gateway of last resort is 192.168.2.2 to network 192.168.2.0

66.0.0.0/30 is subnetted, 1 subnets
R 66.161.151.224 [120/2] via 192.168.1.1, 00:00:14, FastEthernet0
C 192.168.1.0/24 is directly connected, FastEthernet0
* 192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.2.2/32 is directly connected, Serial0
S* 192.168.2.0/24 [1/0] via 192.168.2.2
R* 0.0.0.0/0 [120/1] via 192.168.1.1, 00:00:14, FastEthernet0

Augustine Cisco IP Route:

Gateway of last resort is 192.168.1.2 to network 192.168.1.0

R 66.0.0.0/8 [120/3] via 192.168.1.2, 00:00:25, Serial0
* 192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
S* 192.168.1.0/24 [1/0] via 192.168.1.2
C 192.168.1.2/32 is directly connected, Serial0
C 192.168.2.0/24 is directly connected, FastEthernet0
S* 0.0.0.0/0 [1/0] via 192.168.1.2


Any insight or help is appreciated.

Thanks,

Matt

 

[netmediasystems]

matt - just by quickly looking at your config, it looks if you have the remote location looking just to the main office...no internet dns servers are listed. you have a strict point to point configured. are you able to resolve internet addresses at any point on the network?

brian

 

[matt21]

Brian:

I have the same DNS Servers set-up at both locations on each client PC. At the main location(Western), I can resolve addresses at the remote location I can not resolve addresses. Oddly, it worked yesterday but this morning when everyone came in it did not work. Nothing was changed. The only thing I can think of is maybe there is a problem with RIP and the Netgear.

 

[netmediasystems]

matt - i would attempt to see if any "clear" commands reestablish internet connectivity. I do not believe that the routing protocol would be the causing this type of issue. do a clear arp and see if that helps. after that do a show arp and let me know if the dns servers appear in the list...or at least the gateway to which the dns servers exist.

brian

 

[matt21]

One moer bit of information that I just found. If I do a trace from the Augustine Router to the DNS Server, the packet just bounces between the two routers until the TTL expires. I'm guessing I have some type of loop.

Matt

 

[netmediasystems]

is the remote office trying to resolve dns through the ip route(the main office) ???

 

[matt21]

Yes, it's trying to resolve dns through an external server.

 

[ChrisAC]

Could you post the router configs?

Chris.
**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[help24ca]

matt21,

From your original post, I believe that your interfaces are configured as:

Netgear:
- eth0: ip addr 192.168.1.1 255.255.255.0

Western:
- fa0: ip addr 192.168.1.2 255.255.255.0
- s0: ip addr 192.168.2.2 255.255.255.255

Augustine:
- fa0: ip addr 192.168.2.2 255.255.255.0
- s0: ip addr 192.168.1.2 255.255.255.255

I am assuming that the NetGear router is the default gateway for all the hosts in the Western office and is routing/NAT to the Internet. If this is so, the most glaring issue is that the ip addresses of the serial interfaces connecting the two routers are not in the same network. My first suggestion would be to use something like:

Western:
- fa0: ip addr 192.168.1.2 255.255.255.0
- s0: ip addr 192.168.3.1 255.255.255.252
- ip route 0.0.0.0 0.0.0.0 192.168.1.1
- ip route 192.168.2.0 0.0.0.255 192.168.3.2

Augustine:
- fa0: ip addr 192.168.2.2 255.255.255.0
- s0: ip addr 192.168.3.2 255.255.255.252
- ip route 0.0.0.0 0.0.0.0 192.168.1.1

Then the routes on Western would be:
C 192.168.1.0/24 is directly connected, FastEthernet0
C 192.168.3.0/30 is directly connected, Serial0
S 192.168.2.0/24 via 192.168.3.2
S*0.0.0.0/0 via 192.168.1.1

and on Augustine:
C 192.168.2.0/24 is directly connected, FastEthernet0
C 192.168.3.0/30 is directly connected, Serial0
S*0.0.0.0/0 via 192.168.1.1

The NetGear box will also need to know the route to 192.168.2.0/24.

On the other hand, if the Western router is the default gateway for the Western hosts, then this is a little easier as the Augustine router uses this as its default route instead.

I hope this helps.

cheers,
help24ca@yahoo.ca