Quote from: Dea on January 09, 2014, 01:35:29 PM

Quote from: woowoo on January 09, 2014, 01:18:23 PM

so is the port meant to be 13135 or 13145 ?
can see connections trying to port 13145
im forwarding both ports inbound just incase for the moment.

Not sure what that 13145 biz is about, but the .conf info is on point an allowed my wallet to pop a block for coins so, looks good, may wanna remove that 13145 port off your forward so you haven't any future problems from it.

Good luck an have a splendifferious day!

---------------

On a side note, I'd like to state that this coin may fool you into thinking it's a run of the mill coin, but at the same token, like mentioned above, it's a backed coin by trusted and talked to folks, I myself can be freely found among the chatrooms somewhere trying to make as many as I can laugh an lighten up, helping when I can, mostly skype an exchange chats but regardless, we are out there, among you all, learning and growing the same, we have a mission to bring about added services and support to an already beautiful and poetically helpful community, even if we are all a bunch of coin collecting / trading " Gulloms ".

May the Shwartz be with yous...

its all good, just noticed lots of connections out to 13145 , would of expected connections to 13135
took a while to connect, and i had to use the peer.dat that was linked before. im soloming so could be the reason.
anyway ive found a block, so must be working ok =)

netstat -an | grep 13145
tcp 0 0 192.168.1.110:45252 111.69.242.x:13145 ESTABLISHED
tcp 0 1 192.168.1.110:57065 75.73.60.x:13145 SYN_SENT
tcp 0 0 192.168.1.110:43210 173.175.73.x:13145 ESTABLISHED
tcp 0 0 192.168.1.110:48788 60.234.254.x:13145 ESTABLISHED
tcp 0 61 192.168.1.110:36595 50.135.112.x:13145 ESTABLISHED