Quote from: doktor83 on Today at 02:27:44 PM

Quote from: agavrilyk on Today at 01:09:47 PM

Quote from: doktor83 on Today at 12:29:31 PM

Quote from: agavrilyk on Today at 08:37:30 AM

And who is this then
waw02s13-in-f14.1e100.net 443

Google server.

Quote from: agavrilyk on Today at 08:37:30 AM

Version 0.4.0 on Windows Server 2008,2012,2016,2019 works without issue.

Quote from: doktor83 on October 09, 2020, 03:41:26 PM

Cause this check wasnt implemented back then.

Windows 7,10 works.
Windows Server 2008,2012,2016,2019 doesn't work.
All machines are located behind 1 Mikrotik router and go out through 1 provider.
You can look at your check that you have implemented since version 0.4.
Or what is missing from Windows Server 2008,2012,2016,2019?
Thank you

If win7,10 works and all go out on same router then something is blocking it on windows server, because if it was the router then it wouldn't work on W7,W10.
If it was a miner issue then it wouldnt work on W7, W10 too

I got users running it on Win Servers.

I decided to experiment.
I took a server 2012 on which it does not work, installed Hyper-V there, deployed Windows 7 - it works without problems, I also deployed Windows 10 and also without any problems (I did not even turn off the firewall).
Since I have Windows Server 2008,2012,1019 then I have deployed Windows Server 2016 and it DOES NOT WORK.
Also, when launched on Windows Server 2019, it swears at
libcrypto 1-1_x64.dll

There is no such error on Windows 2008,2012,2016.

Can you install at least some of the Windows Server and check it out?
Thank you.