cgminer tells me my pushpool server is dead!! ?

This setup is for learning purposes, so I will reinstall the server and set it up from scratch once I get this figured out
the pushpool server is by its self on one machine with bitcoind running.
the cgminer is on another machine connected to the network.

any one have any idea what I have done wrong??

server.json

Quote

{
   # network ports
   "listen" : [
      # binary protocol (default), port 8342
      { "port" : 8342 },

      # HTTP JSON-RPC protocol, port 8341
      { "port" : 8341, "protocol" : "http-json" },

      # HTTP JSON-RPC protocol, port 8344,
      # with trusted proxy appserver.example.com forwarding
      # requests to us
      { "port" : 8332, "protocol" : "http-json",
        "proxy" : "192.168.1.118" },

      # binary protocol, localhost-only port 8338
      { "host" : "192.168.1.118", "port" : 8343, "protocol" : "binary" }
   ],

   # database settings
   "database" : {
      "engine" : "mysql",
      "host" : "localhost",
      "port" : 3306,
      "name" : "miningfarm",
      "username" : "xxxxxxx",
      "password" : "xxxxxxx",
      "sharelog" : true,
      "stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
      "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

   },

   # cache settings
#   "memcached" : {
#      "servers" : [
#         { "host" : "127.0.0.1", "port" : 11211 }
#      ]
#   },

   "pid" : "/tmp/pushpoold.pid",

   # overrides local hostname detection
   "forcehost" : "localhost.localdomain",

   "log.requests" : "/tmp/request.log",
   "log.shares" : "/tmp/shares.log",

   # the server assumes longpolling (w/ SIGUSR1 called for each blk)
   "longpoll.disable" : false,

   # length of time to cache username/password credentials, in seconds
   "auth.cred_cache.expire" : 75,

   # RPC settings | Notice how this ISN'T port number 8332 this is becuase the same port number should not becuase inconjunction with the JSON RPC port other wise you'll get 500 errors
   "rpc.url" : "http://127.0.0.1:8335/",
   "rpc.user" : "xxxxxxx",
   "rpc.pass" : "xxxxxxx",

   # rewrite returned 'target' to difficulty-1?
   "rpc.target.rewrite" : true
}

bitcoin.conf

Quote

#rpcpassword=xxxxxxx

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# … or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
server=1

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

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# 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=192.168.1.*

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

# 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=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

# Miscellaneous options

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

# Use SSE instructions to try to generate bitcoins faster. For muliple core processors.
#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

# Allow direct connections for the ‘pay via IP address’ feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
min=1

# Minimize to the system tray
minimizetotray=1

Server Side:

Quote

[2013-03-01 01:44:29.693680] Listening on host :: port 8342
[2013-03-01 01:44:29.694469] Listening on host :: port 8341
[2013-03-01 01:44:29.694891] Listening on host :: port 8332
[2013-03-01 01:44:29.695182] Listening on host 192.168.1.118 port 8343
[2013-03-01 01:44:29.700813] initialized
[2013-03-01 01:45:21.553129] client host 192.168.1.72 port 48943 connected
[2013-03-01 01:45:21.553563] client host 192.168.1.72 port 48944 connected
[2013-03-01 01:45:21.554151] client host 192.168.1.72 port 48945 connected
[2013-03-01 01:45:56.361272] client host 192.168.1.72 port 48949 connected
[2013-03-01 01:45:56.361794] client host 192.168.1.72 port 48950 connected
[2013-03-01 01:45:56.362289] client host 192.168.1.72 port 48951 connected
[2013-03-01 01:46:56.365829] client host 192.168.1.72 port 48955 connected

cgminer:

Quote

4: Enabled Dead Priority 4: http://192.168.1.118:8343 User:admin101.stargate