Prev: The server failed to retrieve the SID of Session BRoker
Next: TS 2008 settings for this terminal server cannot be retrieved
From: Larry Smith on 20 Nov 2008 11:18 My first time setting up a Windows Server 2008 Terminal Services Gateway. When trying to establish a connection thru the gateway the following dialog box is displayed: "This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance." I have tried both Vista and XP clients with the same result. All machines are up to date with patches. I am using a trial certificate form COMODO which appears to be installed correctly. Nothing I have tried has solved this issues. What am I overlooking? Thanks, Larry
From: Ayesha Mascarenhas [MSFT] on 1 Dec 2008 14:46
Hello, please take a look at this discussion to see whether the proposed steps help you resolve your problem: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/85368088-53d9-4353-8a24-75d69c41cca5/ One possible issue: The problem was related to the fact I had not defined any default gateway on my clients. If the client doesn't have this information, it seems that it's not able to send anything to the TS gateway even if this one is on the same subnet and DSN resolution works fine. "Larry Smith @ SRHD" <Larry Smith @ SRHD(a)discussions.microsoft.com> wrote in message news:97D68A87-29BD-4D4C-8C80-59E40A38A53F(a)microsoft.com... > My first time setting up a Windows Server 2008 Terminal Services Gateway. > When trying to establish a connection thru the gateway the following > dialog > box is displayed: > "This computer can't connect to the remote computer because the Terminal > Services Gateway server is temporarily unavailable. Try reconnecting later > or > contact your network administrator for assistance." > I have tried both Vista and XP clients with the same result. All machines > are up to date with patches. > I am using a trial certificate form COMODO which appears to be installed > correctly. > Nothing I have tried has solved this issues. What am I overlooking? > Thanks, > Larry |