Cisco 2600, need to route through Domain Controller

[mav617]

Hi,

I have a PTP circuit with a 2600 at either end. All works fine except I can't see one of the machines on the other end of the network. It's not a PC, it's a Digital Video Recorder. The DVR has an IP address and a gateway, the gateway being the router at that end of the circuit. I can access the Domain Controller PC at the far end, and from there I can ping the DVR, but I can't ping the DVR from this end of the PTP. Tracert shows that my ping is getting as far as the other router but then not knowing where to go. Can I create a static route to the DVR through the Domain Controller?

IP's on this end are 192.168.100.> and the subnet at the other end is 192.168.200.> Router config at the other end is:

RouterManchester>
C 192.168.200.0/24 is directly connected, FastEthernet0/0
10.0.0.0/24 is subnetted, 2 subnets
C 10.10.10.0 is directly connected, Serial0/0
S 10.146.40.0 [1/0] via 10.10.10.1
R 192.168.100.0/24 [120/1] via 10.10.10.1, 00:00:25, Serial0/0

Ignore the 10.146.40.0, that's for a seperate VPN we use occassionally. If every other machine with 192.168.200 address is visible, why is this one not (could it be due to DNS/DHCP settings on the Domain Controller?)

 

[lambent]

Check the routing table in the DVR (if possible) and see if there's a default route or 0.0.0.0 0.0.0.0 route there. Then make sure that the next hop of this default route is set to the IP address of f0/0 in RouterManchester.

You can also try to replace your DVR with a dummy PC with exactly the same IP configuration and see if you can ping this dummy PC.

 

[mav617]

Thanks Lambent,

There is nor outing table in the DVR, just an IP address (192.168.200.20) and the gateway, which is the IP address of the Manchester Router (192.168.200.25). It was working fine until the Domain Controller on the network at that end went down and has since been replaced. I've tried adding a route in the Remote Access and Routing on the DC, but no joy.

 

[PeterHurst]

The fact the traceroute gets to the Manchester router means your routes out are fine.

Can you ping the DVR from the router console? If so then that leaves an issue with default gateway/mask on the DVR or routes back.

As you can see the other PC's on the network I doubt it's the routes. Check the ip/mask and the gateway carefully on the DVR. We have DVR's which require a reboot to make any IP changes effective.. check the documentation in case the DVR requires something daft like leading 00's in the address or such like.

If possible default the DVR's IP's or at least change them and change them back.. remember if the Default gateway is correct but the subnet mask is wrong the DVR may not try and use the DG if it thinks you are on a local subnet.

eg 192.168.200.20 mask 255.0.0.0 would never user the DG as it thinks you are local.

 

[mav617]

Thanks Pete,

I'll need to drive up there and check the DVR then. I set it up as IP - 192.168.200.20 Mask -255.255.255.0 GW -192.168.200.25, and it used to work fine. I can ping it from the domain controller, but not from the router, which sounds like your point about thinking it's local?