My original post was a result of changing the "Port" information in the miner.conf from 63336 to 63335, looking at the listener on the diskcoind server, tcp ipv4 is listening on 63335 and ipv6 is on 63336 which is the default and I changed it because I am not routing ipv6. Since, I nage changed it back to 63336 and the logs now read differently error however the miner still performs the same. It opens but does not do anything.
"Mode" : "pool",
"Server" : "192.168.1.109",
"Port": 63336,
"UpdaterAddr" : "192.168.1.109",
"UpdaterPort": 63336,
"InfoAddr" : "192.168.1.109",
"InfoPort": 63336,
"EnableProxy": false,
"ProxyPort": 8126,
"Paths": [
"D:\\"
],
15:57:34 === Config loaded ===
15:57:34 Miner path: C:\Users\dc-test\Downloads\dcminer.0714\dcminer.0714\
15:57:34 Searching servers...
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Updater thread started
15:57:34 Update mining info
15:57:34 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:34 *! GMI: error parsing JSON message from pool
15:57:35 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:35 *! GMI: error parsing JSON message from pool
15:57:36 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:36 *! GMI: error parsing JSON message from pool
15:57:37 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:37 *! GMI: error parsing JSON message from pool
15:57:38 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:38 *! GMI: error parsing JSON message from pool
15:57:39 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:39 *! GMI: error parsing JSON message from pool