Error 10061: No connection could be made because the target machine actively refused it

395 views
Skip to first unread message

tedsco...@gmail.com

unread,
Sep 4, 2017, 3:22:16 AM9/4/17
to tryton


I have recently installed the tryton client. I have been able to connect to the server and run the client successfully on my Ubuntu desktop.

However, when a colleague installed the client application on their Windows 10 laptop, the got the following error:

[Error 10061]: No connection could be made because the target machine actively refused it

I have SSH installed and running on the Linux server.

This is what I've done so far, to try and solve the problem:

1. run ps aux | grep ssh to make sure SSH is running on server:

root 4359 0.0 0.1 65520 6304 ? Ss Sep02 0:02 /usr/sbin/sshd -D
root 19148 0.0 0.1 95400 6704 ? Ss 08:23 0:00 sshd: morpheous [priv]
morpheo+ 19166 0.0 0.0 95400 3380 ? S 08:23 0:00 sshd: morpheous@pts/0

2. run netstat -l to make sure port 8000 is being listened to:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:ssh *:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
tcp6 0 0 [::]:8000 [::]:* LISTEN
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 16673 /run/user/1000/systemd/private
unix 2 [ ACC ] STREAM LISTENING 11592 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 11597 /var/run/docker.sock
unix 2 [ ACC ] STREAM LISTENING 11601 /run/uuidd/request
unix 2 [ ACC ] STREAM LISTENING 15199 /run/docker/libnetwork/c691c7be0884cd7e163479e2dca860cec5877a0dc01ed98a50e22d236d70b7e0.sock
unix 2 [ ACC ] STREAM LISTENING 9616 /run/systemd/private
unix 2 [ ACC ] SEQPACKET LISTENING 9623 /run/udev/control
unix 2 [ ACC ] STREAM LISTENING 9631 /run/systemd/fsck.progress
unix 2 [ ACC ] STREAM LISTENING 9644 /run/systemd/journal/stdout
unix 2 [ ACC ] STREAM LISTENING 15072 /var/run/docker/libcontainerd/docker-containerd.sock

3. Used putty from the Windows machine, to try to connect to the server. However, when presented with the Linux CLI and prompted to login, when I enter valid credentials, I get the error message: Access denied

4. I obtained the IP address of the windows machine, and then checked /var/log/auth.log on the server machine to see if the IP address of the windows machine was in there (to see if the machine had been refused connection as reported by the Tryton client app). THERE WAS NO RECORD OF THE IP ADDRESS IN THE LOG FILE!

Can someone help with the required steps needed to diagnose and fix this problem?

Sergi Almacellas Abellana

unread,
Sep 4, 2017, 3:34:38 AM9/4/17
to try...@googlegroups.com
El 03/09/17 a les 15:58, tedsco...@gmail.com ha escrit:
> Could you post the config file you are using for trytond? By default
trytond only listens to localhost, so it's not possible to connect from
other machines. You can change is using the listen property of the web
section in the configuration file:

http://doc.tryton.org/4.4/trytond/doc/topics/configuration.html#listen

Hope it helps.

--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk

Cédric Krier

unread,
Sep 4, 2017, 3:40:07 AM9/4/17
to tryton
On 2017-09-03 06:58, tedsco...@gmail.com wrote:
> Can someone help with the required steps needed to diagnose and fix this problem?

It was asked on https://stackoverflow.com/questions/46022665/error-10061-no-connection-could-be-made-because-the-target-machine-actively-ref
But the topic was deleted because the user just did not use the right
IP.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
Reply all
Reply to author
Forward
0 new messages