While deploying an URA gateway in a DMZ hosted by Forefront TMG I got a weird behaviour when I try to access through remote desktop to my server. Indeed another access like HTTPS for the NLS hosted on the URA server working well.
1/ Architecture
2/ Settings deployed on Forefront TMG
2.1/ DMZ setup
As we could see on the Forefront TMG networks, the Private DMZ is on route relation between the internal network and the DMZ network.2.2/ Access rules
Then on the firewall access rules the RDP protocol is allowed between the internal network and the Private DMZ, and my laptop got as a default gateway for the DMZ the Forefront TMG IP.3/ Problem
When I try to reach the server through Remote Desktop on the log live of Forefront TMG I got these two lines:
Transport
|
Port
|
Protocol
|
Result Code
|
Source
Network
|
Destination
Network
|
TCP
|
3389
|
RDP
|
0x80072743 WSAENETUNREACH
|
Internal
|
DMZ Private
|
TCP
|
3389
|
RDP
|
0x8007274c WSAETIMEDOUT
|
Internal
|
DMZ Private
|
Here's the detail of the first one.
And for the second one.
4/ What's happening on the URA gateway
When I look closer on the firewall state I see that only the Public profile is in active mode without any reason.
And we I look on the network card settings the Private DMZ NIC got the domain information.
5/ How to solve this
I restarted the Network Location Awareness service in order to force the server to re-evaluate the profile of the NICs.And after this both Domain and Public profile become actives on the firewall and the Remote Desktop works without any updates on Forefront TMG :).
Aucun commentaire:
Enregistrer un commentaire