Show changed Filetransfer-Port

[justincase]

Hi,

some time ago i think i changed the server-port for filetransfers somehow.
Is there a way to show the port via serverquery or so?

thank you

(im aware of that the standardport is 30033)

[numma_cway]

instanceinfo

[dante696]

Or the server log.

[justincase]

hmm.. i have this port:

serverinstance_filetransfer_port=25223

and port is forwarded properly but filetransfer does not work :-(
voice is doing fine.

regards

[numma_cway]

You know that's TCP?

[justincase]

Yes, forwarded both TCP and UDP

[dante696]

Yes, forwarded both TCP and UDP

This is wrong. Never open Both if you only need one.

Try another port if 25223 does not work for you. This is not a problem from the TeamSpeak server.

[justincase]

This is wrong. Never open Both if you only need one.

Try another port if 25223 does not work for you. This is not a problem from the TeamSpeak server.

True, this was only to avoid wrong information from the internet
and i now have a client in the network of the server, and it works ==> Network-Problem

But can i make a client-log somehow, to see why it fails?
Or does the filetransfer-port maybe need an additional (fixed?) port?

[dante696]

There is no real aditional information why it fails in the client.

Just something liek, rejected, could not read, timeout etc.
The real informations must be used from your OS or firewall / router.

[justincase]

I have additional information to this case.
All of this was based on a friends problem, who wasn't able to download files. (i was able to, cause i'm in the same network)

Now i tried it also connected from the internet, and for me it works great!
so there is no bad setting in firewall or somewhere else. everything is set up to work properly, but he still can't download files - voice works fine.
(so this issue changed to an client-based one)

can we find out somehow, how this issue is caused?

regards

[Chris]

unless you tested it from a device that is not connected to your router or network in any way, your test has a chance of being meaningless. Most routers will know that you try to reach something on the inside and thus directly pass you through, so you won't even have your data coming in from the internet. As such (depending on your modem / router / firewall) these may never get blocked or trigger any rules in the firewall since in effect they're internal connections.

If there are others outside your network that have working filetransfer on your server then it may be a problem with his setup, otherwise it's possibly still your firewall blocking things, or the server setup.

[justincase]

Yes i tested it from a completely other network connecting over the internet and it worked.

so it has to do with his setup anyhow.