I have a server behind the firewall which, up until a couple of weeks ago, I was able to RDP into (it's a Windows server). Now suddenly I can't, though everything seems to be fine on the server side of things. I know the commands used are old here, but it was set up a while ago by someone else. Could someone confirm that this looks right to pass RDP (TCP port 3389) traffic through?
I'm far more familiar with access lists, myself, so I don't really know how these conduits work. But you're basically saying I could toss the conduit for RDP and just use an access list (which I've used for this before)? I just don't want to break anything. But if that's what you mean, then couldn't most of those conduits be done through access lists?
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...