I am using Zabbix server and Zabbix agent 3.2 and server and client are different locations via IP sec connectivity.I am facing the issue on windows agent. The agent gets the latest data of event logs and icmp but in Zabbix dashboard still shown red and shown (Get value from agent failed: ZBXTCPREAD failed: 104 Connection reset by peer). Hi to all, we have a RDS 2012 R2 farm with 2 gateway, 2 connection broker and 8 session host. We have a problem when a MAC user try to connect to farm from internet. The Microsoft Remote Desktop client version 8.0.36 (Build 27228) fails the connection with error: Connection reset by peer.
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Dec 30, 2017
Hi All I am new to NiceHash Miner Legacy . I have installed v1.8.2.0-Pre2 on a Windows 7 PC and mining with my CPU i7-6700K. After I started mining for several minutes, it appeared a 'Connection reset by peer' error. Attached please find the screenshot and log file. log.txt I have tried to switch to other 'Service Location', but it still have the same issue. How can I fix it? Thanks Felix |
commented Dec 30, 2017
you can try increasing the size of your virtual paging ram file? make it double the size of your physical ram |
commented Dec 30, 2017
also i have an i7 3770k (older than yours) and im hitting nearly 300h/s you not overclocking it or something? |
commented Jan 1, 2018
for speed read that https://github.com/nicehash/NiceHashMiner/wiki/Notes-and-hints-on-CPU-mining for conections droping.. nicehash have at start problems.. right now you have also problem? |
commented Jan 2, 2018
This error is happening to me as well sometimes in all locations... |
commented Jan 2, 2018
Hi jimmyhackers, dadoremix, sirbig Thanks for all your help. I have set the virtual page file size and then re-run the benchmark. After the benchmark completed, the NHML changed the default mining algorithms from Xmrig to Xmr-stak. After NHML use Xmr-stak for mining, the 'Connection reset by peer' error disappeared. In order to improve the hash rate, I have tried to set LOCKED PAGES in Memory (follow the instruction in https://msdn.microsoft.com/en-gb/library/ms190730.aspx) but it failed. After I reboot PC and windows desktop appeared few seconds, system hanged with a blue/yellow screen. Do you all have the same issue? Thanks Felix |
commented Jan 2, 2018
This is a problem related to nicehash servers. With or without LP enabled and doesn't matter the algo mining as long as it trys to communicate with nicehash servers it always happens 'connection reset by peer' after a few hours mining. |
commented Jan 22, 2018 • edited
edited
I'm getting this too on my Online server (xmrig). |
commented Jan 22, 2018
Here it is NiceHash support response related to this matter:
|
commented Jan 22, 2018
https://www.reddit.com/r/NiceHash/comments/7b3rbe/please_fix_eu_cryptonight_pool/dpfho8i/ Seems like they just don't feel the urgency to fix the issue. |
commented Jan 22, 2018
And why would they? It's a waste of time and money to enlarge the pool resources so weaker miners can actually mine CryptoNight. |
commented Jan 22, 2018
No, it's an oversight from their part since CryptoNight is the best coin to mine with CPUs at the moment. CPU miners can't compare with GPU miners. It's idiot to make both mine with the same difficulty and have their system kick out (decent) CPU miners. |
commented Jan 22, 2018
I doubt that they have the same difficulty but I think if you have a CPU mining around 200 H/s you should be fine. From personal experience I had problems with CPUs mining at 100+ H/s where the connection would reset all the time. |
commented Jan 22, 2018 • edited
edited
My CPU does 275 H/s, have been banned from Nicehash overnight and is forced to run at a static 200k diff. It barely finds any share. When I poolmine ETN, I get a variable difficulty from 3k to 10k. The issue is Nicehash, not our CPUs. |
commented Jan 22, 2018
I guess you are probably right, but I don't think NiceHash staff is too worried about this since there is no update regarding this issue for nearly 2 months now. |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment