I've installed SourceOffsite Server 4.2 and able to connect from clients within my local network.
But the clients behind a NAT are not able to connect.
When I look at the log file, I see log entries as below -
1/15/2007 10:20:11 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 2.
1/15/2007 10:20:13 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 3.
1/15/2007 10:20:19 PM - 2: Unable to get hostname from address: 10.28.127.14
1/15/2007 10:20:19 PM - 3: Unable to get hostname from address: 10.28.127.14
Send failed: An existing connection was forcibly closed by the remote host
Send failed: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:19 PM - 3: Exception processing messages: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:19 PM - 2: Exception processing messages: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:19 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 4.
1/15/2007 10:20:24 PM - 4: Unable to get hostname from address: 10.28.127.14
Send failed: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:24 PM - 4: Exception processing messages: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:31 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 5.
1/15/2007 10:20:36 PM - 5: Unable to get hostname from address: 10.28.127.14
Send failed: An existing connection was forcibly closed by the remote host
1/15/2007 10:20:36 PM - 5: Exception processing messages: An existing connection was forcibly closed by the remote host
Can anyone help me on this issue.
Thanks,
Param.
Unable to connect to Server from a client behind NAT
Moderator: SourceGear
Users should be connecting to the external IP address.
If the client with the connection issue is 10.28.127.14, then it looks like the SOS Server is getting the connection, but not able to communicate back out again. Check to see if something is blocking or incorrectly routing traffic from the SOS Server port to the Internet.1/15/2007 10:20:11 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 2.
1/15/2007 10:20:13 PM - Connection accepted from 10.28.127.14:2415 on local address 0.0.0.0:8080, session id is 3.
1/15/2007 10:20:19 PM - 2: Unable to get hostname from address: 10.28.127.14
1/15/2007 10:20:19 PM - 3: Unable to get hostname from address: 10.28.127.14
Send failed: An existing connection was forcibly closed by the remote host
Send failed: An existing connection was forcibly closed by the remote host
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Linda,
Thanks for your quick reply.
I ran your comments through our network team, and they are saying that the firewall rule is only for the incoming traffic and it should automatically allow outgoing calls if the server uses the same port to communicate back.
I wanted to check with you, if this is always the case or this is some fallback option on connection error.
The entries in the log file is -
1/17/2007 11:20:19 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 2.
1/17/2007 11:20:22 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 3.
1/17/2007 11:20:25 AM - 2: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:25 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:25 AM - 2: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:26 AM - 2: Preparing to send the list of databases...
1/17/2007 11:20:26 AM - 2: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:26 AM - 2: Sending the challenge message body to the client.
1/17/2007 11:20:26 AM - 2: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:26 AM - 2: User disconnected from 10.28.127.14.
1/17/2007 11:20:27 AM - 3: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:27 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:27 AM - 3: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:27 AM - 3: Preparing to send the list of databases...
1/17/2007 11:20:27 AM - 3: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:27 AM - 3: Sending the challenge message body to the client.
1/17/2007 11:20:27 AM - 3: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:27 AM - 3: User disconnected from 10.28.127.14.
1/17/2007 11:20:28 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 4.
1/17/2007 11:20:32 AM - 4: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:32 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:32 AM - 4: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:32 AM - 4: Preparing to send the list of databases...
1/17/2007 11:20:32 AM - 4: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:32 AM - 4: Sending the challenge message body to the client.
1/17/2007 11:20:32 AM - 4: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:32 AM - 4: User disconnected from 10.28.127.14.
1/17/2007 11:20:40 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 5.
1/17/2007 11:20:45 AM - 5: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:45 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:45 AM - 5: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:45 AM - 5: Preparing to send the list of databases...
1/17/2007 11:20:45 AM - 5: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:45 AM - 5: Sending the challenge message body to the client.
1/17/2007 11:20:45 AM - 5: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:45 AM - 5: User disconnected from 10.28.127.14.
Your help is highly appreciated.
Thanks & Regards,
Param.
Thanks for your quick reply.
I ran your comments through our network team, and they are saying that the firewall rule is only for the incoming traffic and it should automatically allow outgoing calls if the server uses the same port to communicate back.
We did some more testing today after enabling the verbose. The thing we found out is that SOS is trying to do mbName lookup for the source IP using UDP on port 137 is this was never allowed.lbauer wrote:If the client with the connection issue is 10.28.127.14, then it looks like the SOS Server is getting the connection, but not able to communicate back out again. Check to see if something is blocking or incorrectly routing traffic from the SOS Server port to the Internet.
I wanted to check with you, if this is always the case or this is some fallback option on connection error.
The entries in the log file is -
1/17/2007 11:20:19 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 2.
1/17/2007 11:20:22 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 3.
1/17/2007 11:20:25 AM - 2: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:25 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:25 AM - 2: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:26 AM - 2: Preparing to send the list of databases...
1/17/2007 11:20:26 AM - 2: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:26 AM - 2: Sending the challenge message body to the client.
1/17/2007 11:20:26 AM - 2: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:26 AM - 2: User disconnected from 10.28.127.14.
1/17/2007 11:20:27 AM - 3: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:27 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:27 AM - 3: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:27 AM - 3: Preparing to send the list of databases...
1/17/2007 11:20:27 AM - 3: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:27 AM - 3: Sending the challenge message body to the client.
1/17/2007 11:20:27 AM - 3: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:27 AM - 3: User disconnected from 10.28.127.14.
1/17/2007 11:20:28 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 4.
1/17/2007 11:20:32 AM - 4: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:32 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:32 AM - 4: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:32 AM - 4: Preparing to send the list of databases...
1/17/2007 11:20:32 AM - 4: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:32 AM - 4: Sending the challenge message body to the client.
1/17/2007 11:20:32 AM - 4: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:32 AM - 4: User disconnected from 10.28.127.14.
1/17/2007 11:20:40 AM - Connection accepted from 10.28.127.14:2747 on local address 0.0.0.0:8080, session id is 5.
1/17/2007 11:20:45 AM - 5: Unable to get hostname from address: 10.28.127.14
1/17/2007 11:20:45 AM - The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for
1/17/2007 11:20:45 AM - 5: Connection from: 10.28.127.14 (10.28.127.14)
1/17/2007 11:20:45 AM - 5: Preparing to send the list of databases...
1/17/2007 11:20:45 AM - 5: Sending the challenge to the client.
Send failed: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:45 AM - 5: Sending the challenge message body to the client.
1/17/2007 11:20:45 AM - 5: Exception processing messages: An existing connection was forcibly closed by the remote host
1/17/2007 11:20:45 AM - 5: User disconnected from 10.28.127.14.
Your help is highly appreciated.
Thanks & Regards,
Param.