Tasharen Entertainment Forum
Support => TNet 3 Support => Topic started by: djray2k on April 26, 2016, 07:02:01 PM
-
Hi. I'm trying to get the TNServer.exe running in a virtual machine using Azure. I used to use Amazon EC2 cloud a while ago, but I figure I might as well use Azure since I get a free membership from my job.
So far I just have the executable running like below. IP is colored out for safety.
(http://i.imgur.com/pS5uQm6.png)
When I try to connect from my game it fails to connect to the external IP in red. I can connect locally when I run TNServer on my own machine.
Is there a step I'm missing?
Edit: Here's my ports I opened, but still nothing. The other two are the same with 28 and 29 as UDP. I also allowed it through the Windows Firewall in the VM.
(http://i.imgur.com/MzPDlx4.png)
-
I don't have experience with Azure, so can't suggest much -- but you really shouldn't be running UDP discovery (5129) on a remote server. Nor UDP (5128) for that matter. I'd suggest sticking to just 5127.
-
Thanks, I'll take those out asap.
You're familiar with Amazon EC2's. Do you have a guide for that? I can try to translate it into Azure.
-
From what I remember, Amazon was very straightforward. I just had to open ports via their website, and the virtual OS needed to allow the same port through, and it worked fine.
-
Thanks! I figured something out similar to what I did when I used amazon.
But now the only way it will work is if I open all the TCP ports. When I try to do a specific range (like 5127-5129) it won't work, but once I open all of them it's good again.
I assume that's not good practice, and wondering how I could fix it?
-
I think that would be more of a question for Azure. TNet just needs 1 port (5127 in your case). On Amazon I only open the ports I need, keeping the rest closed. I even keep the remote desktop port closed to everyone except my IP for extra security.