I've tried setting up the ASA 5505 multiple times. I am able to access the server from a client but cannot access the internet. As of right now, I have no need to set up a dmz, only inside and outside interfaces. I've also tried different cables but was under the impression that the ASA had auto-sensing capabilities. What I have noticed is that the ASDM "forces" you to set up a dmz. Any ideas on getting re-started? I'm not sure if this a problem but the ASA will be the only device configured between the internal network and the "outside".
I can't believe how easy that was. Many thanks. One question I have is why would I use "nat(Inside) 5 0 0" and "global(Outside) 5 interface" as opposed to "nat(Inside) 1 0 0" and "global(Outside) 1 interface? "
You can use any number you like, it's a map from a NAT source to an IP(s). You can use more than one too. I typically use one for NATing all internal users to the outside interface IP. I then use another (2 for example) for a specific mapping, like an email server.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...