none
RD gateway id temperorly available RRS feed

Réponses

  • Thanks for all supports.

    but i solved that error  like this way...

    from client PC-
    C:\Windows\System32\drivers\etc\hosts
    i manually added our RDS server " public IP and Server FQDN "
    and saved that on notepad as administrator rights
    and on CMD type : ipconfig /flushdns.
    exit

    and i retried ......
    reconnected my RDS. result was successful.

    Feel Free.... replay me!!




    jeudi 5 janvier 2017 08:21

Toutes les réponses

  • Hi,

    When you click the icon on the RD Web Access page, a prompt will be shown with Gateway server: <FQDN>.  Please verify that the FQDN shown resolves to the correct ip address for the RD Gateway server and that TCP port 443 and UDP port 3391 are forwarded to it on the firewall.

    Thanks.

    -TP

    mardi 3 janvier 2017 18:24
    Modérateur
  • Hi Amrh ali,

    When the issue occurs, you may ping the RD gateway, check if it is available;

    Also check the event log in Event Viewer>Applications and Services Logs>Microsoft>Windows>TerminalServices-Gateway>Operational, check if there are related logs at that time, if there's no log, it probably no connection attach the RDG. If there are logs, check the log's information.

    Since it's a temporary issue, you may also use network monitor to capture traffic both on the client and RDG for further troubleshooting:

    https://www.microsoft.com/en-us/download/details.aspx?id=4865

    If the issue is due to RDG heavy load, then you may set up RDG high available, if the issue is due to network congestion, then you may optimize the network structure; if the issue is due to client adapter issue, then you may troubleshoot on client side.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    mercredi 4 janvier 2017 07:46
    Modérateur
  • Thanks for all supports.

    but i solved that error  like this way...

    from client PC-
    C:\Windows\System32\drivers\etc\hosts
    i manually added our RDS server " public IP and Server FQDN "
    and saved that on notepad as administrator rights
    and on CMD type : ipconfig /flushdns.
    exit

    and i retried ......
    reconnected my RDS. result was successful.

    Feel Free.... replay me!!




    jeudi 5 janvier 2017 08:21
  • Hi Amrh ali,

    Glad to hear you have solved the issue and thanks for the feedback.

    Then the issue is indeed due to DNS resolution as TP indicated.

    You may mark useful replies as answer, so that this case can be closed.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    jeudi 5 janvier 2017 09:26
    Modérateur