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..

Status
Not open for further replies.

Marcusm88

Technical User
Joined
Apr 15, 2005
Messages
13
Location
US
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 192.1.1.8 and it cannot reach this address. I thought of a workaround, by adding the global ip 204.xx.xx.33 and the hostname to the hosts file in windows, but i know this is just a patch for the problem.

Any suggestions?
 
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.

 
Take a look at the below extracted commands

ip access-list extended exchangeip
deny ip host 192.1.1.8 192.168.0.0 0.0.255.255
permit ip host 192.1.1.8 any

the "deny" line, together with the NAT settings, means that 192.1.1.8 will be NATed except for the destination network 192.168.0.0/16, which includes all of your internal networks I believe.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top