After a lot of searching and false turns, I finally found GuiMiner to make use of my two computers both with NVidia cards. So Thumbs up on a reasonable program for using GPUs for mining.  

I know I'm bucking the trend here, but I want to Solo mine on my two machines and point them both to the same BitCoin instance running on one of the machines to collect any coins in one account.

I've got it running locally on one machine which has a GTX 470.
And it connects to localhost on that machine to an instance of BitCoin.exe. That seems to work fine and I'm getting 84MH. Which we can talk about later if that seems like a problem.

The other machine has a GTX 260, so I'd like to fire it up too.
But I can't connect between the machines.

Both machines are running Win 7 x64.

I've opened the firewall for BitCoin and for guiminer.exe and for poclbm.exe for both Home/work(private) and Public networks.
I'm guessing that I don't need to open it for guiminer.exe, but at this point I'm not sure.
Using TcpView ( from here if you've not seen it: http://technet.microsoft.com/en-us/sysinternals/bb897437 ) I see that poclbm.exe is trying to connect to the machine running BitCoin.
When I start the guiminer the following appears in the guiminer console:

Oddly enough. Using TCPView on the local machine shows this:
bitcoin.exe:2464   TCP   AlienStorm:8333   AlienStorm:0   LISTENING   

How strange. The local machine appears to be listening on 8333.
Is this because 8332 is used on the other machine, and they both need to be unique over the public network since I'm behind a NAT router?
So to connect to my local machine I have to use port 8333. Ok I guess I can deal with that.

But I'd like to use the other machine on the network.

Any clue why guiminer [poclbm.exe] can't connect to cyberstorm?
Actually, it does not appear to be able to connect to the local machine either.

TCPview shows a pile of strange entries:
   

Not knowing any better, I would guess that someone is not cleaning up their failed sockets.
But I do see this:

Which leads me to guess that the problem is not that the connection can't be established, but that the protocol fails in some other way.

Thanks for your help.
WG

Same problem here: Server is Win7 x64 SP1 and client is Win7 x32 with no updates.

I'm going to try XP next on client.

I noticed some weird behaviour also. Locally I was able to get GUIminer working, but then I tried to repeat my results, I can no longer connect to local bitcoin server.'

GUIminer client on remote client PC is stuck in "connecting" mode.


Here is my TCP/IP scan:



Seems to show local GUIminer is connected at 8332, but GUIminer doesn't think so.