Sometimes administrators may find themselves in a situation when they don't seem to be able to access UAG server (via RDP and/or Ping). In most cases the issue is due to either – 1) routing; 2) security restrictions:
- UAG [typically] has two interfaces – internal and external, but only one, external, should be configured with the default gateway. This means that for internal interface to be reachable from subnets other than the one it’s on one would need to add persistent static routes using “route add –p [destination network] mask [mask] [gateway]” command. Verify the results using “route print” command.
- UAG is a harden network device protected by TMG and as such only allows administrative access from authorized hosts. To see or modify the list of allowed hosts go to TMG Management Console, navigate to Firewall Policy, select Toolbox \ Computer Sets \ Remote Management Computers, double-click to view or edit (modify to suit your needs):