mIRC Home    About    Download    Register    News    Help

Print Thread
Joined: Nov 2008
Posts: 2
S
Bowl of petunias
OP Offline
Bowl of petunias
S
Joined: Nov 2008
Posts: 2
So, I've connected to this server many times before (but not where I'm at now) and never had any problems. I tried three different IRC programs and verified that it is some kind of network/conn. issue but I can't figure out what it is. I click connect and get:

Quote:
* Connecting to irc.dextroverse.org (6667)
-
-irc.dextroverse.org- *** Looking up your hostname...
-
-irc.dextroverse.org- *** Found your hostname
-

And nothing more. No MOTD, no further scripts, nothing. After a while it will time out (or something) and disconnect giving me this:

Quote:
* Connecting to irc.dextroverse.org (6667)
-
-irc.dextroverse.org- *** Looking up your hostname...
-
-irc.dextroverse.org- *** Found your hostname
-
* [10053] Software caused connection abort
-
* Disconnected
-
* Connect retry #1 irc.dextroverse.org (6667)
-
-irc.dextroverse.org- *** Looking up your hostname...
-
-irc.dextroverse.org- *** Found your hostname (cached)
-

I am currently in Antarctica and we must use the US Antarctic Program network for connection, but they're fairly liberal in the apps a person can use. All instant messaging works fine, internet isn't filtered, etc. so I can't figure out why IRC-based chat won't work. I was thinking maybe there was a way to run mIRC through a proxy if it is a USAP network issue?

Running Vista64 on a Toshiba laptop. Issues w/ IRC-based chat and Vista/Vista64?

I have a registered nick on the server, but haven't logged on in a while. These are the instructions for connecting to the server:

Quote:
- Be sure that Enable Identd server is checked
- User ID – Your Username (for me it’s Nitin)
- System – UNIX
- Port – 113
- Check Show IdentD requests
- Check Enable only when connecting


Anyone have any ideas?

Thanks in advance,

Aaron

Last edited by shinsain; 10/11/08 03:08 PM.
Joined: Sep 2008
Posts: 62
_
Babel fish
Offline
Babel fish
_
Joined: Sep 2008
Posts: 62
Quote:

Preface
Clients may report "socket-error: 10053, errornumber: 0x800CCC0F" regardless of client program used.

Cause
The winsock connection is being dropped by Windows itself due to malformed communication (i.e. tcp/ip packet size, forced timeout, etc).

Reason
Most probable cause is your antivirus program or your firewall, or anti-rootkit or anti-spyware software, interferring with the traffic to the remote system. The problems have been reported by systems running windows 95 all up to Vista (aka Windows 6).
Recent fixes can be available and we recommend that you search for the keyword: 10053 at the site of your antiviral vendor.

references: Microsoft KB, Symantec, McAfee, ZoneAlarm, Norton


1) If you have Antivirus software installed, disable it completely and try again

2) If you have firewall software installed, disable it completely and try again

3) If you have auto-tuning enabled, disable it and try again

To disable auto-tuning:

1. Click on the Vista start orb and type cmd
2. The search results will display a program named cmd.exe
3. Right-click on the link and select "Run as administrator"
4. After the command prompt window opens, type
"netsh interface tcp set global autotuning=disabled" without
the quotation marks, then press Enter.
5. Test connecting
6. If nothing changes, re-enable the autotuning feature by typing
"netsh interface tcp set global autotuning=normal"


Good luck and report back your findings!


Joined: Nov 2008
Posts: 2
S
Bowl of petunias
OP Offline
Bowl of petunias
S
Joined: Nov 2008
Posts: 2
I had already tried all that, to no avail.

As it turns out I installed SSL and connected to the server via SSL and it's fine now. I guess the USAP network wasn't as liberal as I thought.

Why they would block mIRC but not AIM, MSN, Yahoo Messenger, Skype, etc. I don't know? But the situation's resolved itself. Thanks for the tips!


Link Copied to Clipboard