I'm seeing some rather odd TMG behaviour:
I have a TMG 2010 Server 2008 R2 Server with 4 nics
Nic 1 - internal 172.16.10.10/29
Nic 2 - external 172.16.10.6/29
Nic3 - dmz 1 192.168.10.5/128
Nic4 - dmz 2 192.168.10.130/128
Binding order - Internal Nic, DMzs, then External at the bottom
On the internal network range I've defined subnet 10.10.0.0 to 10.10.255.255 as being an internal network
The route relationships I've configured are
internal to external- NAT
external to internal - NAT
Everything else is set to route
I'm trying to connect from localhost (TMG server) to internal on 443 on server 10.10.20.22, the connection sometimes works, however at other times it fails. I have an issue where the event log shows
src: localhost
destination:internal 443
status: Operation completed successfully
At other times it shows:
src:localhost
destination:external 443
status:access denied
For some reason the network that is registered on the internal address range shows as external.
I don't know why 10.10.20.20 would show as external and internal within the space of 4 minutes. When I do manage to connect, after a while the HTTPs connection will drop out with an access denied displayed in the log viewer.
One thing that is an issue is that the DC is down at the moment, TMG is a domain member. Would lack of connectivity cause this sort of quirky behaviour? The whole kit is offsite and I'm trying to resovle remotely...