I got my pure server to run BEHIND a router!
Credit for this goes to rhugg and to google which enabled me to find it and this board :) -- see his original post. This is true on WinXP SP2. All you need to do is edit your hosts file (inside C:\windows\system32\drivers\etc) and add this line under the 127.0.0.1 line:
Code:
xxx.xxx.xxx.xxx PCNAME EDIT - I added this info to the wiki page |
Confirmed as working (Win 2003 server). Thanks. Have started up the Titan demo servers and connected via the server browser for the first time.
|
Well, I'm not sure if people can connect to it... can someone give it a try? The name of the server is: cock_n_balls: giblet hut and it's running the vehicle capture the flag map. Please let me know if you can see it and if you can connect.
Thanks! |
I can see it in the server browser but with ping 0.
I can't connect to it. Can't connect to the Titan UK either,showing up with 0 ping,too. I can connect to the multiplay DM server or the [COREIX] vctf one,my connection is fine. |
Quote:
|
...it may be that the random UPD ports need to get forwarded to the server as well.... when I pulled it out from behind the router logging connections, I saw a number of incoming UDP requests that aren't getting passed on to the sever when it's behind the router.
If this is true, the people at epic should be ashamed that they overlooked such a basic security feature. Most people would like to keep their PCs behind a hardware firewall. Maybe there's a way to specify a UDP port range for use with the server? ...can anyone else confirm that they cannot connect to my server? |
Quote:
Still not working. We still can't run UT3 Demo servers that anyone can connect to. Epic? Any chance of getting this one feature patched so that we can run servers? |
Quote:
Sorry for bad news :( |
s'ok thanks for the info...must be those other udp ports.
|
Nah, it's just that the workaround doesn't work...unfortunately
|
if you can see it in the list and cannot connect to it then its the host issue. The ip address in the server browser is pointing to your local address.
Look at the server logs. You should see this...(this is what I see) Init: Sockets: I am xcadeserver (206.83.242.242:0) This is the IP address the server will send to the server browser. In linux it pulls it from the host file. Before I changed the host file I saw 192.168.1.1:0 try opening the console in UT3 and manual connect to it. (hit ~ at menu) open xxx.xxx.xxx.xxx:7777 If you connect to it then you're firewall is correct. Hopefully this will give you some insight. |
Yeah, so the server logs still show my internal LAN IP addy. That said, I can open xxx.xxx.xxx.xxx:7777 where the x's are my EXTERNAL IP addy and I can connect just fine. Problem is the internal IP addy.
|
Doesn't work here. I've been trying for hours. Ports are forwarded and the hosts file is set. Still no good. I can't even connect to my external IP.
|
+1 for a router firmware update! :)
Working like a charm! |
All times are GMT +1. The time now is 06:22 AM. |