We would like to connect to our SourceOffSite Server using encryption via Port 80 so that we can reach it when we are on a client site where port 80 is the only available port. No websites on our our server are using port 80. The VaultService is running on this machine but we connect to the Vault server exclusively via SSL over port 443. So far our attempts to connect to SOS via port 80 have failed. Does anybody have any suggestions?
Thanks.
Using SourceOffSite on port 80
Moderator: SourceGear
Could IIS still be using port 80 even though you don't connect on that port?
There are a couple of ways to test whether something is blocking the connection between SOS Client and SOS Server:
Open a web browser on the client machine and type:
http://servername:port
Another test is to telnet to that port:
telnet <servername> <port>
If the connection is allowed to pass, then you should see "200 .....". If not,
then there is something on the network blocking the path between the
SOS Client and Server.
There are a couple of ways to test whether something is blocking the connection between SOS Client and SOS Server:
Open a web browser on the client machine and type:
http://servername:port
Another test is to telnet to that port:
telnet <servername> <port>
If the connection is allowed to pass, then you should see "200 .....". If not,
then there is something on the network blocking the path between the
SOS Client and Server.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Thanks Linda. We've set the default web site to TCP Port 1234 and SSL Port 443 and are using Vault over SSL and port 443. There are no other websites on the system.
When I invoke telnet [servername]:80 I get this response:
"Connecting to [severname]:80...Could not open a connection to host on port 23 : Connect failed."
It looks like IIS may still be listening on port 80.
When I invoke telnet [servername]:80 I get this response:
"Connecting to [severname]:80...Could not open a connection to host on port 23 : Connect failed."
It looks like IIS may still be listening on port 80.