Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Foxorz

Registered:
Posts: 4
Reply with quote  #1 

Hello everyone.

I have looked through this forum and there were similar problems to mine, but not quite.

I have followed the procedure laid out by LawsonThompson, and the port seems to be open to the internet when trying.

Me and my wife played the game at home, and loved it. We thought to invite a couple of friends to play over the internet. All 4 copies were bought through steam. We are all playing on Windows.

As it may be obvious, my friends cannot connect to my server. 

I have even put my computer on DMZ at my router and asked my friends to turn off their windows firewalls. 

Any other ideas I could try?

NoseyNick

Avatar / Picture

Registered:
Posts: 112
Reply with quote  #2 
Not clear exactly which "procedure laid out by LawsonThompson" you're referring to, but summarising from my own experience:

You'll run the server on one of your machines. The server screen will probably tell you its INTERNAL IP, likely 10.x.x.x, 192.168.x.x or 172.x.x.x?

You'll make sure any Windows/OS/3rd-party firewall on that server allows inbound TCP port 2010.

You can test from other machines on the same LAN, they should be able to connect and play? They will continue to connect to this INTERNAL IP.

On your router you'll configure a port-forward, to forward EXTERNAL TCP 2010 to INTERNAL [server address above] 2010

To complicate things: If you have any other routers "daisy-chained", you'll need to have done the above for the "most internal" one first, then find the EXTERNAL IP of that first router, and get the SECOND router to forward ITS external TCP 2010 to the first router's external 2010

Finally you'll need to know the external IP of your outer-most router (hopefully only one router?). Your router might tell you on a status page, BUT if it's another 10.x.x.x, 192.168.x.x or 172.x.x.x one it strongly implies there's another firewall somewhere beyond, like your ISP runs a big "carrier-grade firewall/NAT", where you probably can't configure port-forwards. Unfortunately this is fairly common, especially on Cable, less so but still happens on DSL.   [frown]

If your (one and olny?) router doesn't tell you its external IP, good chance you can find this by browsing to https://icanhazip.com/ - and THIS is the address you'll share for other people over the internet to connect to (not the internal 10.x.x.x, 192.168.x.x or 172.x.x.x one).

Bear in mind you're assuming NONE OF THE ABOVE CHANGE. If your server machine has changed IP between tests (did you reboot / power-cycle something?) then you'll need to fix the port-forward. If your external icanhazip.com address has changed (Did you reboot the router, or go offline for some other reason?), you'll need to inform your internet players.

To reiterate: Your internal LAN players will still connect to the INTERNAL 10.x.x.x, 192.168.x.x or 172.x.x.x address. Your external / Internet players will connect to your external / icanhazip.com IP address via your port-forward(s).

If it still doesn't work, it's possible your ISP is filtering / firewalling inbound connections on a GCFW/CGN as above, in which case you're pretty much doomed I'm afraid.

Anyone who tells you you need UDP 2010, or any other ports, is misinformed, misled, lying, or trying to expose other services (do you wanna run TeamSpeak too for example?) or possibly even trying to hack you.  [rofl]   There's other UDP stuff happens on the LAN ONLY for the auto-discovery, but that ain't gonna work over the interwebs no matter how hard you try. TCP 2010 inbound is the only one that matters for Artemis.

Hope that helps!
NoseyNick
Foxorz

Registered:
Posts: 4
Reply with quote  #3 
Quote:
Originally Posted by NoseyNick
Not clear exactly which "procedure laid out by LawsonThompson" you're referring to, but summarising from my own experience:

You'll run the server on one of your machines. The server screen will probably tell you its INTERNAL IP, likely 10.x.x.x, 192.168.x.x or 172.x.x.x?

You'll make sure any Windows/OS/3rd-party firewall on that server allows inbound TCP port 2010.

You can test from other machines on the same LAN, they should be able to connect and play? They will continue to connect to this INTERNAL IP.

On your router you'll configure a port-forward, to forward EXTERNAL TCP 2010 to INTERNAL [server address above] 2010

To complicate things: If you have any other routers "daisy-chained", you'll need to have done the above for the "most internal" one first, then find the EXTERNAL IP of that first router, and get the SECOND router to forward ITS external TCP 2010 to the first router's external 2010

Finally you'll need to know the external IP of your outer-most router (hopefully only one router?). Your router might tell you on a status page, BUT if it's another 10.x.x.x, 192.168.x.x or 172.x.x.x one it strongly implies there's another firewall somewhere beyond, like your ISP runs a big "carrier-grade firewall/NAT", where you probably can't configure port-forwards. Unfortunately this is fairly common, especially on Cable, less so but still happens on DSL.   [frown]

If your (one and olny?) router doesn't tell you its external IP, good chance you can find this by browsing to https://icanhazip.com/ - and THIS is the address you'll share for other people over the internet to connect to (not the internal 10.x.x.x, 192.168.x.x or 172.x.x.x one).

Bear in mind you're assuming NONE OF THE ABOVE CHANGE. If your server machine has changed IP between tests (did you reboot / power-cycle something?) then you'll need to fix the port-forward. If your external icanhazip.com address has changed (Did you reboot the router, or go offline for some other reason?), you'll need to inform your internet players.

To reiterate: Your internal LAN players will still connect to the INTERNAL 10.x.x.x, 192.168.x.x or 172.x.x.x address. Your external / Internet players will connect to your external / icanhazip.com IP address via your port-forward(s).

If it still doesn't work, it's possible your ISP is filtering / firewalling inbound connections on a GCFW/CGN as above, in which case you're pretty much doomed I'm afraid.

Anyone who tells you you need UDP 2010, or any other ports, is misinformed, misled, lying, or trying to expose other services (do you wanna run TeamSpeak too for example?) or possibly even trying to hack you.  [rofl]   There's other UDP stuff happens on the LAN ONLY for the auto-discovery, but that ain't gonna work over the interwebs no matter how hard you try. TCP 2010 inbound is the only one that matters for Artemis.

Hope that helps!
NoseyNick


Hi Nick!

 

Thanks for the reply.

The procedure I was mentioning was from this thread and video, by Lawson Thompson.

https://artemis.forumchitchat.com/post/port-forwarding-howto-video-7211028?highlight=port+forwarding&pid=1285447046

I have my server setup. It does show it's LAN IP. I can connect my second computer to it, via LAN.

Port Forwarding is set up on my only router. External to internal TPC 2010.

I always check what my external IP is before sending the address to my friends to try to connect to my server. UDP is not being port forwarded.

When trying to play the game with friends, I have my PC on DMZ by the router and Windows firewall down.

I hope it isn't my ISP...

NoseyNick

Avatar / Picture

Registered:
Posts: 112
Reply with quote  #4 
Quote:
this thread and video


Oooh neat, using an external service to test your port 2010 from the outside too!

Does your router's idea of its "external IP" agree with https://icanhazip.com/ ?

If so, it's probably "on the internet" fine, and you "only" need to get the port-forward to work properly.

If they disagree, then there's probably another NAT / GCN in between you and the interwebs, owned by your ISP, and you're REALLY unlikely to be able to add a port-forward to THAT.   [frown]
Simoof

Registered:
Posts: 1
Reply with quote  #5 

Hi there,
I had a similar issue:

I had my port open but my firewall on my Artemis server pc blocked initially. Adding an exclusion in and out to my firewall resolved for me.

Maybe your friends have firewalls running that need to allow the port/app through too?

 

 

Foxorz

Registered:
Posts: 4
Reply with quote  #6 

Quote:
Originally Posted by NoseyNick


Oooh neat, using an external service to test your port 2010 from the outside too!

Does your router's idea of its "external IP" agree with https://icanhazip.com/ ?

If so, it's probably "on the internet" fine, and you "only" need to get the port-forward to work properly.

If they disagree, then there's probably another NAT / GCN in between you and the interwebs, owned by your ISP, and you're REALLY unlikely to be able to add a port-forward to THAT.   [frown]


Well, my router's IPv4 agrees on the external IP with other websites.

But it does not agree on the IPv6 with these sites, including icanhazip.com.

[frown]

 

Oh well. I guess I can try to set up a server on the cloud?

Foxorz

Registered:
Posts: 4
Reply with quote  #7 
Quote:
Originally Posted by Simoof

Hi there,
I had a similar issue:

I had my port open but my firewall on my Artemis server pc blocked initially. Adding an exclusion in and out to my firewall resolved for me.

Maybe your friends have firewalls running that need to allow the port/app through too?

 

 



Hi, thank you for your reply.

We had all firewalls off for the testing of the connection. Both on my computer and on theirs. :/

NoseyNick

Avatar / Picture

Registered:
Posts: 112
Reply with quote  #8 
IPv6 shouldn't matter for Artemis, I'm about 95% certain it's IPv4 only.
Hmmm... bug report?   [wink]

If you want a cloud server, my nerdy instructions can be found at http://noseynick.org/artemis/nebula/
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.