Can't connect to servers after new router firmware
I recently upgraded my router firmware (some weird Hawking router) and everything seemed fine. All apps and games seems to be able to connect to their servers without a problem but Half Life 1 is acting up.
It can get server lists and server info as usual but it tries to connect to the server 2-3 times before telling me that it couldn't establish network connection. I can create my own servers as usual.
Everything in the router is set to "allow all" and there are nothing I could find that could be blocking hl1.
Also my firewall has everything about hl1 set to "allow".
What could be wrong?
I searched for answers on this topic but couldn't find anything about it :-/
It can get server lists and server info as usual but it tries to connect to the server 2-3 times before telling me that it couldn't establish network connection. I can create my own servers as usual.
Everything in the router is set to "allow all" and there are nothing I could find that could be blocking hl1.
Also my firewall has everything about hl1 set to "allow".
What could be wrong?
I searched for answers on this topic but couldn't find anything about it :-/
Comments
Something odd I just noticed is that NS beta 2.1 doesn't connect but the public version works fine. :S
I don't remember changing any settings since i played last time so what could be wrong in that case?
I don't have any usersettings cfg file.
* i meant a userconfig.cfg file
I sorely hope you mean 3.2...
I have NS regular installed in:
C:\Games\Steam\SteamApps\xxxxxxxxx\half-life\ns\
and NS beta in:
C:\Games\Steam\SteamApps\xxxxxxxxx\half-life\nsp\
My best guess is that it is some configuration error but I haven't messed much around in the hl config files before because I had no need to.
But I thought the 27015 port had to be open, or something similar.
I compared the config files and there were no big differences other than theese:
gl_polyoffset "0.1" was "-0.001" in beta
cl_cmdrate "40" was "30" in beta
cl_updaterate "40" was "20" in beta
I don't think they have anything to do with it though <img src="style_emoticons/<#EMO_DIR#>/sad-fix.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad-fix.gif" />
<a href="http://216.104.71.5/english/routers/port_forwarding/Hawking/H2BR4/Steam_Client.htm" target="_blank">http://216.104.71.5/english/routers/port_f...team_Client.htm</a>
Also the router doesn't seem to support port forwarding properly, only those virtual servers (what is the difference anyway since it works just like port forwarding)
The recent firmware upgrade actually made my web-config page of my router look *really* crappy where it before looked like on the page (almost) you linked to.
What a crappy router <img src="style_emoticons/<#EMO_DIR#>/sad-fix.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad-fix.gif" />
Also port forwarding is the same thing as virtual servers. It's just a different name for the same feature.
Here's the golden rule with router firmware. If it's working perfectly then don't upgrade firmware.
Your problem doesn't sound firmware related though. Since all HL1 mods use the same hl.exe and you say that ns 3.1 works fine then you know it's not a router issue at least.