Printable View
well, i do have two files that matchQuote:
Originally Posted by MasterX(BKC)
1st one is C:\WINDOWS\system32\drivers\etc\hosts
everything in the file is remed-out with an # except for this line
127.0.0.1 localhost
the other one is
C:\WINDOWS\system32\drivers\etc\lmhosts.sam
in this file everything is remed-out with an #, no exceptions
so i guess i gotta ask ya what kind of router you have and i'll try to buy that thing.
:puzzled:
127.0.0.1 localhost is just the loopback, standard
if everything else is #'d out your fine, sometimes windows will add entries below the loopback that it thinks are bad.....
if thats alls there its not that
Don't just open UDP, try UDP and TCP, both 17200-17300 :puzzled:
hey killme
if you aren't able to join from behind the router, what type of error are you getting ? - is the machine that wants to join the server able to see it using "LAN" by searching ? does it time out or give an error message ?
I am wondering if your DHCP settings are not forwarding the packets to the serving machine properly - do you have DHCP on, and set to automatic ?
You might try concentrating on getting the machines to talk to each other behind the router so that it is clear whether or not the problem is the router or possible the windows setup - because it is clear that your machine is conversing with novaworld and sending the server information there, yet it is unclear whether the other machines are being stopped at the router , or if the packets are arriving properly but being blocked by your internal windows firewall or some other windows setting, or even some other problem (pppoe or a proxy setting if those apply, or possibly even a dns error - what do the machines that are trying to connect to your server see when they try ?) (note that when the machine connects to novaworld to give nova the server information, it does not connect on 17000 range, it connects on different ports to perform those tasks)
also, as someone else mentioned, the ports should be 17200 to 17500, mine often connects at 17479, so be sure to include the whole range if you are forwarding, or setting your router to "virtual server" (same thing).
Hi guys, I too have been trying to run a server from behind a modem/router firewall with no success. I get the server running, but I can't join the game from my second pc. It tells me, "unable to connect to the selected server".... I tried opening TCP 17200 to 17500 and also UDP 17200 to 17500 and forwarding to the IP address specified within the firewall settings but still get the same results. The router I am using is a Efficient Networks SpeedStream 6300. IS there something I am missing here?? I notice on the Server page that shows up once you start hosting, at the top it says "Novaworld Server: TestServer [TDM] (7818) Does this 7818 maybe have something to do with it?? I notice this number changes every time you start a server.
Also, on the left side of this page, it says "receive port:0x4447". This maybe mean anything?? Probably just fishing here but am trying to provide any info that might help all of us...
Try hosting it in the DMZ.
Hi unoyt, what do you mean by hosting it in the DMZ?? I would think if no one can connect while hosting in TDM, then there must be something wrong with the open ports...Quote:
Originally Posted by unoyt
When you look up this on Novalogic, they have this posted "If you are hosting a game from behind a router you will need to set the outbound port, or trigger and the incoming port the same as the firewall ports for the game." But, no where do they mention any port numbers.
Hey MasterX, what do you mean by "127.0.0.1 localhost is just the loopback, standard
if everything else is #'d out your fine, sometimes windows will add entries below the loopback that it thinks are bad...."
How do you find out if these HOST and lmhosts files are #'d out?? What is meant by that?? I have them on my pc but am not sure where to go from there....
ports are normally 17200-17500 to be safe but 17200-17300 werx for me, and UDP protocol.
if the only entry you have is 127.0.0.1 Localhost you are fine, if there are other addresses and site names then delete the whole file....
simple as that, windows will rebuild the file with only good entries after a full restart...
Okay. Thanks for the info MasterX, will give it a shot....
Although your computer will rebuild hosts and lmhosts, neither of these affect the ports that would be used by the game or interfered with the firewall. These files exist to simplify the lookup from your computer trying to resolve the URL address of a website to it's IP address. Do not worry about deleting them, as it will not make any difference.
The following is a list of ports I found that are used by Commanche 4 to communicate with servers. the first on the list is the default port, and the rest are fall-backs designed for servers that do not respond properly to the first one.
17200, 21296, 25392, 29488, 33584, 37680, 41776, 45876, 49968, 54064, 58160 or 62256.
that is partially true. lmhosts provides name-based resolution within your subnet and/or internal lan to provide your machine with the ability to directly access machines on your subnet without bouncing all the way up to the nearest ip router (presumably your ISP's). hosts provides the functionality to override the DNS server you are using (presumably your ISP's). what masterx probably encountered was a name collision whereby the hosts file routed an ip request back to local host and he couldn't connect to the host he wanted to. hosts has a lot of useful functionality for blocking adware too, here is a link that is worth reading http://www.mvps.org/winhelp2002/hosts.htm
I have only ever had to alter these files to allow my machine to host multiple websites on multiple ips simultaneously, but I don't even remember what I did ( I just followed the instructions that came with apache)
bottom line is - if you use named pipes for file shares on your lan or subnet, or vpn, you probably wouldn't want to wipe the files as has been suggested. you could 1) back them up first, then delete and check to see if that helps, or you could 2) just scroll through and look for dns entries starting in novaworld, novaworld3, nw3, nw etc and delete them, which would stop the misdirection (if that was the cause)
I run a server behind a router and LAN connect to it with my 2nd pc......is that not what you looking to do Scream....... :smokin.gif:
all this port stuff is to confusing :puzzled:
finally its seems to be working :bouncy:
i bought a standard dsl-modem from my telephone-company and a router 'smc baricade smc7004vbr-eu' - two seperate boxes.
a team mate told me that this router works fine for him.
Hey Kill_me, any chance you could maybe explain the exact way you got it working?? I just got a SMC Barricade g SMCWBR14-G and am trying to get it working for this but no luck yet. Would really appreciate it.....
I guess I'm just lucky. I run a 2Wire modem/router that came with my SBC DSL. I can run a C4/BHD server and join from my 2nd PC no problem. I can even run a server on both PCs and have no problem with people getting in. And just for the hell of it one time, I ran a C4 and BHD server at the same time from one PC and could get into both servers. All that without doing any port forwarding what so ever. All that might sound a little low on the security side of things, But I had an IT friend of mine try to remote access my PC once and after setting the router in the DMZ zone and sending a remote access invitation and he still couldnt connect. I don't know if 2 Wire makes routers for anybody but SBC but if you can find one I would highly recomend it.