Remote Desktop Connection Manager Error 50331661

I am trying to use RDC Manager to connect to a terminal server via a remote desktop gateway.  Everything was working just fine until I changed the terminal servers IP address.  Now I am getting an Error 50331661.  Anyone have any idea what this error is? I haven't been able to find anything online.  

Trying to make connection from a Windows 7 machine to a server 2008 R2 RDP GW then to a server 2003 TS.
LVL 2
Infamous_QAsked:
Who is Participating?
 
George HanelConnect With a Mentor Commented:
Just tried it.  If you set your gateway to gatewayfqdn:8 in rcdman where 8 is your external port number on the firewall that redirects to 443.

This worked for me.
0
 
AnthonyHamonCommented:
First of all, check whether you are able to make a RDP connection from the Remote Desktop Gateway server to the Windows Server 2003 server.  If not, there may be a firewall (or similar) blocking the access
0
 
Infamous_QAuthor Commented:
Sorry for the delay in my response.  I am able to use a regular RDP sessions to make the connection.  But when I try to open the connection in RDCMan then it gives the error.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
George HanelCommented:
Hi, just sorted a situation pretty similar to yours.

On windows 8, connecting to 2008R2 server, through 2008R2 gateway.  Works fine through RDP but was giving the same error using RCDMan.

I use proxy servers in schools and normally set it through internet options, lan settings.  Sometimes (noticed it since windows 8 so might not apply to 7) I have to set a proxy server on WinHTTP - to use windows store from inside a school.  I open powershell with admin rights, then following comands
netsh
winhttp
show proxy

If this isn't correct - ie shows "Direct access (no proxy server)" or the proxy server you may have to use - then this is probably your issue.  Basically it appears RDP uses settings from internet options, RCDMan uses settings from WinHTTP.

The following commands will replace the WinHTTP settings with what you have in Internet Options

netsh
winhttp
import proxy source=ie

If not proxy server have a look through WinHTTP related settings and look for incorrect settings.
0
 
Infamous_QAuthor Commented:
Thanks for the reply, however this didn't fix the issue. I did look around in WinHTTP but didn't see any settings that were different from My normal IE settings.  No proxy is set in either IE or WinHTTP. I really have no idea why it can't connect.  Its pretty much a straight shot until you hit the firewall.   However that raises a question just now.  Can RDCMan use RDP protocol 8?  I am using a different port than the normal port 443 for the connection.  I know that I had to update my windows RDP client to handle the port change.  Would this be the same for RDCMan?
0
 
George HanelCommented:
How have you changed your client to connect to port 8 on RDP?  Is it the gateway that listens on port 8 or is it the end computer that listens on port 8?  Are the gateway or end computer (the one that isn't on 8) listening on their standard ports ie 443 if the gateway, 3389 if the end computer?

In the original post you said you changed your terminal servers IP...was this the internal or external IP?
0
 
Infamous_QAuthor Commented:
the firewall listens on port XXX then forwards the traffic to port 443 on the gateway.  Everything else is set up pretty standard internally.  To be able to use port XXX from the outside we had to update the windows RDP client to use RDP protocol version 8.  Otherwise it would only use the standard port 443 for the gateway connection.  What I'm wondering is if RDCMan is able to use a gateway that is not on port 443.
0
 
Infamous_QAuthor Commented:
I will check my configurations and try again once I'm offsite.  Thanks!
0
 
Infamous_QAuthor Commented:
Sorry for the delay in my response.  I checked my settings and I guess that I had forgot to include the port number, but all is working well.  thank you all for your help.
0
All Courses

From novice to tech pro — start learning today.