DirectAccess and Firewalls and NAT

re: DirectAccess and Firewalls and NAT

Bry — Mon, 16 Apr 2012 19:14:17 GMT

Other commenters, please read the closing statement, "that firewall cannot NAT connections between the DirectAccess clients and the UAG DirectAccess Server."

re: DirectAccess and Firewalls and NAT

Geekcroft — Sat, 08 Oct 2011 22:16:41 GMT

Tom.

If I have a customer that is doing some kinds of fancy NAT on their ASA - still giving me a public IP address but having a NAT entry for the IP in their rules - will this likely give me some strange niggly issues?

Thanks,

Stephen

re: DirectAccess and Firewalls and NAT

Geekcroft — Sat, 08 Oct 2011 22:12:15 GMT

hypothesis, As the UAG server will require a public IP address you may have to change your simple d-link ADSL router.

NAT, in lamens terms, allows devices behind your firewall to utilize public IP's whilst having a none-public IP address.

re: DirectAccess and Firewalls and NAT

hypothesis — Tue, 16 Aug 2011 14:10:24 GMT

Hi Tom,

Is it so necessary to exclude NAT at all? I'm using simple d-link ADSL router to connect to Internet. Isn't it sufficient to forward proto 41 and UDP 3544 port in and out to DirectAccess server behind firewall?

Really detailed info but why NAT is so bad and how overcome this!

Ilya

re: DirectAccess and Firewalls and NAT

Thomas W Shinder - MSFT — Thu, 06 May 2010 19:56:03 GMT

Hi Don,

Sure, TMG firewalls are like any other kind of firewall. Just make a ROUTE Network Rule

Source: Network that the UAG DA server's external interface is connect to

Destination: External (the default external Network)

Tom

re: DirectAccess and Firewalls and NAT

BigDon86 — Thu, 06 May 2010 19:10:44 GMT

Hi Tom;

I'll ask the obvious question....

Can a UAG DA device sit behind a TMG firewall? If yes, how?

Thanks for all the good info!

Don