Unable to connect from New Work Site
Moderator: SourceGear
Unable to connect from New Work Site
I have moved to a new work site and am unable to connect to my Vault server with the Vault Client or the IDE support.
I'm am running the latest versions of all software (3.1.. My client is Windows XP SP2 with all updates and my server is Windows 2003 running Vault on IIS 6 and SQL Server 2000.
When I attempt to log into my server, I get a dialog box:
"Unable to connect to http://oceana-srv01/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: An unexpected error occurred on a receive."
So far I have used to support forums to try the following:
1) Pinged my server. I can reach it.
2) Logged in to the Vault Web support on the server. I can use the Web client in a normal fashion
3) Checked that Windows Firewall is off.
4) Turned on full logging and examined the log file. Not able to descern much from it. I've attached the log file that has two login attempts, both of which have failed.
Can you help me debug this further?
Thank you - Jeff Odell
I'm am running the latest versions of all software (3.1.. My client is Windows XP SP2 with all updates and my server is Windows 2003 running Vault on IIS 6 and SQL Server 2000.
When I attempt to log into my server, I get a dialog box:
"Unable to connect to http://oceana-srv01/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: An unexpected error occurred on a receive."
So far I have used to support forums to try the following:
1) Pinged my server. I can reach it.
2) Logged in to the Vault Web support on the server. I can use the Web client in a normal fashion
3) Checked that Windows Firewall is off.
4) Turned on full logging and examined the log file. Not able to descern much from it. I've attached the log file that has two login attempts, both of which have failed.
Can you help me debug this further?
Thank you - Jeff Odell
- Attachments
-
- VaultGUIClient.txt
- Log file from attempt to log in with Vault client and with logging set class set to "all".
- (4.4 KiB) Downloaded 633 times
Is this the actual error message? Are you on the same LAN as the Vault Server? If you are working remotely, "oceana-srv01" is not enough information in the login to find the server over the Internet. Try the IP address or fully qualified domain name "oceana-srv01.yourdomain.com," for instance.Unable to connect to http://oceana-srv01/VaultService
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I have the following entry in my local hosts file:
71.101.73.51 oceana-srv01
This works fine from all other locations. Also, as I posted,
http://oceana-srv01/VaultService/
connects fine. I don't think that is the problem.
jlo
71.101.73.51 oceana-srv01
This works fine from all other locations. Also, as I posted,
http://oceana-srv01/VaultService/
connects fine. I don't think that is the problem.
jlo
Can you connect to the Vault Server using just the IP address, using the Vault GUI Client?
Can you connect to http://71.101.73.51/vaultservice/vaultservice.asmx with a web browser?
Can you connect to http://71.101.73.51/vaultservice/vaultservice.asmx with a web browser?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Yes - I can use either:
http://71.101.73.51/vaultservice/vaultservice.asmx
or
http://oceana-srv01/vaultservice/vaultservice.asmx
The issue isn't DNS. I'm thinking there are some ports blocked on the way out or the way in. Is there a documented list of ports that must be open for Vault to operate?
http://71.101.73.51/vaultservice/vaultservice.asmx
or
http://oceana-srv01/vaultservice/vaultservice.asmx
The issue isn't DNS. I'm thinking there are some ports blocked on the way out or the way in. Is there a documented list of ports that must be open for Vault to operate?
Did you try using 71.101.73.51 for the Vault server name in the Vault GUI Client Connect to Server dialog?
If that fails, then something between you and the server is blocking the connection. Vault runs as a service in IIS and uses the port configured in IIS. The default is port 80. Since you can connect via a web browser, that port appears to be open to HTTP traffic. It's possible that a proxy or firewall is blocking SOAP messages and XML content used by the Vault GUI Client.
If that fails, then something between you and the server is blocking the connection. Vault runs as a service in IIS and uses the port configured in IIS. The default is port 80. Since you can connect via a web browser, that port appears to be open to HTTP traffic. It's possible that a proxy or firewall is blocking SOAP messages and XML content used by the Vault GUI Client.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
It appears to be something on the client side, as I was able to contact your Vault Server (but not login) with the Vault GUI Client. Check with your ISP or the Sys Admin at your new work site to see if they can help determine what is blocking Vault. Check your machine to see if firewall or anti-virus software could be blocking connections.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager