Jump to content


Photo
* * * * * 1 votes

Fix: "An existing connection was forcibly closed by the remote host"


  • Please log in to reply
14 replies to this topic

#1 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 13 December 2006 - 01:15 PM

Solving the forcibly closed connection


Statement of problem


Some hubs (Outdated hubs) have problems with the new connection types(NMDC2) and when you connect to such hub you get "An existing connection was forcibly closed by the remote host.", because hubs consider your $MyInfo for invalid.

NOTE:This is solution only for the outdated hubs problem.You can get the same message for different reasons.


Solution

You must use the old connection types(NMDC1) (and not use emulation for now).To change your current connection type:1. Go to Settings (General tab).
2. Select "Connection Type (old DC++ method)" and choose your connection.
Here's an example:
Posted Image



#2 balder

balder

    AKA [Linux-Admin]Cheers

  • Support
  • 535 posts

Posted 14 December 2006 - 09:04 PM

ifmn can you explain why you have to do this please :blushing:

#3 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 15 December 2006 - 11:45 AM

ifmn can you explain why you have to do this please :)


PM...

#4 Seeker

Seeker

    Senior

  • Member
  • PipPipPipPip
  • 237 posts

Posted 15 December 2006 - 04:55 PM

Solving the forcibly closed connection


Statement of problem


Some hubs have problems with the new connection types and when you connect to such hub you get "An existing connection was forcibly closed by the remote host."
Solution

You must use the old connection types (and not use emulation for now).To change your current connection type:1. Go to Settings (General tab).
2. Select "Connection Type (old DC++ method)" and choose your connection.
Here's an example:
Posted Image



thats not true, i have it on that setting all the time, yet i still get "An existing connection was forcibly closed by the remote host."
Posted Image

#5 Zlobomir

Zlobomir

    Master of Puppets & Soldier of Fortune

  • Tester
  • 2,459 posts

Posted 15 December 2006 - 05:05 PM

Maybe ifmn has solved only one of the reasons, and you have another issue.

Apex DC++ Guides
 


#6 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 15 December 2006 - 05:28 PM

Maybe ifmn has solved only one of the reasons, and you have another issue.


Yes, my solution is for outdated hubs :

Some hubs have problems with the new connection types and when you connect to such hub you get "An existing connection was forcibly closed by the remote host."


The msg tells you that the hub has disconnected you for some reason(in my guide - for 'invalid' connection type).I dont think you can do anything about the fact that the hub disconnects you.Please try connecting with some other client(or different settings) and if you find solution please post it :) .

#7 Seeker

Seeker

    Senior

  • Member
  • PipPipPipPip
  • 237 posts

Posted 15 December 2006 - 05:56 PM

true, but the problem still remains
Posted Image

#8 Crise

Crise

    Developer

  • Management
  • 2,958 posts

Posted 15 December 2006 - 06:16 PM

Note that this error message can also be "legit" (read: plain network problems on the hub side)

Also seeker, if you use DC++ emulation, your old connection type is "converted" to new one so that your connection type wouldn't give you away...
Crise
ApexDC++ - Lead Developer

Proud Affiliates of: TechGeeks Online, PeerWeb

#9 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 15 December 2006 - 06:58 PM

Note that this error message can also be "legit" (read: plain network problems on the hub side)

Also seeker, if you use DC++ emulation, your old connection type is "converted" to new one so that your connection type wouldn't give you away...


And that convert can be avoided by emulating some older dc++ version...(as i said)

#10 Crise

Crise

    Developer

  • Management
  • 2,958 posts

Posted 15 December 2006 - 08:47 PM

And that convert can be avoided by emulating some older dc++ version...(as i said)


Then there would be a risk of exposure in other areas :)
Crise
ApexDC++ - Lead Developer

Proud Affiliates of: TechGeeks Online, PeerWeb

#11 Seeker

Seeker

    Senior

  • Member
  • PipPipPipPip
  • 237 posts

Posted 16 December 2006 - 10:29 AM

what a tangled web we weed. so there is no solution to this mess?!
Posted Image

#12 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 16 December 2006 - 11:39 AM

it aint a mess...

Note that this error message can also be "legit" (read: plain network problems on the hub side)


did u try connecting with another client ?!?

#13 Crise

Crise

    Developer

  • Management
  • 2,958 posts

Posted 16 December 2006 - 12:03 PM

did u try connecting with another client ?!?


No but i don't need to, as this ain't any special error message specific to DC, but standard socket error message... so it very much can also be legit in some cases. (the text actually comes from windows)
Crise
ApexDC++ - Lead Developer

Proud Affiliates of: TechGeeks Online, PeerWeb

#14 ifmn

ifmn

    Not Banned

  • Member
  • PipPipPipPipPip
  • 524 posts

Posted 16 December 2006 - 12:24 PM

No but i don't need to, as this ain't any special error message specific to DC, but standard socket error message... so it very much can also be legit in some cases. (the text actually comes from windows)


I know and i was talking to seeker to prove him i aint creating a mess...

#15 Seeker

Seeker

    Senior

  • Member
  • PipPipPipPip
  • 237 posts

Posted 16 December 2006 - 12:44 PM

I know and i was talking to seeker to prove him i aint creating a mess...



its ok, i didnt say you were.
Posted Image


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users