Help...Trying to connect 2 networks???

[chattgroup]

Site A - established (172.x.x.x) network Cisco 2620 router MAIN NETWORK (INTERNET, SERVERS, DNS, ETC.)
Site B - new install (10.x.x.x) network Cisco 2612 router JUST LINKING TO MAIN SITE

T1 connection is established and I can see both the internal and external addresses on the routers yet I cannot ping/see other IP addresses past the switches the routers are plugged into. What type of routing needs to be setup on the switches? Or is it something else on the routers?

Thanks,
chattgroup

 

[gturrubi]

Since you have two different netoworks that means that you subnet mask is different as well. Are you using eigrp, rip, or ospf between the networks? How are these devices going to talk to each other, through what interfaces and routing protocol?

 

[chattgroup]

Below is our current config. We are using EIGRP and a PPP encap.

ip subnet-zero
!
interface Ethernet0
ip address 172.16.x.x 255.255.0.0
no ip directed-broadcast
!
interface Serial1
ip address 55.1.0.5 255.255.255.252
no ip directed-broadcast
encapsulation ppp
no ip mroute-cache
no fair-queue
!
router eigrp 10
network 10.0.0.0
network 172.16.0.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 55.1.0.6

Thanks for your reply,
chattgroup

 

[Frenchie2069]

Silly question, but have you set the default gateway to 172.16.x.x (or 10.x.x.x) on the device that you are pinging?

If you are running EIGRP then there is no need to have the static route entry, both networks should appear in the routing tables of both routers (show ip route will verify this). Check that the routers are forming an adjacency (show ip eigrp neighbor).

HTH,
Michael.

 

[chattgroup]

Yes, the default gateway is set on the devices. Another thing that might help is, when try to ping from the (172.16.x.x) network to the (10.x.x.x) I have to change my default gateway on my computer to the ip on the router to be able to ping anything on the 10. side.

Any suggestions???

chattgroup

 

[jwi71]

How complex is your setup?

Do you have multiple routers at your main site necessitating the use of EIGRP? From your description, it sounds like the remote site is a stub. Just use a static route from remote site to main and add a route from main to the remote site.

 

[chattgroup]

Okay, here is our setup...

We have a router to a watchguard (watchguard is our GW) then it breaks down to our network (just like any standard network). This is our main site (172.16.x.x).

Inside our network we have a VX Encore CSU/DSU for our remote location to connect through. On data port on the CSU, we have the Cisco 2600 router which then plugs into our backbone switch.

At the remote location (10.x.x.x), everything is static mapped (all pcs and wireless devices) and will connect to Site A for all mainframe access and internet access.

The connection is made already.

The first problem is the 10.x.x.x actually sees the servers and internet or anything past our backbone switch (Cisco 3550).

The second problem is that when I am on the 172.16.x.x network, I can not ping anything on the 10.x.x.x network without changing my default gateway on my pc to reflect the internal address on the router. I know that this is due to my default gateway on my 172.16.x.x network is the watchguard.

HELP

 

[jwi71]

I dont follow you on this:

"The first problem is the 10.x.x.x actually sees the servers and internet or anything past our backbone switch (Cisco 3550)."

Did you mean cannot?

As for the second problem, run a trace from 2620 to 2612. One hop, simple.
Run a trace from a pc (with firewall inside IP) to the 2612.
Run a trace from the pc using the router IP to the 2612.
Compare the results and I bet you are having issues with the firewall. To test, run a trace from inside the firewall to the 2612.

Looking at those traces will help you determine the culprit (my prime suspect is the watchguard).

J

 

[chattgroup]

I do mean "cannot" see the servers etc...

I am about to try tracing

Thanks,
chattgroup

 

[chattgroup]

Okay, when I trace...with the watchguard IP it tries to send me to the outside and Request Times Out

With the router IP, it hops no problem

What needs to change on the watchguard? A route from 10.x.x.x to Router IP?

chattgroup

 

[jwi71]

Good. We're making progress.

At this point though, I must proclaim Watchguard ignorance.

I honestly know zilch about them. You are on the right path though and the firewall is most definetly the problem.

Wish I had a better reply, but I don't.

Good luck and post the fix when you solve it.

J

 

[chattgroup]

The route between 172.16.x.x to 10.x.x.x is up and running now. We had to add a route on the watchguard to the ip on the internal router at Site A and everything is good there.

Thanks for everyone's help,
chattgroup