Have you tried 0.5.5.4? I couldn't get 1.0.1 working right (as stated in my previous post), so I've switched.It was the 1.0.1 version. All on Windows 8.1 x64.
On 0.5.5.3 (32 bit), the lowest setting for "Delay Between Measurements (sec)" is 15. On 0.5.5.4 (64 bit), the lowest setting is 10. That makes me wonder if 0.5.5.4 doesn't score better.I use the 32bit version so I don't have to worry about installing 64bit JAVA. It is just simpler and I have gotten lazy with it. I also use the 0.5.5.3 and yes it will sometimes seem like it isn't working even though they still score. I couldn't tell you what kind of programmers they have, but they seem to move slow.
Done http://hardforum.com/showpost.php?p=1041172630&postcount=6This might have been documented in the last 15 pages, but I thought I'd post what I found.
It looks like windows firewall will block inbound ICMP even if you have given the program send and receive in windows firewall.
I followed the guide here on my windows 10 machine, and enabled firewall. ICMP traffic was not blocked anymore. I will have to go back and do the same on the other machines now.
(edit) Further info: This fixed the issue with my W10tp x64, W8.1 x64, and W7 x32 installs. Should this be added to the thread for installing the client?
Fixed. Not sure why using the tools from the forum that it isn't liking the links. So, this is one of many times I've had to manually edit the links.Gilthanis,
I did see you quoted my post in the instructions thead, cool, maybe as you fix the link, you could toss in my username.
I will have to look more at the ICMP blocking. I am sure that the DIMES agent ICMP rules are good, they are essentially the same as the rule that I created. The way I have it fixed opens inbound ICMP for everything, some people might concider that a risk. DIMES agent must be relying on inbound ICMP to some other program that is not gaining an inbound ICMP rule. I will keep digging, because if I can find this, we can be more secure. I am thinking javaw.exe possibly.