1
Tutorial Collection / Re: [TUTORIAL] Port Forwarding I CANT SEE MY SERVER ON THE L
« on: September 08, 2011, 11:20:05 AM »
Ok, I believe I figured out why I will not be able to host a server and am reporting back in the hopes that what I learned will be of any help to those still pulling their hair out at this.
First, read this thread on the skulltag forums: http://www.skulltag.com/forum/viewtopic ... 72&t=23236
I determined that my isp is definitely running a router on their end, and in my case, I don't care that much to call them and see if they will allow me to run a skulltag server. (Long story short, it's a hokey local isp outfit that I actually know the owners personally. If it comes down to them having to make a change, I'll just cut my losses and see about a friend running a server.)
Anyways, how did I determine this in my case? Well, my isp provises the service via RF towers, an antenna on the roof recieves the signal. In the house, a PoE (Power over Ethernet) box both powers the antenna and provides the internet via a standard ethernet jack.
From there we can run it to a router, and we do, but it you can also connect your computer straight to said jack. (and if my isp would have it their way, we'd be paying extra to be allowed the 'privilege' of connecting any router to 'their' internet. They still provide the exact same bandwidth, they are just greedy and want the ignorant client to pay more for the exact same thing.)
Anyways, connected via the wireless or wired to the router (different one I was trying before), I can get the proper port I forward (10666) to appear in doomseeker by my ip, albeit still unresponsive. I could get this to work with the other router via upnp, though with the same result: proper port, no response. Connecting via upnp, of course, made no difference with this router. Finally, I decided to try a direct connection to the roof antenna, taking the router entirely out of the equation (we have no modem in this setup btw).
Lo and behold, the problem of the mysterious port I didn't assign problem returned, and upnp threw a NAT error in the skulltag server now. At this point, I was pretty sure that there was a router on the isp end that I could do nothing about blocking me from running a server. I was sure of it when I noticed the WAN (external) IP that my router was reporting: a 192.168.x.x ip, definitely not my WAN IP, but the IP of another router that my router was connecting to.
So if you are experiencing the symptoms that the OP describes in that thread I linked, do yourself a favor and call up your isp about possibly running a small, private game server. If they give you bs like being unable to give you your actual ip or other weirdness and they shrug their shoulders at your problem, either see about finding a better isp, or just give up on serving anything.
I know that depending on how your isp looks at 'running a server of any scale' they may require you pay for a separate option more suited for serving to begin with, ie, one with better upload speeds that servers require. Some will outright turn a blind eye at anything they really don't want the average customer to know about, and if your options are like mine, you really don't have any other choices.
It's just as well that my isp is blocking me from running a server, the download speeds are hardly decent at times; the lag would have most likely been too much to run any kind of game server.
For those of you with a better isp, in terms of overall speed and bandwidth, you might look into trying to get a VPN working or try something like Hamachi: https://secure.logmein.com/products/ham ... nload.aspxI have successfully ran a netplay server for some emulators in the past at my college with hamachi, but the lag made it beyond unworkable. Scratch that, with a VPN you are directly connecting to other computers via a 'virtual lan' so someone would run a server in LAN only mode, and everyone would connect to said virtual lan to get access to it. It does the same thing more or less, albeit with a lot of lag introduced in many cases.
First, read this thread on the skulltag forums: http://www.skulltag.com/forum/viewtopic ... 72&t=23236
I determined that my isp is definitely running a router on their end, and in my case, I don't care that much to call them and see if they will allow me to run a skulltag server. (Long story short, it's a hokey local isp outfit that I actually know the owners personally. If it comes down to them having to make a change, I'll just cut my losses and see about a friend running a server.)
Anyways, how did I determine this in my case? Well, my isp provises the service via RF towers, an antenna on the roof recieves the signal. In the house, a PoE (Power over Ethernet) box both powers the antenna and provides the internet via a standard ethernet jack.
From there we can run it to a router, and we do, but it you can also connect your computer straight to said jack. (and if my isp would have it their way, we'd be paying extra to be allowed the 'privilege' of connecting any router to 'their' internet. They still provide the exact same bandwidth, they are just greedy and want the ignorant client to pay more for the exact same thing.)
Anyways, connected via the wireless or wired to the router (different one I was trying before), I can get the proper port I forward (10666) to appear in doomseeker by my ip, albeit still unresponsive. I could get this to work with the other router via upnp, though with the same result: proper port, no response. Connecting via upnp, of course, made no difference with this router. Finally, I decided to try a direct connection to the roof antenna, taking the router entirely out of the equation (we have no modem in this setup btw).
Lo and behold, the problem of the mysterious port I didn't assign problem returned, and upnp threw a NAT error in the skulltag server now. At this point, I was pretty sure that there was a router on the isp end that I could do nothing about blocking me from running a server. I was sure of it when I noticed the WAN (external) IP that my router was reporting: a 192.168.x.x ip, definitely not my WAN IP, but the IP of another router that my router was connecting to.
So if you are experiencing the symptoms that the OP describes in that thread I linked, do yourself a favor and call up your isp about possibly running a small, private game server. If they give you bs like being unable to give you your actual ip or other weirdness and they shrug their shoulders at your problem, either see about finding a better isp, or just give up on serving anything.
I know that depending on how your isp looks at 'running a server of any scale' they may require you pay for a separate option more suited for serving to begin with, ie, one with better upload speeds that servers require. Some will outright turn a blind eye at anything they really don't want the average customer to know about, and if your options are like mine, you really don't have any other choices.
It's just as well that my isp is blocking me from running a server, the download speeds are hardly decent at times; the lag would have most likely been too much to run any kind of game server.
For those of you with a better isp, in terms of overall speed and bandwidth, you might look into trying to get a VPN working or try something like Hamachi: https://secure.logmein.com/products/ham ... nload.aspx
