Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi, I'm trying to set up my ASA5510 so that it will pass webmail traffic. I've permitted http 80 and IMAP4 143 to my exchange server on the ouside interface of the ASA but no joy. Can anyone suggest where I'm going wrong?RegardsEgg
Hi all,At present I'm installing a ASA firewall between my 2811 router and the network.The router at the moment has an internal ip address of 192.9.200.253 and has NAT rules set up. The 192.9.200.254 address is that of our exchange server. My questio...
Hi all,At present I'm installing a ASA firewall between my 2811 router and the network.The router at the moment has an internal ip address of 192.9.200.253 and has NAT rules set up. The 192.9.200.254 address is that of our exchange server. My questio...
Hi all, I’ve inherited a 2811 router with a firewall feature pack from a previous support guy and it looks in a bit of a mess. I'm having problems RDPing out through our 2811 with firewall feature set. I have a route map pointing to an access list pe...
I have a 2811 router with an IOS Firewall and I'm trying to enable smtp through. I've added smtp to the access lists but no joy. I even disabled the access lists and applied one with permit tcp any any and still no joy. I'm suspecting the ip inspect ...
Hiya,Yeah OWA. I've permitted http, https and IMAP4 from anywhere to my Exchange server. My ASA is connected to my internal network and to a router on the ouside interface on a 10.10.10.0 subnet. I've been wondering how to configure NAT. This is a ne...
Hi halijenn,Yeah, I already thought of that but remarks don't show up as line# in the sho ip access-list adsl24external command. Only the permit and deny statements. How would I remove the remarks?RegardsEgg
Thanks Halijenn,Scoolboy error, the subnet msk should've been reversed, yeah?What do you make of the remarks repeating themselves in the access lists?RegardsEgg
Oh hang on! I've sussed it. it was nothing to do with that. there was an old nat statement pointing at an old exchange server.Thanks for your interest.RegardsEgg
