"Server closed connection" for the one client

Alek · Post by **Alek** » Tue Dec 13, 2005 3:56 am

There is simular problem found
http://support.sourcegear.com/viewtopic.php?t=1808

Sorry for my English.
We are running Source Off Site 3.5.3 on a Windows 2000 server.
Some clients working with no problems, but one can not connect.
"Server closed connection" error appears.

Server log:
Tue Dec 13 11:41:20 GMT+03:00 2005 - <client ip> - Connection Established
Tue Dec 13 11:41:20 GMT+03:00 2005 - <client ip> - Error processing client message
Tue Dec 13 11:41:21 GMT+03:00 2005 - <client ip> - User "null" disconnected

On the client side through IE i can see response from server:
250 Protocol-Version:2.0 Message-ID:00000000 Database Aliases:vss Content-Length:43 Key Length:16 ...

telnet <server ip> <port>
blank

> For the users who have problems, do they share a common type of network?
Connections through internet .

> Do they receive a login dialog or does the failure occur before that point?
Client does not receive login dialog

> Does it seem to make a difference if they use the secure or unsecure port?
It is seems that no difference between secure and unsecure port

>Are they passing through a firewall or proxy that the other users (who don't have problems) aren't?
"Problem client" passing through Symantec Client firewall.
At first time, he received message "Cannot connect to server". We added sos.exe to "Program list" with "Permit all" access.
And now he received "Server closed connection" error and we can see messages in server log.
We also added server IP to trusted list. There is no effect.

How can i try to resolve this problem ?
P.S. Sorry for my English.

lbauer · Post by **lbauer** » Tue Dec 13, 2005 4:55 pm

telnet <server ip> <port>
blank

Unless telnet is disabled on the SOS Server machine, the telnet test should return the same results as the browser test.

If the telnet test isn't working, then possibly SOS won't either. The browser test works for http traffic. SOS uses tcp\ip. Did you open the firewall for tcp\ip traffic, in both directions?

Alek · Post by **Alek** » Tue Dec 13, 2005 8:38 pm

lbauer wrote:
telnet <server ip> <port>
blank
Unless telnet is disabled on the SOS Server machine, the telnet test should return the same results as the browser test.

If the telnet test isn't working, then possibly SOS won't either. The browser test works for http traffic. SOS uses tcp\ip. Did you open the firewall for tcp\ip traffic, in both directions?

Yes, tcp\ip traffic was opened, but telnet does not working.
You message really help me!
I am added server ip to "trusted zone" ( "...need to share files and printers...") and telnet and SOS start work!
General rule for this ip to enable "to and from" tcp and upd connections - is not enoght.
Thank you!

lbauer · Post by **lbauer** » Wed Dec 14, 2005 7:16 am

added server ip to "trusted zone" ( "...need to share files and printers...") and telnet and SOS start work

Glad you figured it out -- since there are so many types of firewalls out there, we can only give general configuration advice. I'm sure your post will help other users with Symantec Client Firewall.