LAN servers are server with one of the following IPs:
127.0.0.1
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
and they can pop-up multiple times as well!
often it show up as 1 LAN server with the following IP: 127.0.0.1.
sometime you'll also get another with the IP you have inside your LAN.
So that's nothing to worry about!
"masterserver.savage.s2games.com revolved to 216.127.51.199
Couldn't connect to tcp port 11236 on 0 to request a firewall test"
In the past savage servers got tested by the masterserver! The masterserver would try to connect to the remote admin system of the savage server and trigger a response to make the savage server send heartbeats. This system does no longer work so you'll get those lines in your console.
So that's nothing to worry about!
So why doesn't it work...?! well, that's usually hard to tell.
It could be that one of the/your firewalls is blocking the UDP/TCP packets on port 11235.
It could be that your router does not forward traffic from port 11235 to port 11235 of your PC.
It could be that your ISP for whatever reason prevents you from hosting a public server!
The one thing i can help with is the following:
http://www.newerth.com/?id=serverlist&details=your IP:Port
will show your server name/info when it all works. If it shows blank("Players: /") your UDP packets are getting blocked somewhere and your server cannot be reached!