Connection problem across a WAN link between 2 Servers

[ArmedAndClueless]

I have a problem with a fairly basic network. On one network, 10.0.0.0/16, I am running an Iomega NAS file server. Two networks across at 10.210.1.5/16, it cannot be pinged, nor browsed to. Between them are two Cisco 1700 series routers with a leased line between them. Here are the running configs.


version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname ROUT01
!
enable secret 5 $1$RuqO$64oTV9tJZgk6UigPJGik7.
!
ip subnet-zero
!
!
!
!
interface FastEthernet0
ip address 10.0.0.2 255.255.255.0
ip accounting output-packets
speed auto
half-duplex
!
interface Serial0
ip address 10.0.1.1 255.255.255.252
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.0.5
ip route 10.210.0.0 255.255.0.0 10.0.1.2
no ip http server
!
!
snmp-server community public RO
snmp-server community private RW
!
line con 0
line aux 0
line vty 0 4
password 7 1401005A080127
login
!
no scheduler allocate
end

This router is at the main site, where the DC and internet connection are. Also, this is where the NAS box in question is.

version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname ROUT02
!
enable secret 5 $1$r7J9$DgtrbfydMMsbjvAPT3QFP.
!
ip subnet-zero
!
!
!
!
interface FastEthernet0
ip address 10.210.1.5 255.255.0.0
speed auto
half-duplex
!
interface Serial0
ip address 10.0.1.2 255.255.255.252
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.1
ip route 10.0.0.0 255.255.0.0 10.0.1.1
no ip http server
!
!
!
line con 0
line aux 0
line vty 0 4
password 7 0719331D4A0C1B
login
!
no scheduler allocate
end

This is the other router, at a stub network. From the stub router, I can ping the internet gateway (10.0.0.5) but not the NAS box. (10.0.0.3). Inside the furthest network, I can once again ping the gateway but not the NAS box. What am I missing? Do I have a missing routing statement or something?

Oh, and here is a rough layout of the network.



Server NAS Box
| |
| |
Switch----ROUT02-----WAN Link------ROUT01-----Switch-----DC
| | |
| | |
Clients | |
Clients |
|
Internet

It seems like the only thing that can't be accessed is the NAS machine. The DC is readily accessible, and all of the machines to the left can get out to the internet. What is going on?

 

[ArmedAndClueless]

Correction to the topology, all the clients on the right, as well as the servers and internet, are hooked to the switch on the right. Layout error, sorry X-P

 

[Zen37]

Hi ArmedAndClueless (love that handle BTW)

First of all, i recommend changing the IP of your serial interface for it's on the same network (of sorts) as the 10.0.0.0/16

In theory, 10.0.0.3/16 and 10.0.1.2/31 can cause problems since there is a possibility of a 10.0.1.2/16 in your first network. It's probably not the cause of your issue, but it can lead to confusion and should be changed.

Second, what is the subnetmask and default gateway of your NAS device? Can you ping the device from the same network? If yes, then it's very probably routing issue. If not, then it's a layer 1 or 2 issue.

 

[ArmedAndClueless]

Thanks, yet once again, I have another error. I was typing without thinking. In reality, the network on the left runs a /16 while the router in the right runs a /24 network. Ah, they joys of VLSM! (choke)

However, something useful that did come to mind is that the net on the right iss using the same network address as the entire network of 10.0.0.0 . Could this be causing connection issues, a subnet having an overlapping network address with the whole network? I have never directly encountered an issue, but I get leery about doing that.

 

[Zen37]

According to your config (assuming you did not 'choke' on anything there ;-), there is an issue.

If your network overlaps, it's not good. If my memory serves me right, your /16 will be serviced before your /24, so if you have an identical address on each side, the /16 will get the bulk of the traffic.

Also, if you have a /24 on the network to the right, your IP route statement should be:
ip route 10.0.0.0 255.255.255.0 10.0.1.1

I recommend using a segment in the 192.168.0.0/16 network for your serial connections. It would make your design easier to understand when your LAN addresses are not on the same playing fields as your WAN addresses.

So i recommend you change your config to the following
for the left router (ROUT02)

Interface Serial 0
Ip address 192.168.2.2 255.255.255.252

Ip route 0.0.0.0 0.0.0.0 192.168.2.1
(not needed but you can still put it in) Ip route 10.0.0.0 255.255.255.0 192.168.2.1

On the right router (ROUT01)

Interface Serial 0
Ip address 192.168.2.1 255.255.255.252

Ip route 0.0.0.0 0.0.0.0 10.0.0.5
Ip route 10.210.0.0 255.255.0.0 192.168.2.2

Now your NAS must have the IP of 10.0.0.2 as a default gateway and a mask of 255.255.255.0

With that, everything should work.

 

[ArmedAndClueless]

All right, that is a great idea with the 192 network. I will try to implement that as soon as possible. However, the internet connection is on the right, the first network, while being a 10.0.0.0/24, doens't overlap with 10.210.0.0/16 I think. Also, from the lest side, the stup network, everything is readily accessible, such as the internet, servers, other clients, etc. This seems to be a rather narrow problem, it seems to indicate that maybe something is wrong the said NAS. Thanks anyways.

 

[Zen37]

Which brings me back to my original question; do you know the NAS subnet mask and default gateway? Are you able to ping or traceroute from the NAS device?

If you do a traceroute from your 10.210 network to you NAS, at what point do you get the * * *? That will point where you need to look. My guess is that your ROUT01 will be the last address you will see. The next hop after that is the NAS itself.

Good luck