Quote from: Dubrov on January 28, 2014, 03:38:13 PM

Quote from: halibit on January 28, 2014, 02:56:16 PM

Quote from: Dubrov on January 28, 2014, 02:11:27 PM

Quote from: halibit on January 28, 2014, 12:31:28 PM

There was something wrote about some china IPS blocks 4444,44444 port connetions.
So port 4444,44444 nodes you may cant use.
With first update I recommend dev may change port, so more secured/monitored clients can join in too.
Are you all in China?

It is not helpfull, as I wrote before, we tried all kind of ports:

addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278

Almost all clients use 4444 port and if your IPS for some reason block that, it may fixed when new client are launched, but I made one test if you like to try.
https://mega.co.nz/#!qRol1TYb!J16aO64JD4q9uw7vGRdrVUz0TbAFkOPDF-WbX55cFEU

There you can find version where port is changed to 3232
But this not change other clients nodes on irc network ofcourse.

This is not official version. Only change for original source is the port address.
Just for curious test. (Windows version)
(For me it's working. I have this in 3 win7 computer)

I downoaded this archive and run in virtual box with XP (many altcoin clients work on this virutal machine)

The behaviour of this client is the same:
1. Imideatly after start of the microCoin.exe I have 1 active connection
2. About 2 minutes nothing changes (sync don't start)
3. I lost connection at all

Here is my debug.log:
http://pastebin.com/RdyRBwDL

My microcoin.conf

Code:

rpcport=3232
rpcuser=user
rpcpassword=x
rpcallowip=*
server=1
listen=1
addnode=84.251.34.142:3232
addnode=145.220.255.56:35937
addnode=24.155.217.218:62494
addnode=183.171.178.11:10278

I coninue to investigate the trouble with connection.
Now I have stable 1 active connection and blockchain is syncronized!
I use your "Specailly compiled" version with no config file (there is no config file at all).
So I dont know what exactly did you change, but It give me one working connection (I suspect it is your node with the same compiled version).