@cheatoshin0 running win64binary T806
1. do I have to open some firewall ports in order to connect to the network? Output with -d is always only like this:
cheatcoin> state
Trying to connect to the main network.
cheatcoin> net hosts
Active hosts:
0. 7193D54C 0 sec, T13.806, local trust 127.0.0.1:0
cheatcoin>
2. miner also never works, only "badaddr" shows up in "miners" command with AAAAAAAA.... as an address
3. I am not running as an administrator
4. my system time is GMT+1, but I don't want to change that. This shouldn't be an issue just to sync up right?
5. I am using the following program:
https://www.nirsoft.net/utils/run_as_date.html (first time I'm using it, dont't like that it intercepts windows api calls, hopefully it intercepts the right call that your compiled binary is using to fetch the time)
- if I test with PHP, it works:
<?php
for ($i = 0; $i < 3; $i++) {
echo date('d.m.Y H:i:s') . "\n";
sle ep(1); // TYPO because of cloudflare protection! :( [SIC]
}
echo date('d.m.Y H:i:s') . "\n";
Console:
C:\Users\kbs1\Desktop\win64exe>"C:\cygwin64\bin\php.exe" timetest.php
10.01.2018 04:01:54
10.01.2018 04:01:55
10.01.2018 04:01:56
10.01.2018 04:01:57
Later with
runasdate /movetime /startin "C:\Users\kbs1\Desktop\win64exe" Hours:-1 "C:\cygwin64\bin\php.exe" timetest.php
10.01.2018 03:04:40
10.01.2018 03:04:41
10.01.2018 03:04:42
10.01.2018 03:04:43
So it seems to work nice.
I run cheatcoin.exe as such:
runasdate /movetime /startin "C:\Users\kbs1\Desktop\win64exe" Hours:-1 "C:\Users\kbs1\Desktop\win64exe\cheatcoin.exe" -d
....which produces results above. Any ideas please? I might try to compile on linux later, but I don't want to install full blown visual studio for windows compilation, that is not my use case.
6. dnet.log always the same...
2018-01-10 03:09:47 Current connections:
2018-01-10 03:09:47 Current streams:
2018-01-10 03:09:50 dnet gc: start to collect
2018-01-10 03:09:50 dnet gc: 9 threads total, 7 collected
2018-01-10 03:09:54 dnet.128: starting connection with 52.5.32.68:13654.
2018-01-10 03:09:54 dnet.129: starting connection with 52.5.32.68:13655.
2018-01-10 03:09:54 dnet.130: starting connection with 45.63.58.16:13654.
2018-01-10 03:09:54 dnet.131: starting connection with 109.90.229.170:35585.
2018-01-10 03:09:54 dnet.132: starting connection with 52.232.109.201:13654.
2018-01-10 03:09:54 dnet.133: starting connection with 199.16.31.96:3355.
2018-01-10 03:09:54 dnet.134: starting connection with 54.37.158.221:13654.
2018-01-10 03:09:54 dnet.132: connection error (-6), No error
2018-01-10 03:09:54 dnet: poll failed for socket 908
2018-01-10 03:09:54 dnet.129: connection error (12), No error
2018-01-10 03:09:55 dnet.131: connection error (-6), No error
2018-01-10 03:09:55 dnet.130: connection error (-6), No error
2018-01-10 03:09:55 dnet.134: connection error (-6), No error
2018-01-10 03:09:55 dnet.133: connection error (-6), No error
2018-01-10 03:09:55 dnet.128: connection error (-6), No error
2018-01-10 03:10:50 dnet gc: start to collect
2018-01-10 03:10:50 dnet gc: 9 threads total, 0 collected
2018-01-10 03:11:01 dnet.135: starting connection with 52.5.32.68:13654.
2018-01-10 03:11:01 dnet.136: starting connection with 52.5.32.68:13655.
2018-01-10 03:11:01 dnet.137: starting connection with 109.90.229.170:35585.
2018-01-10 03:11:01 dnet.138: starting connection with 45.63.58.16:13654.
2018-01-10 03:11:01 dnet.139: starting connection with 199.16.31.96:3355.
2018-01-10 03:11:01 dnet.140: starting connection with 52.232.109.201:13654.
2018-01-10 03:11:01 dnet.141: starting connection with 54.37.158.221:13654.
2018-01-10 03:11:02 dnet: poll failed for socket 536
2018-01-10 03:11:02 dnet.136: connection error (12), No error
2018-01-10 03:11:02 dnet.137: connection error (-6), No error
2018-01-10 03:11:02 dnet.135: connection error (-6), No error
2018-01-10 03:11:02 dnet.141: connection error (-6), No error
2018-01-10 03:11:02 dnet.139: connection error (-6), No error
2018-01-10 03:11:02 dnet.140: connection error (-6), No error
2018-01-10 03:11:03 dnet.138: connection error (-6), No error
2018-01-10 03:11:50 dnet gc: start to collect
2018-01-10 03:11:50 dnet gc: 16 threads total, 7 collected
2018-01-10 03:12:08 dnet.142: starting connection with 52.5.32.68:13654.
2018-01-10 03:12:08 dnet.143: starting connection with 45.63.58.16:13654.
2018-01-10 03:12:08 dnet.144: starting connection with 109.90.229.170:35585.
2018-01-10 03:12:08 dnet.145: starting connection with 52.5.32.68:13655.
2018-01-10 03:12:08 dnet.146: starting connection with 199.16.31.96:3355.
2018-01-10 03:12:08 dnet.147: starting connection with 52.232.109.201:13654.
2018-01-10 03:12:08 dnet.148: starting connection with 54.37.158.221:13654.
2018-01-10 03:12:09 dnet: poll failed for socket 716
2018-01-10 03:12:09 dnet.145: connection error (12), No error
2018-01-10 03:12:09 dnet.144: connection error (-6), No error
2018-01-10 03:12:09 dnet.148: connection error (-6), No error
2018-01-10 03:12:09 dnet.146: connection error (-6), No error
2018-01-10 03:12:09 dnet.147: connection error (-6), No error
2018-01-10 03:12:10 dnet.142: connection error (-6), No error
2018-01-10 03:12:10 dnet.143: connection error (-6), No error
2018-01-10 03:12:50 dnet gc: start to collect
2018-01-10 03:12:50 dnet gc: 16 threads total, 7 collected
2018-01-10 03:13:15 dnet.149: starting connection with 52.5.32.68:13655.
2018-01-10 03:13:15 dnet.150: starting connection with 52.5.32.68:13654.
2018-01-10 03:13:15 dnet.151: starting connection with 45.63.58.16:13654.
2018-01-10 03:13:15 dnet.152: starting connection with 199.16.31.96:3355.
2018-01-10 03:13:15 dnet.153: starting connection with 54.37.158.221:13654.
2018-01-10 03:13:15 dnet.154: starting connection with 52.232.109.201:13654.
2018-01-10 03:13:15 dnet.155: starting connection with 109.90.229.170:35585.
2018-01-10 03:13:16 dnet: poll failed for socket 816
2018-01-10 03:13:16 dnet.149: connection error (12), No error
2018-01-10 03:13:16 dnet.155: connection error (-6), No error
2018-01-10 03:13:16 dnet.153: connection error (-6), No error
2018-01-10 03:13:16 dnet.152: connection error (-6), No error
2018-01-10 03:13:16 dnet.154: connection error (-6), No error
2018-01-10 03:13:17 dnet.150: connection error (-6), No error
2018-01-10 03:13:17 dnet.151: connection error (-6), No error
2018-01-10 03:13:50 dnet gc: start to collect
2018-01-10 03:13:50 dnet gc: 16 threads total, 7 collected
2018-01-10 03:14:22 dnet.156: starting connection with 52.232.109.201:13654.
2018-01-10 03:14:22 dnet.157: starting connection with 109.90.229.170:35585.
2018-01-10 03:14:22 dnet.158: starting connection with 52.5.32.68:13654.
2018-01-10 03:14:22 dnet.159: starting connection with 199.16.31.96:3355.
2018-01-10 03:14:22 dnet.160: starting connection with 52.5.32.68:13655.
2018-01-10 03:14:22 dnet.161: starting connection with 54.37.158.221:13654.
2018-01-10 03:14:22 dnet.162: starting connection with 45.63.58.16:13654.
2018-01-10 03:14:23 dnet: poll failed for socket 824
2018-01-10 03:14:23 dnet.160: connection error (12), No error
2018-01-10 03:14:23 dnet.161: connection error (-6), No error
2018-01-10 03:14:23 dnet.157: connection error (-6), No error
2018-01-10 03:14:23 dnet.159: connection error (-6), No error
2018-01-10 03:14:23 dnet.156: connection error (-6), No error
2018-01-10 03:14:24 dnet.162: connection error (-6), No error
2018-01-10 03:14:24 dnet.158: connection error (-6), No error
2018-01-10 03:14:47 Active hosts:
0. 7193D54C 0 sec, T13.806, local trust 127.0.0.1:0
2018-01-10 03:14:47 Current connections:
2018-01-10 03:14:47 Current streams:
2018-01-10 03:14:50 dnet gc: start to collect
2018-01-10 03:14:50 dnet gc: 16 threads total, 7 collected
2018-01-10 03:15:29 dnet.163: starting connection with 109.90.229.170:35585.
2018-01-10 03:15:29 dnet.164: starting connection with 52.5.32.68:13655.
2018-01-10 03:15:30 dnet.165: starting connection with 52.5.32.68:13654.
2018-01-10 03:15:30 dnet.166: starting connection with 52.232.109.201:13654.
2018-01-10 03:15:30 dnet.167: starting connection with 45.63.58.16:13654.
2018-01-10 03:15:30 dnet.168: starting connection with 54.37.158.221:13654.
2018-01-10 03:15:30 dnet.169: starting connection with 199.16.31.96:3355.
2018-01-10 03:15:30 dnet.168: connection error (-6), No error
2018-01-10 03:15:30 dnet: poll failed for socket 648
2018-01-10 03:15:30 dnet.164: connection error (12), No error
2018-01-10 03:15:30 dnet.163: connection error (-6), No error
2018-01-10 03:15:30 dnet.165: connection error (-6), No error
2018-01-10 03:15:30 dnet.169: connection error (-6), No error
2018-01-10 03:15:30 dnet.166: connection error (-6), No error
2018-01-10 03:15:31 dnet.167: connection error (-6), No error
2018-01-10 03:15:50 dnet gc: start to collect
2018-01-10 03:15:50 dnet gc: 16 threads total, 7 collected
EDIT: and as such, we can see here that "runasdate" is effective in this situation => time is correct! ;-) NTP is used to fetch system time, and I only subtract one hour from it to get GMT (currently in my timezone)
Thank you a lot!