Search results for query: *

Well when I first inherited this network it supposedly has a tunnel in between both sites. Unfortunately, I dont believe that tunnel exists because i should be able to see both networks even if im at the office. Im trying to think of what else I can get you. I only have one router on the network...

yea no problem. My ASA is setup with an ip address of 172.16.200.1. I cant get to the 172.16.200.128 network through my VPN. I have a file server on the 172.16.200.128 network that I need to get too, but cant get to it when I VPN in. I can get to everything on the 172.16.200.0 network and thats it.

What you're saying is correct. One network is 172.16.200.128 and the other is 172.16.200.0. When I VPN into my network I VPN into 172.16.200.0 which is where the ASA is located. I can get to my servers in Eastern Oregon on that network, but cant get to my File server in Portland, which has an IP...

Yea. Except, the subnet is split. One side would be 172.16.200.1 - 172.16.200.50. (hypothetical) And on the other network it would be 172.16.200.128 - 172.16.200.250. We have two DNS and two DHCP servers at both ends. When im on one network say on the west side I get 172.16.200.150 as DHCP and...

I will be changing the IP structure at one of the sites pretty soon. Basically, im changing it from 172.16.200.x to 172.16.220.x. Would that make it any better?

So how would I get it to route packets to the other network? It comes into the ASA via VPN, but wont go anywhere else on the network except for where it comes in. Would the routing issue be on the ASA or the router itself?

Im sure someone might know what the problem could be...Here is my situation... Ive got two networks going on right now. They are both on the same subnet, but split into two different networks. I have a VPN tunnel setup on the ASA firewall at my remote location. When I VPN in I VPN into that...