Server Support

[kvgeorge1]

I wanted to host a dedicated server and also be able to play against it on the same LAN that I have the server on.  When I startup the server, everything appears fine and the server is listed in the server list when I go online.  However, any client connecting to the server gets a UE immediately upon connection.  However, if I stop the server and run it as a LAN server (-nologin), then the users on my LAN can use the server with no issues, but as expected, will not show-up in the server list on Tribes Next.

Any suggestions?

[Krash]

Users within a network cannot join using the server's external address.  You can hit your 'Insert' key in the list to manually add the LAN address to your listing, and click in the 'Favorite' column to save it to you list.

[kvgeorge1]

So,  if I want users to play online that are on my local network, they will have to connect as described (pressing INSERT and connecting directly to the IP address), but outside users will be able to connect via the Master Servers?

[Krash]

Yes, that sounds about right. If the server is displaying on the list and the server was able to retrieve its own address, outside users shouldn't have any trouble connecting. 
The error you described wherein LAN connections cause the client to crash is a known issue that generally occurs when attempting to connect (usually multiple times in succession) to the external address from a local connection.  It's basically just a glitch on the client end caused by a quick server disconnection following an IP sanity check failure due to the server and client reporting mismatching addresses.


Alternatively to inserting the IP, local users could open up the console(~) and enter: 'queryLanServers(28000);' - where 28000 is your server's port.  This query is normally run on refresh, but was accidentally transposed for a similar function in the current version of the patch.