Tasharen Entertainment Forum
Support => TNet 3 Support => Topic started by: biyarjomandi on June 14, 2016, 02:30:18 AM
-
hi Tnserver.exe does not open ports (i turned off firewall on my PC) and shows this :
No arguments specified, assuming default values.
In the future you can specify your own ports like so:
Local IPs: 1
1: 192.168.1.25 (Primary)
[2016/06/14 11:49:56] Checking UPnP status on 192.168.1.25...
[2016/06/14 11:49:58] UPnP.WaitForThreads() took too long -- aborting.
[2016/06/14 11:49:58] External IP: 217.219.180.112
[2016/06/14 11:49:58] UDP Lobby Server started on port 5129 using interface 0.0.
0.0
[2016/06/14 11:49:58] Admins: 0
[2016/06/14 11:49:58] Bans: 0
[2016/06/14 11:49:58] Game server started on port 5127 using protocol version 20
160207
[2016/06/14 11:49:58] Loaded server.dat
[2016/06/14 11:50:00] UPnP.WaitForThreads() took too long -- aborting.
[2016/06/14 11:50:00] Press 'q' followed by ENTER when you want to quit.
[2016/06/14 11:50:01] UPnP Gateway: Not found
[2016/06/14 11:50:01] UPnP: Unable to open UDP port 5128
[2016/06/14 11:50:01] UPnP: Unable to open UDP port 5129
[2016/06/14 11:50:01] UPnP: Unable to open TCP port 5127
---------------------------------------------------
And when i try to shut it down it crashes..!
-
It happens sometimes for me too but it resolves if i restart my router.
-
It happens sometimes for me too but it resolves if i restart my router.
no this is not the answer...! did not worked.i run it local to test and what router do u mean ?
-
no this is not the answer...! did not worked.i run it local to test and what router do u mean ?
I restarted the Wifi Router to fix it but does not happen to me always. May be some else can tell what is wrong.
-
TNet can only open ports if UPnP is accessible. If the router doesn't support it, or if there is no router, then the ports can't be opened. If the router doesn't support UPnP, you will need to forward ports manually. If there is no router, then you don't need to do anything. Since you mention that you turned off the firewall, it sounds like you don't need to worry about it.
The crashing was resolved with 3.0.2b. It wasn't a crash per say, just an uncaught exception that was only showing up on non-Windows platforms.
-
TNet can only open ports if UPnP is accessible. If the router doesn't support it, or if there is no router, then the ports can't be opened. If the router doesn't support UPnP, you will need to forward ports manually. If there is no router, then you don't need to do anything. Since you mention that you turned off the firewall, it sounds like you don't need to worry about it.
The crashing was resolved with 3.0.2b. It wasn't a crash per say, just an uncaught exception that was only showing up on non-Windows platforms.
Thanx but what can i do now ? i am using my pc that is connected to my Office LAN and my laptop that has no connectin (no internet and no other network) but i still have the problem . my windows is 7 and i have enabled network discovery that i think enables UPNP .
-
Laptop that has no connection? I am not sure what you expect to happen there... TNet can be used in offline mode, but anything related to establishing a live connection will obviously fail if you try to use it on a PC that has no network connection.
I don't quite understand your question "what can I do now". In regards to what? Your original question was about TNet not opening ports, and I explained that this is fine, and ports can't always be opened. You would get that line of text when launching the server on Amazon EC2 for example.