It is impossible to sign in by COMETID

It is impossible to sign in by COMETID.

The problem of a name server or DNS server.

Reply: CometID cannot be signed in now.

but WEB pages and forums sign in OK.

Setup: It is automatic connection at the time of a start.

Use: BitComet 1.29

I can’t seem to sign in to bitcomet. what’s worst is that i can’t even log in to its homepage. am i the only one facing this problem? because of this, my dl is less than 10kb/s.. please fix or tell me if u guys are doing any updates

As for a problem, neither addition of the point nor the improvement in speed of some should be obtained.

It is not understanding ranking, either.

Do you use any IP filtering programs?

thank you for reply.

filter program not used.

i think network problem.

reason:ns1..com ns2..com(bitcomet used name server) mentenace date 16/10/2011.

   change data can not update global name server. (delay or not push change data)

I think there’s a server problem, as my BC didn’t manage to sign in all day long either.

Not that I care much about that, but just to clear this topic.

this problem of not being able to sign in just started for me right after i upgraded to bitcomet 1-29 is that a coincidence or not?

Hi. wavelink.

Thank you for your reply.

answer is NO.

It is not immediately after upgrade.

It became impossible to sign in about three days before.

I was facing the same too, fistly i thought i was the 1 got problem. anyhow, any1 know when will it be back on?

I don’t have a problem signing in, but then, I dropped back from 1.29

The cause seemed to be the server down.

It waits for recovery of an early server.

Thank you for you and the reply.

refer:BitComet General Discussion.

topic:servers offline.

The notice also of mail addressed to support was coming.

message:Deferred: Name server: bitcomet.com.: host name lookup failure.

Just installed 1.29 and it signs in as expected. If there was a server outage, it’s obviously been fixed.

Thank you.

Happily, it succeeded in sign-in.

I am thankful to you who sent a reply.

The problem solved this topic.

Yes, I believe it was a DNS update that takes a day or so to reach all areas.