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.
Ok, I'm not sure how to word my problem or what it would actually be called so it's likely that there is a question in the forums about this already...I have an Exchange server hosted on my internal network, which I have to access using the FQDN or i...
Ok, I can't for the life of my figure out why internal syslog traffic would be dropped at the firewall. I've come across a few support forums with comments like 'disable the specific syslog error, etc.' however this does not fix my problem. I need ...
Hi Jose, that thought never even crossed my mind! I assume this means that I have to setup my AD and DNS to be authoritative for mydomain.com, not mydomain.local like I have it now, correct?When I attempt to add a new A record following your suggest...
Jose, your fix to problem 1 allows all access from the outside, assuming you applied the extended list to the outside interface. Try to be more restrictive than an '...ip any any' rule for outside_in connections. For instance, this is what I have f...
If I understand you right, this sounds like a nat routing issue, you have the static nat lines, but they don't know where to forward to. Try something like:nat (inside,outside) source static interface service Good Luck!
