Problems connecting and dropped connections

[acflavell]

Hi,

We have some remote developers trying to access our SOS server and they are getting a lot of connection failures. We are running Visual SourceSafe 6.0d and SOS 4.1.2 (client and server). Below is a snippet from the SOS log. Any ideas what might be going wrong? Thanks.

Andrew

4/14/2006 3:03:09 PM - 11: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:05:47 PM - Connection accepted from 220.117.208.129:2058 on local address 207.46.91.222:990, session id is 12.
4/14/2006 3:05:52 PM - 12: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:05:56 PM - Connection accepted from 220.117.208.129:2292 on local address 207.46.91.222:990, session id is 13.
4/14/2006 3:06:00 PM - 13: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:06:40 PM - 3: Exception: An existing connection was forcibly closed by the remote host
4/14/2006 3:07:09 PM - Connection accepted from 220.117.208.129:1054 on local address 207.46.91.222:990, session id is 14.
4/14/2006 3:07:14 PM - 14: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:08:04 PM - Connection accepted from 220.117.208.129:1055 on local address 207.46.91.222:990, session id is 15.
4/14/2006 3:08:09 PM - 15: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:09:35 PM - Connection accepted from 220.117.208.129:1057 on local address 207.46.91.222:990, session id is 16.
4/14/2006 3:09:40 PM - 16: Unable to get hostname from address: 220.117.208.129
4/14/2006 3:21:01 PM - 4: Exception: Index was outside the bounds of the array.
4/14/2006 3:28:02 PM - Connection accepted from 220.117.208.129:2098 on local address 207.46.91.222:990, session id is 17.
4/14/2006 3:28:07 PM - 17: Unable to get hostname from address: 220.117.208.129

[lbauer]

If you are using 6.0d with ssapi.dll version 98.48, be sure you have made the registry fix to avoid concurrency issues:

http://support.sourcegear.com/viewtopic.php?t=10

A symptom of a concurrency crash is when all users get disconnected, and the SOS Server needs to be restarted before users can connect again.

If only some clients are getting disconnected, it's generally because something on the network or on the client side is closing the connection. Check firewalls, routers, proxies, anti-virus software to see if there are interfering in some way with the connection. For instance, one user reported Norton Internet Security was closing connections on his machine.

http://support.sourcegear.com/viewtopic.php?t=37

Also check the SOS Server manager->General tab to see if you have Timeout Idle Connections enabled. This can cause connections to be closed as well.

Except for this setting, the SOS Server does not close connections.