Arena 3.5.1 - Autoplayer

[hgm]

OK, so you see the client part is not more difficult than using any other engine in the GUI; you just have to know the IP address of the remote engine.

The difficulty is apparently to set up the server. For me that worked after I set connect64 as an exception in AVG. I just have to start connect64 with the specification of the engine executable and the engine folder on its command line. I could make a shortcut for that, if I wanted. I am really puzzled why it wouldnot work similarly easy for you. Are you sure this AVAST is sufficiently disabled to no longer obstruct us?

[Nordlandia]

Yes Avast have that file in exception.

Atleast now i can connect to your remote engine.

[hgm]

Well, not anymore... My Windows 8.1 on that laptop decided it was time for a mandatory update, and put me an ultimatum of 15 minutes to save whatever I still had open, or lose the work. It is now installing the updates.

Isn't it possible to completely switch off both AVG and AVAST on computer A, to make absolutely sure they won't interfere, and then start connect64 with the engine there, and try again to reach it from machine B?

I just had a weird experience here: when I started connect64 as engine server from my desktop, I could not reach it from my laptop, even though I had seen no complaints from any firewall. Turn's out there is a McAfee on that computer which tries to sell itself to me. As I am not interested in having it, I always ignores the popups for that. But it turned out that despite me not buying it, it was still blocking the server, but it would not show the popup for allowing it to proceed, unless I answered the question about buying it first!

[Nordlandia]

Can't you make some shortcuts please this is so time consuming and annoying.

I can try restart both computers and disable avg and avast then retry.

[hgm]

What exactly is time consuming? Starting connect64 as a server?

You don't know how to make shortcuts? (Right-click the program and select 'Create Shortcut' from the menu that pops up. Then right-click the shortcut that appears, and append the 'target' field with the "-ec ENGINENAME -ed ENGINEFOLDER" parameters. Drag the shortcut to the desktop. Double-clicking it should now start the engine server.)

Shortcuts usually cease working when you move them from one machine to another.

[Nordlandia]

I have to disappoint you it's still no connection from computer B.

I'm on the verge of giving up

I found the issue!

I had to disable windows firewall on both computers and it worked!

Now what is the right procedure?

[hgm]

Finally!

Strange that the Windows firewall blocks everything without notification. For me it always throws up a dialog to ask if I want to allow it. What Windows version do you have? Were you logged on as a user without admin rights?

I suppose the trick now is to get connect64 also on the exception list of the Windows firewall. I suppose you can do that via the Settings menu or Control Panel.

I guess first you could check if the AVAST and AVG exceptions you defined are working, by switching AVG and AVAST on again (one by one), and thesting if it then stays working. If it does you could try the Windows firewall. Or you could leave it off. It beats me why you would need three firewalls. (Or even two.) Especially on a computer that no one on the outside could even see, as they would have to pass your router first, which also has a firewall. These firewalls on the computer itself only seem needed to protect you from attacks by your other computers...

[Nordlandia]

I have to disable firewall to make it work i just comfirmed it.

In any case how to proceed now since both computers is connected

[hgm]

You install "connect64 192.168.10.149" as an engine in the GUIs you want to use on computer B. And when you want to play a real engine you have installed in that GUI against an engine on computer A, you then go to computer A, and start connect64 with the desired engine there from a command-prompt window, as I described in steps 1-3 of the 76th post in this thread. Then you select connect64 as engine in your GUI on machine B, and set it playing like an ordinary engine. That is all. If you use always the same engine on computer A, or just a few, you could make short-cuts for starting connect64 with those engines. If you would want to use different engines all the time, then short-cuts wouldnot be very helpful.

[Nordlandia]

Fritz 15 won't let me install that connect64.exe for some reasons.

I don't get anywhere

C:\Users\Kajapix>C:\Users\Kajapix\Documents\connect64\connect64.exe -ec "stockfish 7 x64 bmi2.exe" -ed "F:\Chess Engines\New Stockfish\Stockfish 7\Stockfish 7
# waiting to connect
# set up server
# listening on port 27015
# accepted incoming call
# started stockfish 7 x64 bmi2.exe
# connected
telluser recv failed with error: 10054
# quit stockfish 7 x64 bmi2.exe
# set up server
# listening on port 27015
telluser send failed (error 10054)
# Process died
# waiting to connect
# accepted incoming call
telluser send failed (error 10054)
telluser recv failed with error: 10038
# set up server
# listening on port 27015
# accepted incoming call
telluser send failed (error 10054)
telluser recv failed with error: 10038
# set up server
# listening on port 27015

We previous comfirmed your remote engine worked
flawlessly so i don't get why computer A don't start once i play 1. e4 on computer B.