"Server closed Connection" Error

pratyush.shukla · Post by **pratyush.shukla** » Thu Apr 19, 2007 10:41 am

I have installed SOS Client 4.2 on my laptop and connected to the SOS Server successfully from my home.

I took the same laptop to my office and trying to connect from there. The system asks for my User ID and password and after a while shows an erorr message "Server Closed Connection".

I tried to connect to SOS Demo database with daffy/duck it worked fine.

So I do not know what is wrong when I am connecting to my server from my office.

Please help.

Beth · Post by **Beth** » Thu Apr 19, 2007 1:15 pm

Are you using an IP address from home or a server path?

Are you using the secure port or the unsecure port?

Is there a proxy on your network?

Check your SOS log for errors associated with your attempted logins. The SourceOffSite log file (log.txt) is located on the machine where the SOS server resides. What are the errors?

pratyush.shukla · Post by **pratyush.shukla** » Thu Apr 19, 2007 3:08 pm

1)

I am using an IP address and port 8080 to connect to SOS from home and work both.

2)
[PS]

Is there a proxy on your network?
On which network? The SOS Server network or from the office network? The network where SOS Server is placed and the network from where I am trying to connect are totally different.

3) Check your SOS log for errors associated with your attempted logins. The SourceOffSite log file (log.txt) is located on the machine where the SOS server resides. What are the errors?
[PS]
I do not have access to SOS server. But will try to get that.

Beth · Post by **Beth** » Thu Apr 19, 2007 3:59 pm

I think we are going to need to see the log. It's looking like there might be some piece of networking equipment that is closing the connection, but the log will help verify that.

pratyush.shukla · Post by **pratyush.shukla** » Fri Apr 20, 2007 9:11 am

Contents of the log file

4/19/2007 12:57:59 AM - Connection accepted from 72.1.102.22:54814 on local address 10.0.10.55:8080, session id is 52.
4/19/2007 2:56:47 AM - Connection accepted from 72.1.102.22:3371 on local address 10.0.10.55:8080, session id is 53.
4/19/2007 3:47:41 AM - Connection accepted from 64.172.142.154:28906 on local address 10.0.10.55:8080, session id is 54.
4/19/2007 4:02:23 AM - Connection accepted from 125.245.88.254:4407 on local address 0.0.0.0:8080, session id is 55.
4/19/2007 4:02:28 AM - 55: Unable to get hostname from address: 125.245.88.254
Send failed: An existing connection was forcibly closed by the remote host
4/19/2007 4:02:28 AM - 55: Exception processing messages: An existing connection was forcibly closed by the remote host
4/19/2007 4:02:43 AM - Connection accepted from 125.245.88.254:4407 on local address 0.0.0.0:8080, session id is 56.
4/19/2007 4:02:47 AM - 56: Unable to get hostname from address: 125.245.88.254
Send failed: An existing connection was forcibly closed by the remote host
4/19/2007 4:02:47 AM - 56: Exception processing messages: An existing connection was forcibly closed by the remote host
4/19/2007 10:40:52 AM - Connection accepted from 10.0.10.154:2709 on local address 10.0.10.55:8080, session id is 57.
4/19/2007 10:41:59 AM - Connection accepted from 10.0.10.154:2710 on local address 10.0.10.55:8080, session id is 58.
4/19/2007 10:42:14 AM - Connection accepted from 10.0.10.154:2711 on local address 10.0.10.55:8080, session id is 59.
4/19/2007 11:14:38 AM - Connection accepted from 220.149.80.27:6000 on local address 0.0.0.0:8080, session id is 60.
4/19/2007 11:14:43 AM - 60: Unable to get hostname from address: 220.149.80.27
Send failed: An existing connection was forcibly closed by the remote host
4/19/2007 11:14:43 AM - 60: Exception processing messages: An existing connection was forcibly closed by the remote host
4/19/2007 11:48:24 AM - Connection accepted from 61.95.141.163:3399 on local address 10.0.10.55:8080, session id is 61.
4/19/2007 11:48:24 AM - 4/19/2007 11:48:24 AM - Server Exception (407): [GET / HTT - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/19/2007 11:48:24 AM - 61: Exception processing messages: UNRECOGNIZED_MESSAGE
4/19/2007 11:50:03 AM - Connection accepted from 61.95.141.163:3405 on local address 10.0.10.55:8080, session id is 62.
4/19/2007 11:50:03 AM - 4/19/2007 11:50:03 AM - Server Exception (407): [GET / HTT - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/19/2007 11:50:03 AM - 62: Exception processing messages: UNRECOGNIZED_MESSAGE
4/19/2007 2:37:43 PM - Connection accepted from 207.189.200.244:4114 on local address 0.0.0.0:8080, session id is 63.
4/19/2007 2:37:48 PM - 63: Unable to get hostname from address: 207.189.200.244

Beth · Post by **Beth** » Fri Apr 20, 2007 10:38 am

How many are using SOS? Are any in the office on the domain?

When you are in your office, are you on the same domain/location as your SOS server, or is the SOS server remote to both locations?

Is anyone else experiencing connection issues?

pratyush.shukla · Post by **pratyush.shukla** » Fri Apr 20, 2007 12:51 pm

At the moment, I am the only one who is using SourceOffsite. These are different domains. Like:

1) The network where the SOS server is installed in called "IND-DEL"
2) At home I am not in a domain - where it works.
3) At office, I am in a domain called, MELCO-LOCAL

Beth · Post by **Beth** » Fri Apr 20, 2007 3:14 pm

It's looking to me like maybe a router or firewall for the MELCO-LOCAL domain could be blocking the incoming communication from the SOS server. Would you have a networking person who could check that communication is allowed back in on port 8080? Can logs on that equipment be checked?

pratyush.shukla · Post by **pratyush.shukla** » Fri Apr 20, 2007 3:44 pm

Thanks for your help. Let me see if the network guys are ready to take this pain.

lbauer · Post by **lbauer** » Fri Apr 20, 2007 8:55 pm

4/19/2007 11:50:03 AM - 4/19/2007 11:50:03 AM - Server Exception (407): [GET / HTT - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/19/2007 11:50:03 AM - 62: Exception processing messages: UNRECOGNIZED_MESSAGE

It also looks like HTTP traffic may be coming in on the port used by the SOS Server. This can destablize the Server, which is expecting TCP\IP traffic only.