OK, i have some great news for those of us still using the older getwork type sha256 miners! but a brief explanation first, sorry. I have documented my miner issues in my earlier rantings in this thread about being kicked off nicehash ever since they implemented their DDoS protection measures, necessary of course, but it screwed my sha256 miner over big time. I thought it was nicehash's fault for awhile, but come to find out my miner had issues i wasn't really aware before that keep getting me banned. So I was willing to try anything to get my miner working, and so i followed the suggestion from Pfool about checking out his java proxy, and i am sure glad I did. Pfool obviously did all the work, but Pfool took my numerous debug logs and other network traffic to pinpoint my issues, which after only 5 days, Pfool identified and fixed it! Actually, as i am writing this, my miner is chugging along just fine, and it is great seeing an almost vertical line change show up in my sha256 payout chart on nicehash now. so here is what you need to do for your old getwork miners to get them working with nicehash again...

1. download the latest beta of the java proxy. it can be found here    https://github.com/Stratehm/stratum-proxy/releases    you have to have java loaded on your computer for it to run. the instructions to get it all running is on the main page of that site.

2. I have a ASICMiner Block Erupter Cube, which only uses getwork, hence the need for a stratum proxy. use the following command line with the java proxy to get it up and running. please note you need midstate enabled (default state with this proxy) for this particular miner.

java -jar stratum-proxy.jar --getwork-listen-port xxxx -h stratum.nicehash.com:3334 -u YOUR BTC Address -p xxxx -n NiceHash --set-extranonce-subscribe true --validate-sha256-getowrk-shares

changes the xxxx's to what you have going on for those options.

Some final notes...

my particular issue with getting banned by nicehash, was that my Cube was submitting shares that were either above or below the target difficulty, and while they were being reported as accepted by the proxy, they were getting rejected by nicehash. this basically looked like the reject share attacked they were DDoS with before, hence the instant ban. Now Pfool has implemented the "--validate-sha256-getowrk-shares" opion to have the proxy validate the shares before leaving to nicehash, and not submitting the ones that don't make the necessary targets.  while this has resulted in drastic drop in the acceptance rate reported the Cube (not nicehash, i have nice blue lines   ), at least it is not getting banned, and i am able to contribute some decent hash power again. i do want to stress that the latest version is basically a beta version, so i am sure Pfool will address this particular issue when he can, however it may be something that is inherent to getwork to statrum proxies that can't be fixed. i invite Pfool to chime in on anything presented here, especially if i am off base on something. i don't have a shred of programming skills, and my understanding of what is actually happening may be off. either way, my hat is off to Pfool on getting this far with my issue and i look forward to what he has in store for his java proxy.