I use Windows 8.1. It is the same as the Windows 7.
When you sync first time, it will be slow process, difficult to find peers.
Topic: Ether Peers - Geth Failure (Read 465 times)
I use Windows. This is my command line :
geth --rpc --rpcaddr 192.168.1.201 --rpcport 8545 console
It works most of the time.
geth --rpc --rpcaddr 192.168.1.201 --rpcport 8545 console
It works most of the time.
Just tested on lappy.
Geth is working better for me on Windows 7 with a peerCount of 6.
Guess I'll be changing my rig over to w7.
Kill me. Please.
I use Windows. This is my command line :
geth --rpc --rpcaddr 192.168.1.201 --rpcport 8545 console
It works most of the time.
geth --rpc --rpcaddr 192.168.1.201 --rpcport 8545 console
It works most of the time.
Worst program ever created in the history of cryptocurrency or maybe I'm doing something wrong.
Ports are all opened on firewall, including 30303.
net.listening is reporting true
net.peerCount is 0 will climb to 1 or 2 and go back to 0.
Peers are constantly saying "subprotocol error" or "too many peers".
I've been running this for hours and I want to shoot myself.
Command I'm running: geth --rpc --rpccorsdomain "*" --genesis "genesis_block.json" --verbosity 5 --maxpeers 128 --fast --nat any
I'm using Linux. Would Windows be easier?
Thank you for any help.
Ports are all opened on firewall, including 30303.
net.listening is reporting true
net.peerCount is 0 will climb to 1 or 2 and go back to 0.
Peers are constantly saying "subprotocol error" or "too many peers".
I've been running this for hours and I want to shoot myself.
Command I'm running: geth --rpc --rpccorsdomain "*" --genesis "genesis_block.json" --verbosity 5 --maxpeers 128 --fast --nat any
I'm using Linux. Would Windows be easier?
Thank you for any help.
Jump to: