Quote from: shefflad on October 29, 2013, 03:16:34 AM

Here's something to try:

For my example I'll pretend i'm connecting to Slush's pool, my worker is named 'myloginname.blade', and the password is 'testpassword', my computer is a Win7 32bit system with an IP of '192.168.5.5'.

Download BFGMiner - the best Blade Proxy

First step is to download the Windows7 BFGminer: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.2.3/bfgminer-3.2.3-win32.zip

Setup the blade

Next, go to the blade's setup menu, make sure your gateway and both dns entries are correct (they usually point to your router). For my example they would point to 192.168.5.1 (yours will be different)

Third step is to point the blade to your BFGMiner proxy. I would set '8332,8332' for the ports. For the Server addresses I point to the windows machine, '192.168.5.5,192.168.5.5'. Finally I make up a username and password on the blade, something like 'myblade:mypass,myblade:mypass' (it shouldnt match what you use for your pool connection, nor should it match any other blade).

Press the 'update/restart' button on the blade.

Prepare the computer

Now to setup the BFGMiner software, it's easy to give a test run. First thing to do is make sure your Windows machine isn't blocking port 8332. Easiest way to do this is to disable all firewalls (if only to test, you want to make sure to properly set the firewall up later). Once you're sure it won't block the port (or you tell it to unblock if it asks you), then move to the proxy itself:

Starting the proxy

Slush's pool url is 'mining.bitcoin.cz', and my pool worker info is 'myloginname.blade' / 'testpassword'. Knowing this, and knowing I told the blade to connect to port 8332 of the proxy, here would be my command line:

bfgminer -o mining.bitcoin.cz -u myloginname.blade -p testpassword --http-port 8332

Debugging Issues

If BFG starts up and it connects to slush's pool, then you know the software proxy is working. You'll see a line which says 'HTTP server listening in port 8332', this lets you know the proxy is running. This means BFG is good to go. If it doesn't connect or doesn't run, then debug that first.

You should shortly after see a worker connect (usually shows up as PXY) and it'll start hashing. BFG will show connected to slush's pool with your worker settings. Wait 3 minutes if needed.

If you don't see anything connect, log into the blade and make sure it's pointing to your computer's IP on the proper port, and then hit 'update/restart'. This will force the blade to try again.

Let us know how it goes.

right done all that still not connecting, can get bfg to run proxy it gets connccted but the blades will not communicate back seems like something is blocking it switched all antivirus and firewall off

[/quote]

Can you post a screenshot of your miner settings. and paste the command line code you have to launch bfgminer