Failure calling web services on XXX.XXX.XXX.XX

[Anonymous]

I have a Vault Server on the DMZ that I would like to be able to connect using the Vault client from outside our firewall.  I have opened up port 80 to the outside world.  The Vault Server is connectting to our license server inside the firewall. 

Everything works fine connecting to the internal address inside the firewall.  The problem is when you connect to the outside address.  I get an error "Failure calling web services on "xx.xx.xx.xx".

I can ping the Vault server from outside.  I can see the splash screen when I go through a web browser.  The Vault client can see the server and its available Vaults.

Below is the log from the server when I attempt to connect from outside.

1/15/2015 8:53:15 AM *******************************************************************
Error: Soap Exception ( mesg-id = 635569087956081041 )
Exception: WebServiceError [8005] (http://XXX.XXX.XXX.XX/)
Stacktrace:    at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)
   at Connectivity.Filestore.AuthenticationService.CreateSession(AuthCredentials creds, String dataServer, String knowledgeVault, Boolean isLicensed, Byte[] p)
   at Connectivity.Web.Filestore.v19.AuthService.SignIn(String dataServer, String userName, String userPassword, String knowledgeVault)
   at SyncInvokeSignIn(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Exception(Inner): There was no endpoint listening at http://XXX.XXX.XXX.XX/AutodeskDM/Services/_impl/SiteService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Stacktrace(Inner):
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Server.Proxies.SiteService.SiteService.SignInSite2(SignInSite2Request request)
   at Connectivity.Server.Proxies.SiteAuthenticator.SignIntoSite(String remoteServer, String vaultname)
   at Connectivity.Server.Proxies.ServerTokenCache.Get(Lazy`1 authenticator, String remoteServer, IResourceStore vault, SecurityHeader expiredToken)
   at Connectivity.Server.Proxies.ServiceAccessor`3._service(String remoteServer, Boolean reSignin)
   at Connectivity.Server.Proxies.ServiceAccessor`3.tryexecute(String remoteServer, Action`1 action, Int32 attemptCount)
   at Connectivity.Server.Proxies.ServiceAccessor`3.Execute(String remoteServer, Action`1 action)

Exception(Inner): Unable to connect to the remote server
Stacktrace(Inner):    at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

Exception(Inner): 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 XXX.XXX.XXX.XX:80
Stacktrace(Inner):    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

[Anonymous]

Bump.... I am having the exact same error in the same context! Any autodesk employees out there,Please Help! If I cant get my subs into the vault, a major project is going south in a hurry!

[Anonymous]

Hi Jason

Did you ever manage to sort the issue out as iam having the same problem.

If so can you please tell me what you did to resolve the problem.

Thanks

Adam

[scottmoyse]

Bump again. Come on Autodesk, can someone help with this please? The Thin Client access works fine, but trying to log in via the Thick Client throws this error.

[scottmoyse · Accepted solution]

When this happens it's because the FQDN URL isn't being resolved to the internal IP address of the server. Your IT guy should be able to fix it up properly. But a workaround is to edit the Windows Hosts file which can be found here:

C:\Windows\System32\drivers\etc\

Then on a new line at the end of the file, press TAB, type the internal IP address of the server (by default its 127.0.0.1), then TAB again, followed by the FQDN URL.

[luis_andueza]

Hi everyone,

I am having the same problem, I did what @scottmoyse said, adding a line at the end with the internal IP (also tried 127.0.0.1 and the public IP of the server) but nothing.

Any other advise????

Regards,