Client hangs on connection to server

[mikemil]

Hi,

We are using SOS Version 4.2 (server and clients). Everything was working fine on Friday. On Monday, none of the SOS users could get their SOS clients to connect. My guess is that someone changed something in our network over the weekend and I am trying confirm that. We also noticed that connecting with the client works when running on the same machine or a machine in the same 'network area'. We have a large group in Rockville, some folks in Dallas and some in Hyderabad. The VSS and SOS machine resides in Rockville, while the client users are in Dallas and Hyderabad. Machines in Rockville can get the client to start but not from Dallas or Hyderabad.

Below is a copy of our log.txt after changing the logging levels to capture more information. My machine is J1002399xpdt and I can see that the server is waiting on the client's response to the challenge. After a couple minutes, I exited the client.
Is there anything else I can check to help resolve this issue? We have about 30 developers waiting to get access to the repository...


11/18/2008 9:07:02 AM - ****************************************************
11/18/2008 9:07:02 AM - SourceOffSite Server 4.2 Professional - With Cryptography

11/18/2008 9:07:02 AM - CurrentCulture is en-US.

11/18/2008 9:07:03 AM - Server Information
11/18/2008 9:07:03 AM - Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
11/18/2008 9:07:03 AM - Service Pack: 1.0
11/18/2008 9:07:03 AM - OS Version: 5.2.3790
11/18/2008 9:07:03 AM - Locale: Ox0409
11/18/2008 9:07:03 AM - OSLanguage: 1033
11/18/2008 9:07:03 AM - Total Physical Memory: 16 GB
11/18/2008 9:07:03 AM - Time Zone: (GMT-07:00) Arizona
11/18/2008 9:07:03 AM -
11/18/2008 9:07:03 AM - SSAPI.dll Information:
11/18/2008 9:07:03 AM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
11/18/2008 9:07:03 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
11/18/2008 9:07:03 AM -
11/18/2008 9:07:03 AM - Started at 11/18/2008 9:07:03 AM

11/18/2008 9:07:03 AM - General logging level is Verbose. Method logging is Enabled.

11/18/2008 9:07:03 AM - Number of licenses configured: 36
11/18/2008 9:07:03 AM - SourceSafe Initialization file(s) located at:
11/18/2008 9:07:03 AM - E:\Source\JDAPortfolio\srcsafe.ini
11/18/2008 9:07:03 AM - E:\Source\Portfolio7.4\srcsafe.ini

11/18/2008 9:07:03 AM - PENTAGON is attempting to listen for connections on secure port 8081
11/18/2008 9:07:03 AM - PENTAGON is attempting to listen for connections on unsecure port 8080


11/18/2008 9:07:03 AM - Waiting for a connection....secure = False
11/18/2008 9:07:03 AM - Waiting for a connection....secure = True
11/18/2008 9:07:10 AM - Connection accepted from 172.17.26.64:3733 on local address 10.0.13.49:8080, session id is 1.
11/18/2008 9:07:10 AM - 1: Enter Authorized()
11/18/2008 9:07:10 AM - 1: Connection from: J1002399XPDT (172.17.26.64)
11/18/2008 9:07:10 AM - 1: Preparing to send the list of databases...
11/18/2008 9:07:10 AM - 1: Sending the challenge to the client.
11/18/2008 9:07:10 AM - 1: Sending the challenge message body to the client.
11/18/2008 9:07:10 AM - 1: Waiting for the client's response...
11/18/2008 9:09:43 AM - 1: Exception processing messages: An existing connection was forcibly closed by the remote host
11/18/2008 9:09:43 AM - 1: Enter KillConnection()
11/18/2008 9:09:43 AM - 1: User disconnected from J1002399XPDT.
11/18/2008 9:09:43 AM - 1 - Exit KillConnection()

[mikemil]

We were not able to figure out why the clients weren't responding with the challenge response but we were able to get back operational but changing the un-secure server port from 8080 to 8090.

[Beth]

Thanks for the update. It could be that someone assigned another program or service to use port 8080. SOS can't be on a port that something else is using.