When trying to start GUIMiner (v2011-08-24) I keep getting "Problems communicating with bitcoin RPC" error. None of the probably...4+ guides that I've tried out so far have fixed this problem. I feel like it's something stupid I'm missing, but I would rather just ask and look stupid then keep trying to figure this out.

# You must set rpcuser and rpcpassword to secure the JSON-RPC api#rpcuser=Ulysseys#rpcpassword=YourSuperGreatPasswordNumber_385593

# By default, only RPC connections from localhost are allowed. Specify# as many rpcallowip= settings as you like to allow connections from# other hosts (and you may use * as a wildcard character):#rpcallowip=10.1.1.34#rpcallowip=(removed)

# Listen for RPC connections on this TCP port:rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind# running on another host using this option:rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate# with Bitcoin -server or bitcoind#rpcssl=1

# OpenSSL settings used when rpcssl=1rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTHrpcsslcertificatechainfile=server.certrpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoinsgen=0

# Use SSE instructions to try to generate bitcoins faster.#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for# both prior transactions and several dozen future transactions.keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees# are more likely than free transactions to be included in generated blocks, so may# be validated sooner.paytxfee=0.00

.TH BITCOIN.CONF "5" "January 2011" "bitcoin.conf 3.19".SH NAMEbitcoin.conf \- bitcoin configuration file.SH SYNOPSISAll command-line options (except for '-datadir' and '-conf') may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file..TPThe configuration file is a list of 'setting=value' pairs, one per line, with optional comments starting with the '#' character..TPThe configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, bitcoind(1) will look for a file named bitcoin.conf(5) in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the '-datadir' and '-conf' command-line arguments..SH LOCATIONbitcoin.conf should be located in $HOME/.bitcoin.SH NETWORK-RELATED SETTINGS.TP.TP\fBtestnet=\fR[\fI'1'\fR|\fI'0'\fR]Enable or disable run on the test network instead of the real *bitcoin* network..TP\fBproxy=\fR\fI'127.0.0.1:9050'\fRConnect via a socks4 proxy..TP\fBaddnode=\fR\fI'10.0.0.2:8333'\fRUse as many *addnode=* settings as you like to connect to specific peers..TP\fBconnect=\fR\fI'10.0.0.1:8333'\fRUse as many *connect=* settings as you like to connect ONLY to specific peers..TP\fBnoirc=\fR[\fI'1'\fR|\fI'0'\fR]Use or Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to find other peers..TP\fRmaxconnections=\fR\fI'value'\fRMaximum number of inbound+outbound connections..SH JSON-RPC OPTIONS.TP\fBserver=\fR[\fI'1'\fR|\fI'0'\fR]Tells *bitcoin* to accept or not accept JSON-RPC commands..TP\fBrpcuser=\fR\fI'username'\fRYou must set *rpcuser* to secure the JSON-RPC api..TP\fBrpcpassword=\fR\fI'password'\fRYou must set *rpcpassword* to secure the JSON-RPC api..TP\fBrpctimeout=\fR\fI'30'\fRHow many seconds *bitcoin* will wait for a complete RPC HTTP request, after the HTTP connection is established..TP\fBrpcallowip=\fR\fI'192.168.1.*'\fRBy default, only RPC connections from localhost are allowed. Specify as many *rpcallowip=* settings as you like to allow connections from other hosts (and you may use * as a wildcard character)..TP\fBrpcport=\fR\fI'8332'\fRListen for RPC connections on this TCP port..TP\fBrpcconnect=\fR\fI'127.0.0.1'\fRYou can use *bitcoin* or *bitcoind(1)* to send commands to *bitcoin*/*bitcoind(1)* running on another host using this option..TP\fBrpcssl=\fR\fI'1'\fRUse Secure Sockets Layer (also known as TLS or HTTPS) to communicate with *bitcoin* '-server' or *bitcoind(1)*. Example of OpenSSL settings used when *rpcssl*='1':.TP\fBrpcsslciphers=\fR\fI'TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH'\fR.TP\fBrpcsslcertificatechainfile=\fR\fI'server.cert'\fR.TP\fBrpcsslprivatekeyfile=\fR\fI'server.pem'\fR.TP.SH MISCELLANEOUS OPTIONS.TP\fBgen=\fR[\fI'0'\fR|\fI'1'\fR]Enable or disable attempt to generate bitcoins..TP\fB4way=\fR[\fI'0'\fR|\fI'1'\fR]Enable or disable use SSE instructions to try to generate bitcoins faster..TP\fBkeypool=\fR\fI'100'\fRPre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions..TP\fBpaytxfee=\fR\fI'0.00'\fRPay an optional transaction fee every time you send bitcoins. Transactions with fees are more likely than free transactions to be included in generated blocks, so may be validated sooner..TP\fBallowreceivebyip=\fR\fI'1'\fRAllow direct connections for the 'pay via IP address' feature..TP.SH USER INTERFACE OPTIONS.TP\fBmin=\fR[\fI'0'\fR|\fI'1'\fR]Enable or disable start bitcoind minimized..TP\fBminimizetotray=\fR[\fI'0'\fR|\fI'1'\fR]Enable or disable minimize to the system tray..SH "SEE ALSO"bitcoind(1).SH AUTHORThis manual page was written by Micah Anderson <micah@debian.org> for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation.

On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.

I've tried running bitcoind and all it does is open for around 5 seconds, this message shows:

"Error: To use bitcoind, you must set rpcpassword=<password>in the configuration file: C:\Username\AppData\Roaming\Bitcoin\bitcoin.confIf the file does not exist, create it with owner-readable-only file permissions."

I also don't know how to make a owner-readable-only file permission, there is no option for this that I could find besides the "read-only" check box at the bottom of properties and I've tried that and it still shows that "Error:" message. Also, it's still showing as a text document file. I've tried renaming it to .conf, and .cfg with now such luck changing it's type. Edit: I grabbed another .cfg file from somewhere else on the computer and tried naming it bitcoin.conf, and bitcoin.cfg and put the required information in it and it's still not working.

Please tell me this is something easy to fix, this is getting uber annoying. Haha.

# You must set rpcuser and rpcpassword to secure the JSON-RPC apirpcuser=Ulysseysrpcpassword=YourSuperGreatPasswordNumber_385593

# By default, only RPC connections from localhost are allowed. Specify# as many rpcallowip= settings as you like to allow connections from# other hosts (and you may use * as a wildcard character):rpcallowip=10.1.1.34rpcallowip=(removed)

the instructions I gave where to solo mine from another computer on your network...

is the miner and bitcoind on the same machine?

in that case use IP : 127.0.0.1

I messaged you, hopefully you got it since I'm new here. I'm just going to try to start from the top following your directions only and not trying others until I try yours. That way I don't have to worry about crap being messed up already before I apply your settings.