Have my 1601 NAT-enabled (with static entries for web, mail and dns servers) but all connections to the webserver on the lan side are failing and all virtually hosted domains are not accesible. Any workaound (so that NAT could forward external connections to the webserver and have the virtual sites display)?
Need a little more information. Maybe a simple stick topology diagram and fake ip's would be helpful. Are your internal users trying to access the webserver using the public ip address? If so, they should have internal dns or lmhosts or some other mapping which maps it to the internal address. Not sure what you mean by "virtually hosted domains"
Schematically the setup is as this: LAN (with Private IPs) > NATed Router (1601 with static entries of the type "ip nat inside source static Server Private IP Server Public IP extendable") > Public Network (Internet).
Internally all the hosted domains are accessible. From outside, only the main domain is accessible, all the other domains virtually hosted on the webserver for other people using a single IP (NameVirtual Hosts on Apache 1.3 and Host Headers on IIS 5.0) are not accessible. The connection constantly fails with the following error message: " Network error: Could not connect to the server. Server either too busy or unavailable".
Hope this clarifies my scenario and thanks in anticipation for your help.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...