Alright guy n gals, I'm a networky techy numbnuts and I managed to get my server working tonight. I wasn't gonna try at all out of fear, but my router fell off it's shelf and reset itself (phew) So while I was setting it back up I thought I'd give the Port Forwarding stuff a go...and it worked. So if anyone wants a hand setting a Netgear Router up to run your own server, I'm happy to try and help. Here's how it worked for me
I might be interested! Even tho my chaps are now running the show ;-) I'll write you later what's my model and such!
Alrighty man here's my details. I've a N300 WNR2000v2 I've forwarded already ports and such as described but for some reason when i check with canyouseeme.org it says: connection refused (all of the ports) Windows FW disabled
I advise you to open all three ports individually, not a range of ports. And from the list you attached I cannot see if you opened it for UDP or TCP.
Rule #12 is UDP (range) Rule #13 is TCP I'll try to separate UDP values right now (still Idk why TCP 60001 is closed...)
Nothing... same error. Double checking under ipconfig everything looks correct so the rules are pointing to the right place...
mine is a WNR2000v2 N300 You goto Port forwarding/Port Triggering then click 'add custom service' Fill out the fields like this (the internal IP will fill when you select the computer you want to run the server) then click apply... you may need to delete this and remake it when you want to re-open your server having been off I've put a link to this post in the OP.
Damn... Have you tried rebooting your router after opening the ports? Shouldn't really be necessary but routers are sometimes picky. How exactly do you determine your IP-address? Does your router show it in the menu?
Do you know, I don't know? but tbh it doesn't matter, cause it has stopped working! but aa haaaa I just deleted my original service and re-added it...and it works, so I reckon do it every time you need to set one up. It's up now Porsche Cup if people wanna join..I won't be around but I'll leave it on until about 00.00GMT
Hey Mach, yes that's what I did. On a side note, it's not that I'm getting errors on my dediserver monitor (once is up), and I can host with no problem (people see my server, it has a reachable ping, no problem connecting and so forth...). I was just curious about WHY a check on those ports gives me an error while on the other side the server is up and running and communications seem to work just fine. Weird! Mach have you checked your ports using www.canyouseeme.org?
Oh I don't understand it really, but at I can now set something up if I need to. But the dedicated servers have been very unstable anyway, it's probably not worth bothering yet.
So you know, I spotted something this morning.... the UDP range changes sometimes.. When I first set these up this morning, the RUF cup was UDP 60000, 60002 TCP 60001 and the E30 was UDP 60003, 60005 TCP 60004. Then I shutdown, came back later to restart them as a test...and they changed (see attached) This would explain why they don't work every time. When you start your servers, check that the ports match the ones you have set in your router manager and hey presto, working server every time. Oh and don't close your browser.