Cannot connect using encryption

sergiogiogio · Post by **sergiogiogio** » Thu Jun 02, 2005 5:32 am

Hello,

I have a problem connecting the company's SourOffSite server using encryption... Not using encryption works fine but the SOS client is just unable to connect using encryption.

The server does work though since everyone else in the world is using it with encryption.

Here is my investigation so far:

1. Using internet explorer, when opening www.xxxxxx.xxx:XX, I get:

"250 Protocol-Version:2.0 Message-ID:00000000 ...."

2. On the GUI 3.5.3, I when trying to connect to www.xxxxxx.xxx:XX, I get "server closed connection".

3. Using soscmd, when issuing:

soscmd -command GetFileList -server www.xxxxxxx.xxx:XX -name xxxxx -password xxxx -database "XXXXX" -project "XXXX" -verbose

I keep getting this:

SourceOffSite Command Line Client: 128 bit Encryption version 3.5
Connected to server www.xxxxx.xxx at port XX.
Net error during attempt to read headers. (RH1). Error: 0
Closed connection to server www.xxxxxx.xxx at port XX.

4. The server side logs log.txt show absolutely nothing.

On a completely different level, I cannot re-install the GUI on my computer XP SP2, the installation program 'sos_client_professional.exe' just hangs and I have to kill it using the Task Manager

I would be grateful if you had any help here.

SerGioGioGio

bfinney · Post by **bfinney** » Fri Jun 03, 2005 2:43 pm

Looks like the connection is being killed on your side. The first thing to look at is your firewall - make sure it's open on the port used by SOS for secure connections (probably 8890) to bidirectional TCP. If there's no connection attempts being logged by the server, the packets are getting eaten before they get there.

sergiogiogio · Post by **sergiogiogio** » Mon Jun 06, 2005 8:38 am

Thanks for your reply, bfinney.

After some more investigation here is what I found:
- client does connect to the server on the encrypted port,
- nothing happens for 1 minute (both client and server send nothing),
- server closes connection (probably a timeout issue).

Do you know what is supposed to be happening after the TCP connection?
When I connect to the non-encrypted port, I can see that the server sends some data after the TCP connection. Is the same scenario supposed to be happening with the encrypted port? If so there might be a problem with the server...
Also please confirm this: only one port is needed in either cases (encrypted and non-encrypted).

Thanks in advance,

SerGioGioGio

bfinney · Post by **bfinney** » Mon Jun 06, 2005 9:55 am

Are the connection attempts being logged by the server (i.e. is a new session ID showing in the log)?

The intial connection process is more or less the same, so there should be burst of traffic upon establishment of the connection.

And, yes, only one port is needed.

sergiogiogio · Post by **sergiogiogio** » Mon Jun 06, 2005 10:24 pm

Problem is solved!

- I telnetted the server on the encrypted port. After TCP connection, I received nothing from the server, just as the SOS client was experiencing.
After typing one line of some dummy letters though, I eventually got

Code: Select all

HTTP/1.0 200 OK
Cache-Control: no-store
Pragma: no-cache
Cache-Control: no-cache
X-Bypass-Cache: Application and Content Networking System Software 5.1.15
Connection: Close

<HTML><HEAD><META HTTP-EQUIV="REFRESH" CONTENT="0" URL=""></HEAD><BODY>
</BODY></HTML>

- Then a few seconds later, a second telnet on the encrypted port showed:

Code: Select all

250
Protocol-Version:2.0
Message-ID:00000000
....

which is what's expected.

From that point on I was able to connect using the SOS client

I am really still not sure what the problem really was in the first place.
I believe there was some mysterious issue with the SOS server. Does the server need some kind of prior registration in order to allow the clients to connect? Maybe the few letters I typed during my first telnet session did reset something...?

Anyway it is working now, many thanks for your help!

SerGioGioGio

lbauer · Post by **lbauer** » Tue Jun 07, 2005 1:39 pm

Gremlins.