Windows 2003 Server w/2 nic's trying to route between different subnets.
Configuration: NIC1>>>162.88.56.47 mask 255.255.248.0 GW 162.88.56.1 (Static)NIC2>>>192.168.15.224 Mask 255.255.255.0 GW NoneNIC2 uplinked to switch with IP cameras connected.Devices (Cameras) 192.168.15.xxx Mask 255.255.255.0 DGW 192.168.15.224Problem: Cannot see cameras. Application installed on server using a browser to access. I can see the cameras on the configuration page, not on the client page. (/admin) for configuration. Cannot ping any cameras from any other PC on the 162.88 LAN. Any suggestions? When I tried to route add -p, I received an error for the interface (1). When I did a route print, adaptors were 1x003 and 1x004. Is that the name of the adaptors??? (3, 4) I used adaptor (1) in the route add and got the error "the route addition failed: Either the interface index is wrong or the gateway does not lie on the same network as the interface. Check the IP address table for the machine." Any help is appreciated.
December 20th, 2009 1:30am

You need extra routing, but not on the clients or on the server. The problem is at the gateway router. All machines in the 162.88 subnet use the default router 162.88.56.1 . When they try to send data to 192.168.15.x it fails because this router has no idea where this subnet is. You need to add a static route to this router to forward traffic for 192.168.15.0 to your internal router at 162.88.56.47 . If you can't do that, you will need to add this static route to every machine in 162.88.15 which needs to see the machines in 192.168.15.0, so that the traffic goes to the internl router, not to the gateway router.Bill
Free Windows Admin Tool Kit Click here and download it now
December 20th, 2009 2:05am

Sorry so late getting back Bill. Thanks for taking the time to reply. So, if I understand you, I would add a route to each of the workstations that needs to access the cameras from the 162.88 subnet. Eg. route add 192.168.15.224 mask 255.255.255.255 [workstation IP address] correct? I have set up at our office another server running Server 2003 Standard Edition. I have the server IP set to the same as above (162.88.62.10). My office LAN subnet is 192.168.1.0. when I add the route to my server "route add 192.168.1.104 (workstation I am using as a test) mask 255.255.255.255 162.88.62.10. I can't ping the workstation from the router. Am I missing something???
January 7th, 2010 10:52pm

No, you have it backwards. You do not need any routes to get the traffic to the cameras. That will happen by default. You do need extra routing to get the replies back from the cameras. The routing must be added in the subnet where the cameras are, not where you are sending it from.Bill
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 4:23am

OK. Starting from scratch, this is how I have my little test set up:Router 1 (office router--DSL) 192.168.1.1 LAN Address of the router. DHCP to all workstations.Ethernet switch (SW-1) uplinked to 1 port of office router. (192.168.1.0 office LAN)SW-1 uplinked to Router 2 (Linksys WRT54GL) WAN IP 192.168.1.105 (Static in router)Router 2 LAN address 162.88.62.1 (DHCP Server ON) DNS servers programmed into this router (from DSL)SW-2 uplinked to LAN port of router 2.Router 3 upliked to SW 2 (162.88.62.0)Router 3 WAN 162.88.62.20Gateway 162.88.62.1Router 3 LAN 192.168.15.1SW-3 uplinked to LAN port of router 3.So, SW-1 Office LANSW-2 Client LAN SW-3 Camera LANServer NIC-1 162.88.62.10GW 162.88.62.1SN 255.255.255.0Server NIC-2 192.168.15.10GW 192.168.15.1SN255.255.255.0Client DHCP 162.88.62.0 (SW-2)Cameras 192.168.15.0 (SW-3)Camera Configuration:192.168.15.XXXSubnet 255.255.255.0GW 192.168.15.1Where do I need the route? If I have understood your last email, in router 3?Thanks a million Bill!
January 14th, 2010 1:02am

No, you need the extra routing in router 2 (the Linksys WRT54GL). Traffic from 192.168.15 will get to 162.88.62 by default. It is getting the traffic to go the other way which is the problem. Default routing by itself fails when you have multiple subnets and routers. Ignoring the ofiice LAN, the essential bit of the network looks like this. 192.168.1.105 dg 192.168.1.1 Linksys (NAT) 162.88.62.1 | client LAN 162.88.62.x dg 162.88.62.1 | 162.88.62.20 dg 162.88.62.1 router 3 192.168.15.1 dg blank | camera network 192.168.15.x dg 192.168.15.1 As it stands, the 192.168.15 subnet cannot see the 162.88.62 network and vice versa. It doesn't work because of the default route on the Linksys. The default route of the 162.88.62 machines is to the Linksys, and its default route is to the office network. Traffic which should come back to 192.168.62 never gets back to router 3 because the Linksys does not know where it is or how to forward traffic to it. You need to add a static route to the Linksys so that it knows where the 192.168.15 subnet is and how to reach it. That means adding a static route like 192.168.15.0 255.255.255.0 162.88.62.20 Now when the Linksys gets a packet for a 192.168.15.x address, it does not send it up to the office network (which is its default). It forwards it to the internal router at 162.88.62.20 , and that router then delivers the packet in the 192.168.15.x subnet. Bill
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2010 4:39am

Bill,I have completed the settings as you suggested. I still connot see the cameras from the 162.88.62.0 network. I programmed the route into the 162.88 router (router -2). There are 2 settings iin the static routing for the WRT54GL Linksysy router, Gateway and Router. In looking at the help file, the gateway is used if the router is providing internet routing, (this one is for the 162.88 network, I have our DNS servers programmed into it) or router if another router is providing the route to the internet. I have tries both configurations. I must be missing something. What you instructed me to do make perfect sence! Is ther any more information you can think of that I haven't provided?
January 15th, 2010 1:05am

Try adding the static route to a workstation in the 162.88.62 subnet . You should then be able to see a camera from that workstation. If that works, there is something funny about the static route on the router. Bill
Free Windows Admin Tool Kit Click here and download it now
January 15th, 2010 6:26am

Didn't work. I can ping from the 192.168.15.0 network to 162.88.62.0 network. Could the problem be in router 3? I have a Dlink 604 as #3. the firewall is enabled so maybe it's blocking the traffic. Just a thought. I have ordered another Linksys router. I will install it in place of the D-link. Do you think I need to add a route to router 3 to get back to the 162.88.62.0 network?Dwayne
January 15th, 2010 7:23pm

Before you change the router, just turn it off. Set one of the machines in 162.88.62 to use 162.88.62.20 as its default gateway. You now have the simplest possible routing setup. If it doesn't work, either the phones or the router are not set up correctly. To check which case it is, put a PC in 192.168.15.0 using the RRAS router as its gateway. If the two pcs cannot communicate, you router is not set up properly.If the two pcs can communicate, there is something wrong with the routing setup of the phones.Bill
Free Windows Admin Tool Kit Click here and download it now
January 17th, 2010 1:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics