Using Secret Server as a credential repository

I am trying to connect to Secret Server as a credential repository in RDM but I seem to have some connection issues. This is a test of Secret Server and how it can integrate with RDM so I may be missing something. Is there some documentation or do you have some advice on how to make this integration work? This is the error I am getting.

WebException - Unable to connect to the remote server

at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Devolutions.RemoteDesktopManager.SSWebService.SSWebService.Authenticate(String username, String password, String organization, String domain)
at Devolutions.RemoteDesktopManager.Business.SecretServerReader.GetToken(String organization, String username, String domain, String password)
at Devolutions.RemoteDesktopManager.Business.SecretServerReader..ctor(CredentialsConnection credentialConnection)
at Devolutions.RemoteDesktopManager.Forms.FrmSelectSecretServerEntry..ctor(CredentialsConnection credential)
at Devolutions.RemoteDesktopManager.Frames.CredentialSettings.FreCredentialResolverSecretServerSettings.butBrowse_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

------------------------------------------

SocketException - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.27.1.156:80

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)


I am running enterprise version 7.4.6.0.

As always keep up the good work on this tremendous product. Our company would be lost without it.

Thanks,
Larry