Unable to connect through Dyndns-remote.com

[aikshutan]

Hi,

This is what I had encounter. I purchase a dns pro account from dyndns and registered a mirror url to point back my server public ip. I had no problem to ping my url (For eg: xxxxxx.dyndns-remote.com) through cmd ping command. But when i running the tnet standalone server.exe, and fill in the ip field with the url string (xxxxxx.dyndns-remote.com) provided in the sample scene, unfortunately it fail to connect. I had repeat the process by key in the public ip updated through dyndns updater.

Here is the info:
public ip / external ip reported through dyndns : 14.216.60.75
public ip / external ip reported through ping command line from cmd (windows) through the url string : 14.216.60.75

info from tnet server:
external : 192.168.1.101
internal : 192.168.1.101
gateway : 192.168.1.1

UDP lobby server started on port 5129
Game server started on port 5127
UPnP: unable to open udp port 5129
UPnP: unable to open tcp port 5127
UPnP: unable to open udp port 5128

Operating system : window 7
Unity version : 3.6.7

Everything work if i don connect through dyndns. (meaning tested on localhost and lans)
Many thanks if you could enlighten me on this.

Cheers,
Ignatius

[ArenMook]

External IP showing as 192.168.1.101 matching your internal means that TNet was not able to resolve it. The most common cause is trying to do it from the web player.

Quite a few routers also don't allow loopback addressing, like my Asus router for example. This means that connecting to yourself via 192.168.1.101 will work, but 14.216.60.75 won't. Easiest way to check is to navigate to http://14.216.60.75 -- if you see your router's page, then you won't be able to connect to yourself using the external IP.

Do a web-based port scan instead -- you will get a more accurate result. If the port is open on 14.216.60.75, then you know it works fine.

[aikshutan]

Hi ArenMook,

Thanks for the hint.
This is the result i receive through web base port scan: (http://www.t1shopper.com/tools/port-scan/)

Scanning ports on 14.216.24.37
14.216.24.37 isn't responding on port 5127 ().
14.216.24.37 isn't responding on port 5128 ().
14.216.24.37 isn't responding on port 5129 ().

But something strange happen to me this morning, the external value listed in tnet standalone server is reflecting as 14.216.24.37

I provided the screen shot for tnet standalone server and the unity menu scene.

By navigate to http://14.216.24.37, browser does not lead me to router page. In fact it return as operation time out.
Could you recommanded me a router brand? So that I could test with it. (As i not a technical guy, know nothing much on router. My experience with network is cap to PUN)
I m using TL-WR841N (TP-LINK)

Cheers,

[ArenMook]

The "unable to open" message tells you that UPnP is either not enabled, or is not present on the router, so TNet can't open the port. You have to open it yourself by logging into the router.

Just about any router bought these days supports UPnP, with the exception of Apple Failport.

[aikshutan]

Hi,

I had log in to my router and double check the port forwarding section. The Upnp is active. Here it the screen shot, unfortunately it is in chinese.
Currently Thunder program had utilise upnp, so the upnp is working for my router. I wonder do i need to kill all operation in upnp to ensure tnet is able to run?

Attach is the router screen shot.

[ArenMook]

Nah, there are different ways of communicating with UPnP devices, so I'm guessing your router is using an outdated method that TNet doesn't support but that other program does.

[aikshutan]

Could it be the ISP that blocking it?

[ArenMook]

Try this: http://www.softpedia.com/get/System/System-Miscellaneous/UPnP-Test.shtml

[aikshutan]

Thanks for the link:
TEST 1 - Operating System Support - PASSED
TEST 2 - SSDP Service Running Check - PASSED
TEST 3 - SSDP Service Automatic Check - FAILED
TEST 4 - UPnPHost Service Running Check - PASSED
TEST 5 - UPnPHost Service Automatic Check - PASSED
TEST 6 - UPnP Framework Firewall Exception Check - PASSED
TEST 7 - Adapter #0 - 192.168.1.101 - PASSED
TEST 8 - Get External IP Address (Result: 14.216.42.41) - PASSED

UPnP Test Program v1.16 Copyright Mark Gillespie 2010
Bugs/Comments to:  mark.gillespie@gmail.com
Please do not email me UPnP support requests. I will not answer them.

apparently only one fail, i had launch TnetServer on my laptop which connected through the same router (wireless), the weird thing happen is, both machine are sharing the same external ip. Guess that is the key reason why client unable to define which is the actual machine to connect with right?

[aikshutan]

For any previous post, i m hosting through my imac bootcamp (window 7), now i try it on my laptop (window , both external ip are same 14,216,42,41. I not running both server at same time. Connection through lan work perfectly.

[ArenMook]

The external IP is supposed to be shared. When you launch a TNet server and it opens up a port on your router via UPnP, all connections made via that external IP then go to the program correctly. This means if you have more than one TNet server running in your local network, only one of them will be receiving connections if you used the same ports.

That said, with everything but test 3 listed as "passed" I see no reason why TNet's UPnP shouldn't work for you -- which is odd. My results show less passed tests, for example:

1. TEST 1 - Operating System Support - PASSED
2. TEST 2 - SSDP Service Running Check - FAILED
3. TEST 3 - SSDP Service Automatic Check - FAILED
4. TEST 4 - UPnPHost Service Running Check - FAILED
5. TEST 5 - UPnPHost Service Automatic Check - FAILED
6. TEST 6 - UPnP Framework Firewall Exception Check - PASSED
7. TEST 7 - Adapter #0 - 192.168.1.248 - PASSED
8. TEST 8 - Get External IP Address (Result: XX.237.250.78) - PASSED
9.  
10. UPnP Test Program v1.16 Copyright Mark Gillespie 2010
11. Bugs/Comments to:  mark.gillespie@gmail.com
12. Please do not email me UPnP support requests. I will not answer them.

[aikshutan]

Hi,

Thanks for your great support! I had modify PortForwarding settings (all even some of them not making any sense to me LOL) to enforce open port for 5127,5128,5129. Now it work! Many thanks for guiding me so far!! (Tnet Standardlone Server still return those port is not open, but read one of your reply to other article about the mean of that is only saying Tnet not able to open up for you, so have to do it manually)

Cheers,
Ignatius