Sign in to follow this  
SuperFly

cluster works only LAN

Recommended Posts

Server 1 - 192.168.0.51

port 3724

 

Server 2 - 192.168.0.17

port 3725

 

Opened all necessary ports on router, forwarded 3724 and 3725 respectfully 

 

When someone on server 1 from outside world transfers, server 1 completes the transfer, the client hangs at connecting and I never see any login on server2, I can however transfer back and forth on LAN, these servers are on my local network, Im thinking this is a Internal/External IP address settings issue, have tried many combinations, suggestions please :)

 

Also, have tested these ports using a port check tool from outside world, I see the quieres hit the server 1 and server 2 so I am assuming there is not a router issue, this seems to be server to server issue, like the player isnt being passed across to the other server correctly.

 

I currently have assigned the NIC address to each server in internal and external fields and pointed each at the NIC address of opposite server.

 

Share this post


Link to post
Share on other sites

The IP addresses you listed are local IP's, they are not external IP's.  Nobody outside your local LAN can see those IP's.

If you can remote into one of the servers, open a browser there and search Google for "What is my IP".  This will show you what each server's external IP Address is.

 

Share this post


Link to post
Share on other sites
1 hour ago, Ricowan said:

The IP addresses you listed are local IP's, they are not external IP's.  Nobody outside your local LAN can see those IP's.

If you can remote into one of the servers, open a browser there and search Google for "What is my IP".  This will show you what each server's external IP Address is.

 

 

I guess this is where i get confused, both of these servers will show the same external IP address, on the public side of my router, this is whats reported when I go to whatismyip,   the world accessible ip address, all I have to identify each server is the internal ip address.  Keep in mind I am running 2 separate machines on my network behind a router.

Edited by SuperFly

Share this post


Link to post
Share on other sites

I did have the intention to try to get a cluster running on 2 different machines, but did not have ones that supported lastest java.

Just use the external IP and loop back on the neighbor server tab.

IIll expanded on this tonight.

Share this post


Link to post
Share on other sites
2 hours ago, bigsteve said:

I did have the intention to try to get a cluster running on 2 different machines, but did not have ones that supported lastest java.

Just use the external IP and loop back on the neighbor server tab.

IIll expanded on this tonight.

 

Looking forward to some help with this, would love to get both maps running.   Thanks...

Share this post


Link to post
Share on other sites

You must use the external IP in the external IP field for both servers. Your router should be set up to forward each port to the right machine.

 

In some OSes you will not be able to start the server if the external IP does not exist on the interface in the OS, if you run into that issue you can use my bind to all interfaces mod from here:

 

 

Here's an example setup from my cluster:

 

External ip on all servers = 46.4.83.199

 

Cradle - Login/Entry server - Internal IP = 10.5.0.2
  27016 - Steam Query (Forwarded from router, UDP)
  18000 - External port (Forwarded from router)
  18001 - Serverpacks (Forwarded from router, if you use that mod)
  18002 - Internal (Blocked on router)
  18003 - RMI (Blocked on router)
  18004 - RMI Registration (Blocked on router)


Otherland - Internal IP = 10.5.0.3 

  Steam query set 0 (disabled)
  18010 - External port (Forwarded from router)
  18011 - Serverpacks (Forwarded from router, if you use that mod)
  18012 - Internal (Blocked on router)

  18013 - RMI (Blocked on router)
  18014 - RMI Registration (Blocked on router)

  
Walden - Internal IP = 10.5.0.4 
  Steam query set 0 (disabled)
  18020 - External port (Forwarded from router)
  18021 - Serverpacks (Forwarded from router, if you use that mod)
  18022 - Internal (Blocked on router)

  18023 - RMI (Blocked on router)
  18024 - RMI Registration (Blocked on router)

 

  • Like 1

Share this post


Link to post
Share on other sites
6 hours ago, bdew said:

You must use the external IP in the external IP field for both servers. Your router should be set up to forward each port to the right machine.

 

In some OSes you will not be able to start the server if the external IP does not exist on the interface in the OS, if you run into that issue you can use my bind to all interfaces mod from here:

 

 

Here's an example setup from my cluster:

 

External ip on all servers = 46.4.83.199

 

Cradle - Login/Entry server - Internal IP = 10.5.0.2
  27016 - Steam Query (Forwarded from router, UDP)
  18000 - External port (Forwarded from router)
  18001 - Serverpacks (Forwarded from router, if you use that mod)
  18002 - Internal (Blocked on router)
  18003 - RMI (Blocked on router)
  18004 - RMI Registration (Blocked on router)


Otherland - Internal IP = 10.5.0.3 

  Steam query set 0 (disabled)
  18010 - External port (Forwarded from router)
  18011 - Serverpacks (Forwarded from router, if you use that mod)
  18012 - Internal (Blocked on router)

  18013 - RMI (Blocked on router)
  18014 - RMI Registration (Blocked on router)

  
Walden - Internal IP = 10.5.0.4 
  Steam query set 0 (disabled)
  18020 - External port (Forwarded from router)
  18021 - Serverpacks (Forwarded from router, if you use that mod)
  18022 - Internal (Blocked on router)

  18023 - RMI (Blocked on router)
  18024 - RMI Registration (Blocked on router)

 

 

 

 

Not sure if this worked will have to have someone test externaly in the morning but it loads the server with your binds mod running, before i was getting a bind error when external address were in the external field.  Will update.  Thanks for the help.

 

Share this post


Link to post
Share on other sites
On 3/22/2017 at 3:59 PM, bdew said:

You must use the external IP in the external IP field for both servers. Your router should be set up to forward each port to the right machine.

 

In some OSes you will not be able to start the server if the external IP does not exist on the interface in the OS, if you run into that issue you can use my bind to all interfaces mod from here:

 

 

Here's an example setup from my cluster:

 

External ip on all servers = 46.4.83.199

 

Cradle - Login/Entry server - Internal IP = 10.5.0.2
  27016 - Steam Query (Forwarded from router, UDP)
  18000 - External port (Forwarded from router)
  18001 - Serverpacks (Forwarded from router, if you use that mod)
  18002 - Internal (Blocked on router)
  18003 - RMI (Blocked on router)
  18004 - RMI Registration (Blocked on router)


Otherland - Internal IP = 10.5.0.3 

  Steam query set 0 (disabled)
  18010 - External port (Forwarded from router)
  18011 - Serverpacks (Forwarded from router, if you use that mod)
  18012 - Internal (Blocked on router)

  18013 - RMI (Blocked on router)
  18014 - RMI Registration (Blocked on router)

  
Walden - Internal IP = 10.5.0.4 
  Steam query set 0 (disabled)
  18020 - External port (Forwarded from router)
  18021 - Serverpacks (Forwarded from router, if you use that mod)
  18022 - Internal (Blocked on router)

  18023 - RMI (Blocked on router)
  18024 - RMI Registration (Blocked on router)

 

 

 

Worked like a charm...  Thank you!!!!!!!!

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this