Hi Guys
I had the same issue with server status pages not working -
more specifically the UDP listener from nwserver would never bind to a port = therefore there was no UDP listener to respond to the server status request.
http://www.iscandar....&template=black
My own server which is appearing correctly was able to get it resolved by making a hosts change
(Someone on the forums told me to change it to a valid ip)
# Copyright © 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
8.8.8.8 nwn.master.gamespy.com
8.8.8.8 is googles dns server ip - and I think it is guaranteed to be up 24/7
It seems that if nwn.master.gamespy.com is not connected to within X duration, the UDP listener just gives up, and ends up not being setup on nwserver start up.
If however you fool it into going to a valid IP address, it will bind and listen appropriately to UDP Requests.