RipBot Destributed Encoding Win10Win7 combo

Manul · 20th March 2018, 16:26

Guys/Gals,
Here is a weird case with RipBot. Used to have a working RipBot distributed setup on two Win7Pro x64 boxes. Migrated (fresh install) one to Win10 Pro and started to have weird problems: Win10 RipBot Client cannot connect to Win7 RipBot Server, BUT Win7's RipBot Client CAN connect to Win10's RipBot Server and even to a Win7 Pro VM. Win10 tries to connect for a few seconds and then goes back to offline. Win7's Server shows: "Socket Error # 10060
Connection timed out." Again, the other way around it does work: Win7 can easily connect to both Win10 and Win7 VM. Prerequisites:

RipBot 1.22.2.
Firewalls and Antiviruses are off.
VC++ redistributes are installed.
Did clean RipBot installs on all boxes.
Telnet to port 1000 on all boxes is OK (200 Welcome).
RipBot share is accessible and writable on all boxes.

Any ideas on what could be in play here?
Thank you in advance!

20th March 2018, 16:26	#1 \| Link
Manul Registered User Join Date: Feb 2007 Posts: 9	RipBot Destributed Encoding Win10Win7 combo Guys/Gals, Here is a weird case with RipBot. Used to have a working RipBot distributed setup on two Win7Pro x64 boxes. Migrated (fresh install) one to Win10 Pro and started to have weird problems: Win10 RipBot Client cannot connect to Win7 RipBot Server, BUT Win7's RipBot Client CAN connect to Win10's RipBot Server and even to a Win7 Pro VM. Win10 tries to connect for a few seconds and then goes back to offline. Win7's Server shows: "Socket Error # 10060 Connection timed out." Again, the other way around it does work: Win7 can easily connect to both Win10 and Win7 VM. Prerequisites: RipBot 1.22.2. Firewalls and Antiviruses are off. VC++ redistributes are installed. Did clean RipBot installs on all boxes. Telnet to port 1000 on all boxes is OK (200 Welcome). RipBot share is accessible and writable on all boxes. Any ideas on what could be in play here? Thank you in advance! Last edited by Manul; 20th March 2018 at 17:36.