Unfortunately at this time we are unable to disable NAT with the LTE service.

Alternatively your new LTE has private IPs and NAT enabled that may be causing some issues. 'Potentially there may be an issue if you are using IRC for downloading or running a file server with our traffic management policies.

A VPN allows you to make secure connections that your internet provider cannot interfere with. You will need to 1) contact your internet provider, and 2) try connecting through a VPN. The only way to rule out your internet provider as the cause is to follow the advice that I provided in my previous email. If mIRC sends a ping and you see 10053, this means that your connection had already failed and mIRC detected it. MIRC sends pings specifically to detect whether your connection has failed. All IRC clients identify themselves in some way, whether it is with the VERSION reply, or other variations in the way they use the protocol. MIRC is the most widely used IRC client, so internet providers will almost always check for connections that look like 'mIRC'. If the issue only started after you upgraded your internet connection, and nothing else changed on your computer, and you are using the same exact mIRC installation as before, the most likely reason is that your internet provider is checking for IRC connections on your new line and is disconnecting them. Installing/running 6.35 in a separate directory also has the same issue. I've never used a VPN, so I have no idea what to tell you about that.ĮDIT: I recently tried downgrading to 7.29, and also doing a portable install of 7.43 and running it directly from the.

Could that be it? And if so, why is this suddenly an issue now? This is literally the second question I've ever asked in this forum - the first was in 2009. Went into the options and unhid the ping/pong event, and it looks like Mirc manages two pings on an otherwise idle connection before it dies. Letting it idle now to see if it dumps, based on past behaviour it should ping out in 121 seconds. Something else I've just learned, actually, is that as long as I'm 'talking' constantly, the connection stays live. The problem seems clearly to be something specific to Mirc - could it be 'identifying' itself differently and triggering something? What I've actually discovered is that I have no problems staying connected with another IRC client.

Mirc 7.43 exe replacement