reconnect causes all open network windows to connect to the same one (quite possibly ZNC unrelated) #574

New Issue

2026-10-05T04:30:53+02:00

adam commented

2026-10-05 04:30:53 +02:00

As per the title it most likely is caused by mirc and not znc but this way I can be sure it's not znc.

So when my router changes IP the loss of connectivity, almost always on reconnect, has all open windows (a window == individual network) connect to the same znc network, so I end up with multiples of the same network / channels.

As far as I see it mirc gets confused and connects on all with the default selected network instead of trying to reconnect to each individual different network.

Any chance this can be caused by znc as well? If it's certain it's not znc then I can take this over to mirc forums.

Cheers

As per the title it most likely is caused by mirc and not znc but this way I can be sure it's not znc. So when my router changes IP the loss of connectivity, almost always on reconnect, has all open windows (a window == individual network) connect to the same znc network, so I end up with multiples of the same network / channels. As far as I see it mirc gets confused and connects on all with the default selected network instead of trying to reconnect to each individual different network. Any chance this can be caused by znc as well? If it's certain it's not znc then I can take this over to mirc forums. Cheers

adam closed this issue

2026-10-05 04:30:53 +02:00

adam commented

2026-10-05 04:30:54 +02:00

/msg *status loadmod disconkick

In the master branch the disconkick module has been merged to core, because Pidgin also suffered this issue.

I believe this can be closed.

`/msg *status loadmod disconkick` In the master branch the disconkick module has been merged to core, because Pidgin also suffered this issue. I believe this can be closed.

adam commented

2026-10-05 04:30:55 +02:00

The Pidgin issue was https://github.com/znc/znc/issues/968 and this could well be duplicate of it. I am surprised that no other mIRC user has reported this as it's so popular or maybe those users just have loaded the disconkick module.

The Pidgin issue was https://github.com/znc/znc/issues/968 and this could well be duplicate of it. I am surprised that no other mIRC user has reported this as it's so popular or maybe those users just have loaded the disconkick module.

adam commented

2026-10-05 04:30:56 +02:00

Make sure to specify the network either in username (username/network) or password (username/network:password), so that ZNC knows which network you are connecting to.

Make sure to specify the network either in username (`username/network`) or password (`username/network:password`), so that ZNC knows which network you are connecting to.

adam commented

2026-10-05 04:30:57 +02:00

As far as your mIRC issue, sounds like this. http://forums.mirc.com/ubbthreads.php/topics/244084/Re:_Connect_to_networks

As far as your mIRC issue, sounds like this. http://forums.mirc.com/ubbthreads.php/topics/244084/Re:_Connect_to_networks

adam commented

2026-10-05 04:30:57 +02:00

@jpnurmi I use username/network:password but that doesn't help since after the 1st network which works on start of mirc rest are opened by a script.

@Mikaela it's the client disconnecting from ZNC due to IP change, not ZNC disconnecting from the IRCd

@KindOne- cheers one of your solution seems like the solution I have to try :P Atm I use the native on start up and rest networks are created by a remote script. As such a default network is selected for the first network.

Will use the on:start to have all of them and if needed I will remove the servers.ini

@jpnurmi I use `username/network:password` but that doesn't help since after the 1st network which works on start of mirc rest are opened by a script. @Mikaela it's the client disconnecting from ZNC due to IP change, not ZNC disconnecting from the IRCd @KindOne- cheers one of your solution seems like the solution I have to try :P Atm I use the native on start up and rest networks are created by a remote script. As such a default network is selected for the first network. Will use the on:start to have all of them and if needed I will remove the servers.ini

adam commented

2026-10-05 04:30:58 +02:00

In that case this is fully mIRC bug and there is nothing ZNC could do. You also appear to be going against the ZNC wiki instructions for mIRC.

In that case this is fully mIRC bug and there is nothing ZNC could do. You also appear to be going against the [ZNC wiki instructions for mIRC.](http://wiki.znc.in/MIRC)

adam commented

2026-10-05 04:30:59 +02:00

That is very much true, I never saw that article, which includes KindOne's solution.
I just implemented it on my client and everything looks dandy, will have to wait for that next IP change sponsored as always by my ISP.
Thank you all for your swift & helpfull replies.

Should I close this or wait till I have "verified" it works as intended?

That is very much true, I never saw that article, which includes KindOne's solution. I just implemented it on my client and everything looks dandy, will have to wait for that next IP change sponsored as always by my ISP. Thank you all for your swift & helpfull replies. Should I close this or wait till I have "verified" it works as intended?

adam commented

2026-10-05 04:31:00 +02:00

I think you can close this, because

this is not a ZNC issue.
there are so many mIRC users that they would have said if the wiki instructions don't work.

I think you can close this, because 1. this is not a ZNC issue. 2. there are so many mIRC users that they would have said if the wiki instructions don't work.

adam commented

2026-10-05 04:31:00 +02:00

Yea 2 is quite a valid point :)

Yea 2 is quite a valid point :)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#574