Software caused disconnection problems?

hvilken error får du .. prøv at paste precis hvad mirc skriver ..

og har du prøvet med en anden server?

det er nok det her der er galt ;) .. men hvad du kan gøre ved ved jeg ikke ..
jeg har oplevet det et par gange ... men jeg kan desværre ikke huske i hvilken sammenhæng.

WSAECONNABORTED (10053) Software caused connection abort.

Berkeley description: A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.

WinSock description: Partly the same as Berkeley. The error can occur when the local network system aborts a connection. This would occur if WinSock aborts an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).

TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).

User suggestions: There are a number of things to check, that might help to identify why the failure occurred. Basically, you want to identify where the problem occurred.

Ping the remote host you were connected to. If it doesn't respond, it might be off-line or there may be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again).
Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step)
Ping your local router address. If you're on a serial connection, your local router is the IP address of the host you initially logged onto with SLIP or PPP.
Ping a host on the same subnet as the host you were connected to (if you know one). This will verify that the destination network is functioning.
Try a "traceroute" to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.

jeg vil tro at hvis du prøver en ny server skulle det være fixet

Den kan også gøre det hvis dit navn allerede er taget.
Så står det nederst i skærmen, og lidt efter bliver du smidt af serveren.
Da der ikke må være 2 med samme navn.

så står der nick in use already eller noget ligende :P

loadet >> læs lige mit svar igen, og se at det har jeg skrevet!

ja men det har ikke noget med Software caused disconnection problem at gøre -- det er det samme som at sige at man også kan bliver disconnected hvis man trækker netkablet ud.

det får jeg tit også.
* [10053] Software caused connection abort
* Disconnected


alt for nedtur.
Jeg kan dog komme på igen enten første gang eller et par forsøg efter.

Men jeg kan ikke komme op igen.. så ksal jeg installere en ny mirc client.. men nu det li meget..