Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
NAT- Keeping Access to the Local IP..
Alright good... But what about the lan-2-lan vpn connection that we have there... one of them has 192.168.1.0 network and the other has 192.168.30.0. They do need access to 192.1.1.8. -
NAT- Keeping Access to the Local IP..
Cool, a router side patch is perfered over a client side... pcs in the 192.1.1.0 network would still have access to 192.1.1.8 though? -
Attempting to build a game server with Cisco router
The game server has to be run through a cisco router... does this mean that you're going to be putting it on the internet? or are you going to create a mini little intranet in your classroom? -
NAT- Keeping Access to the Local IP..
So you mean if you enter both of the following commands: ip nat inside source static tcp 192.1.1.77 80 204.118.34.36 80 extendable ip nat inside source static 192.1.1.77 204.118.34.36 extendable Then the IP address 192.1.1.77 will be unreachable from the VPN client side?" Yep, the nat becomes... -
NAT- Keeping Access to the Local IP..
that access list is what allows and denys NAT entries... the 192.168.9.0 is already covered by the 192.168.0.0, but i went ahead and tried it anyway and im still not able to reach 192.1.1.8 -
NAT- Keeping Access to the Local IP..
Yep, that's correct... I've tried doing direct NATs before with other addresses and after I enter: ip nat inside source static 192.1.1.X 204.118.34.XX extendable the internal address becomes unreachable. -
NAT- Keeping Access to the Local IP..
Well in the acl 150 we opened it up to any so that users can use internet and vpn simultaneously. Some things they need to access are stored on a webserver not in our network. I suppose we could add that external source to the acl but they also want to have access to other internet stuff too... -
NAT- Keeping Access to the Local IP..
OK Heres the an exerpt of the cfg... We have 3 seperate VPN connections configured in here 2 LAN to LAN connections and the vpnclients. The LAN to LAN vpn connections can have access to the 192.1.1.8 ip but the vpnclients group doesnt. crypto isakmp policy 1 encr 3des authentication... -
NAT- Keeping Access to the Local IP..
1) Clients in the internal network use 192.1.1.8 without problems. 2) The VPN clients connect back into the internal network. 3) VPN tunneling is configured, but this problem existed before vpn tunneling was setup. The vpn clients just dont have access to the 192.1.1.8 ip address. It seems... -
NAT- Keeping Access to the Local IP..
We have a NAT setup for our M$ Exhange 2003 Server it looks like this: ip nat inside source static 192.1.1.8 204.xx.xx.33 extendable The router does not handle dhcp or dns for the 192.1.1.1 network. The problem is when vpn clients try to go to the exchange server by hostname it returns with... -
Cisco 3745, VPN and Split Tunneling
Thanks. However they both used the same settings. I played around with the settings and found that it worked when I opened my access-list source up to include the entire 192.0.0.0 network. I infered this is neccisary because the vpn ip addresses are in a seperate subnet from the the rest of our... -
Cisco 3745, VPN and Split Tunneling
oh sorry i didnt specify... I'm needing a router to client solution. We use vpn client 4.0(4) software. -
Cisco 3745, VPN and Split Tunneling
The company I work for wants to enable split tunneling for our Cisco 3745 router. Users want to be able to access internet and vpn resources similtaneously. I tried following the model here...
