We currently re-did our network. We were using 192.168.x.x network for our entire site. We decided to segment the networks into 192.168.x.x and 172.16.x.x. We currenlty are using HP Pro Curve switches both 2424m and 4000m. The 2424m sit at department telco cabinets and the 4000m are sitting in the server room. Let me start over...... our current configuration has a cisco router from timewarner as our internet gateway, from there we have an unmanaged switch a small 24 port switch that connects the time warner router and two watch guard routers; one is configured with 192.168.x.x and the other is configured 172.16.x.x, the 192.x.x.x router connects to a 80 port HP Pro Curve switch and that switch is connected using a cross over cable to another 80 port HP Pro Curve switch for our collections dept. The 172.x.x.x router connects to a small 24 port switch for our legal dept. We have configured the two wan interfaces with public address from time warner so that the three routers are on the same network and one interface on each routher with the private network addresses. We have shares on the 172.x.x.x network that need to be accessed by clients on the 192.x.x.x network unfortunately after setting static routes: 172.x.x.x via public and 192.x.x.x via public (public is the other network address which I will not give for obvious reasons) The clients cannot access the shares, instead we trace routed the packets and noticed that when attempting to reach the other network, they would go private interface > wan interface > and then out to the internet; they never even tried to follow the static route. We can ping the address from one network interface address to another such as from 192.168.7.1 to public but cannot get past that interface, we can't reach the private network interface ( 192.168.x.x). Can anyone recommend a possible solution to our issue?