Quake 4 server help...

Post by **signal** » Tue Nov 15, 2005 3:28 am

Hey all!

I'm having some problems starting a dedicated q4 server. I used the sample cfg that is stickied in this forum, put it in my q4base folder, set up the command line properly, and i get this message in the console:

...initializing QAL
...calling LoadLibrary( 'OpenAL32.dll' ): failed
couldn't exec server.cfg
WARNING: idSession: triggering mainmenu watchdog

Is that a problem? Also, is the IP of the machine the address I give out if I want my friends to connect? Sorry for the dumb questions, never ran a server before. Any help would be greatly appreciated. Thanks!

Post by **DooMer** » Tue Nov 15, 2005 3:37 am

Couldn't exec server.cfg looks like a problem. You made the server.cfg file in q4base right?

The IP address you give out has to be your public WAN address, not necessarily your machine's address since it could be a private LAN IP if you're behind a router. http://www.whatismyip.com

Post by **signal** » Tue Nov 15, 2005 3:40 am

Yup. I put it right in the q4base folder.

Post by **signal** » Tue Nov 15, 2005 3:43 am

Funny thing, I'm doing this on my girlfriends machine. When I try the exact same steps on MY machine, it works fine! Hmmm...

Post by **signal** » Tue Nov 15, 2005 3:46 am

Yeah, I even try typing in "exec server.cfg" in the console window and it still won't work, even though the server.cfg is right in q4base! Man, this sucks...

Post by **DooMer** » Tue Nov 15, 2005 3:50 am

Try going to Tools > folder options > view, and uncheck hide extensions for known files types. Maybe it's named server.cfg.txt or something and windows is hiding that extension. It must be something simple.

Post by **signal** » Tue Nov 15, 2005 3:52 am

Hahaha. That was it. Thank you so much! I'm a moron :icon25:

Post by **signal** » Tue Nov 15, 2005 3:55 am

haha, now another problem. I found my WAN ip, but when i try to connect to it from my other machine, it won't go. any idea why? i used default port of 28005.

Post by **Hex** » Tue Nov 15, 2005 4:10 am

28004

Post by **signal** » Tue Nov 15, 2005 4:12 am

still wont work

Post by **signal** » Tue Nov 15, 2005 4:16 am

ok. i think my linksys router is messing things up. i tried to go in and forward the ports but i don't think i did it right. i specified the range for 1 to 28005. for the ip, i put the WAN IP of the machine. any thoughts? still won't go even after i did this.

Post by **DooMer** » Tue Nov 15, 2005 4:19 am

I think you want to forward the ports for your LAN IP, not the WAN IP. 192.168.1.xxx

Post by **signal** » Tue Nov 15, 2005 4:25 am

I tried that. it asks for the start and end range, i did 28000 to 28005. then it asks for protocol, and i set it on "both". for ip address, i put the LAN ip of the machine. then i enabled it, did a release/renew on the router, and then still nothing. ugh... why does this have to be so difficult.

Post by **DooMer** » Tue Nov 15, 2005 4:41 am

On my linksys, port forwarding never seems to work. I have my game servers, or any server that I want outsiders to connect to, set up on the DMZ. When you set up a PC on the DMZ, it's completely exposed to the internet without any protection. The good thing is you dont have to fuck around with port forwarding, the bad thing is people could ruin your shit. Might be a good idea to turn it off when you're done with it.

To do this, plug your server into the DMZ port on the router. Connect to the router, go to Advanced > DMZ Host. enable it, then click specify IP behind the DMZ port. Put in an IP puch as 192.168.1.99. Then Go to your connection properties of your server and set up the IP address as 192.168.1.99, subnet 255.255.255.0, default gateway 192.168.1.1. Also click "Use the following DNS server addresses", and fill those in. To find your DNS addresses, connect back into your router, click Setup > Status, and put those DNS Servers in listed under WAN. This enables the DMZ and makes a static IP on your server instead of using DHCP.

Post by **Hex** » Tue Nov 15, 2005 4:42 am

If your server is on the same LAN, then bypass the linksys entirely and just connect directly to the LAN ip...

?