hgm wrote:I knew it had to be some other firewall!
You should install it the same way you would install the engine that is running at the other side. Connect64.exe is just a proxy for the engine on the other machine, it behaves exactly as that remote engine, and the GUI would not see the difference. So if you run a UCI engine there you should install connect64 as UCI in the GUI, when you run a WB engine you should install it as WB.
Arena 3.5.1 allowed me to install it on both computers but there is no moves displayed in case i play 1. e4 on computer A or B.
You should do step 1-3 we discussed earlier on computer A, to set it up as a server. Then you should install connect64 with as parameter the IP address of computer A in the GUI you run on computer B. After that you should be able to play against connect64 in that GUI. There should not be a GUI on machine A, or a connect64 running in a command-prompt window on machine B. You should also be able to play another engine you installed in the GUI on computer B against connect64.
C:\WINDOWS\system32> I:\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
On computer B i type in:
C:\Users\Expert-2\Documents\Chess Engine\connect64 folder>connect64.exe 192.168.10.149
# waiting to connect
host = 192.168.10.149, port = 27015
telluser (192.168.10.149) Unable to connect to server!
Even with AVG and AVAST in exception. This is bothersome
This is indeed strange. It was working before, wasn't it? Did you restart the computer, and could it be that its IP address changed?
I am going to bed now. Tomorrow I could set up my own computer as a server, so you could try to run that from the command line or GUI, to make sure that at least that part has no problems.
OK, I set up an engine server for Fairy-Max on my laptop, and routed port 27015 (connect64's default port) to it. You should be able to connect to it through:
connect64 83.163.204.254
from the command-prompt (and type protover 2 to see if there is any response), or install that command as a WB engine in a GUI.
Nordlandia wrote:C:\WINDOWS\system32>connect64 83.163.204.254
'connect64' is not recognized as an internal or external command,
operable program or batch file.
C:\WINDOWS\system32>protover 2
'protover' is not recognized as an internal or external command,
operable program or batch file.
Unfortunately
Shouldn't you start again at the folder where connect64.exe lies?
Yes, of course. I assumed you would know how to start connect64 by now... And it makes of course no sense at all to continue typing 'protover 2' as a command to the engine when you did not make the connection to it first.
