Good Afternoon!It is likely that your remote locations contain the same configuration. I would take a previous configuration and apply it to the ASA you are getting ready to deploy. Given that you have the correct IP address and route outside setup. ...
Good Afternoon!
It is not a good idea to open up port 3389. It opens up to much risk to your environment. The best option you have, if you need remote access, is to utilize AnyConnect VPN. There are many options that come with the AnyConnect client ...
First question - create the user account with a priv of 5; you stated you don't have an aaa server... if you run the command: aaa authorization command LOCALThat will solve that problem - to see the privileges of that user log into that account and r...
Maybe you should attempt this:leave the IP address range of 172.16.101.0then run the command: IP dhcpd exclude-address 172.16.101.1See if this helps your issue it should leave the IP technically in the "server" group but simply not hand out that IP a...
Could it be your experiencing a NAT problem? I noticed your line:Nat (outside) 1 Is the same IP address range asNat (server) 1Since the device is no longer in the IP address range of the servers group it may be attempting to use the NAT (outside) rul...
