Forums Bug Reports cannot change default DCC Server port 59

Hi all!
I would definitely like to change the default port 59 of the DCC server
to something else.
Whatever number I am trying mIRC isn't going to react if I try to connect via dcc from outside.
Port 59 works though!
I am using manual portforwarding on a FrtizBox 7490 as well as upnp
in the router and on Win7 Pro.
mIRC 7.38

Try from mIRC : alt+o -> DCC -> Server -> and change the Listen on Port: box , also have a look if DCC is enabled .

Thanks westor for your quickply! :-)
Unfortunately this seems not to be a problem of mIRC settings!
I already changed the settings a lot :-)
On the other hand it's not a NAT problem too - the portforwarding,
of my FritzBox 90 works.
Anyway I must say that everything with DCCdccrks nicely,
only that I cannot successfully change the DCC server port.
The machine I'm testing it with is in the same LAN and always tries
to connect to port 59.
Even if I use something like: /dcc fserve ip-adress:notthedefaultport

I actually feel like it's a mIRC bug:
Found some post where someone is using a script to be able
to change the port - too difficult for me more...

I have just tested this feature on three different computers, under XP, 7, and 8.1, on two different routers, both with and without UPnP, and it worked fine in all of the combinations that I tried. Please note that this feature has been unchanged in at least ten years and as far as I know has always worked correctly.

There is very little that can go wrong with this feature since all mIRC is doing is listening on the port number that you specify in the server dialog. If it is not working for you, the most likely reason is that you are using anti-virus/security software that is blocking unrecognized ports, your router is blocking the port or has not been configured correctly, or quite possibly that your internet provider is blocking the port for some reason.

Thanks Khaled for trying and replying your results to me!
Now I feel very sure that it should be possible, for me too, to make it work!

I was able to forward the ports under Connect->Options->Ports -
then I shall be able to successfully forward the rest.

Maybe rebooting the client or the router ...

Funny was that I found out, after all manual port forwarding,
that the Windows Upnp-service wasn't running on my machine ...
Don't remember that I stopped it.

I'll report any success or failure.

I try to connect to a mIRC server which is located in the same LAN
behind the NAT of a FritzBox 7490.

After changeing the DCC server listen port
(Options->DCC->Server->Listen on Port) in the CLIENT
to the SAME port as actually the server is listening to,
I'm getting these results:

a) /dcc fserve URL:port
result: nothing happens!

b/works!) /dcc fserve URL
result: I'm getting the 'File Server Warning'
popup window on the server side - after clicking 'OK' the connection is working!
On the client I can read this line:
Client: URL (Port I defined in the client's settings!)

c/works!) /dcc URL port
result: same as b)! - connection works!
No change if I use a DIFFERENT port here!
It really looks as if the mIRC client is using the port that has been defined
as it's DCC server port, even if that server ISN'T enabled.

As I cannot test it with a client outside of my LAN I'm curious
if the behaviour is to be expected the same...

Ah, btw.: Is mIRC capable of SDCC connections?
And if not are there any plans to implement it?

You are right, there is an issue with how ports are being parsed. By design, when mIRC does not see a "port" specified after the address, it uses the DCC server port by default. What is happening is that the port number specified after the address is not being parsed correctly, so it uses the default DCC server port. It looks like this happened around the time IPv6 support was added, which required extra parsing to determine the address format but broke the port parsing. Thanks for looking into it. This issue has been fixed for the next version.

I'm glad this helped