PDA

View Full Version : MoH & NAT/port forwarding


Unregistered
08/21/02, 10:37 am
Hi

which ports and protocols need opening/forwarding to a Medal of Honor server ?

TIA

BENSTER
08/21/02, 02:09 pm
http://www.clanservers.net/bb/showthread.php?s=&threadid=2422

Unregistered
08/21/02, 06:12 pm
Read the link above, but it answers a different question about showing up on Gamespy.

I too need to know what ports to open, and which to redirect for my Vigor router.

I have the opposite problem to the other thread. My server is shown on Gamespy, but you can't connect.

Thanks

William

BENSTER
08/21/02, 07:35 pm
PMSgirl
Junior Member

Registered: Jul 2002
Location:
Posts: 22
OMS THANK YOU!!!
OMG!! it worked!

this one: C:\Program Files\EA GAMES\MOHAA +set dedicated 2 +set net_port 12203 +exec server.cfg

THANK YOU SO MUCH!!!!!!!!! THANK YOU!!!!




Use this command line to start your server. Dedicated 2 makes it public, net_port 12203 is specified, and thus you will forward this port in your router. IT will be properly seen by gamespy, and everyone will be able to connect.

Unregistered
08/21/02, 09:26 pm
Thanks, it works.
Buggered if I know why though as the server console was already reporting port 12203 being used and I had opened that port and forwarded it in my router.

Tried it once just now and success, but I'll test more tomorrow.

Thanks

William

BENSTER
08/21/02, 09:54 pm
Here's the deal, some routers block outgoing ports, some don't . If yours don't, it will mask your port, to whoever...in this case the master server. My router masks it with a negative port number, like -103.

So a player browes gamespy, find your server xx.xx.xx.xx:-103 and connectes. THe router already knows that -103 should go to your server and the request is passed along to your local 192.168.0.2:12203 and they get to play just fine. But you give yoru IP address to you buddy, and tell him port 12203, and he'll never be able to connect because the router is not allowing that port.

Take a linksys on the other hand, the latest firmware releases block outgoing as well as incoming port attempts. This is great if you get infected with a trojan program, or just want to stop Spyware type software. On the other hand, nobody can connect at all until you open the ports.

Unregistered
08/21/02, 10:16 pm
I pasted those command line switches in, and I thought it was all hunky dory. But now I'm not sure what happened exactly.
I'm thinking that I connected successfully by my 192 address, not the externally visible 217 etc etc IP address.
I also found that my shortcut to MOH already had this in it as advised by Alliedassult.com

+set dedicated 1
//Launches the game in dedicated console mode

So I had your's then this, presumably fighting each other. I took out the '1' one, and launched the server again, but since then I've not been able to connect in.
It's still seen on the internet, but I notice that it appears twice, one with internal address and one external.
Not surprisingly, when I pick the 192 one it goes in ok. Not so the 217 now.

I have tried both permutations of +set dedicated now, but neither work.

Too tired to continue now, but I was wondering where you got the advice that it opens the server publically.
This seems very fundamental, and the advice page on this URL doesn't mention it being needed.

http://www.alliedassault.com/community/guides/bull/guide1.shtml

thanks and goodnight

William

BENSTER
08/21/02, 10:39 pm
Quake 3 setup guide explains a majority of it

+set dedicate 1 = Dedicated server, LAN only. Will not report to master server

+set dedicated 2 = Dedicated Public server...sends pings to the Master server.

Depending on your router, you may not be able to view it as a public server.

When you say it shows up twice, as public IP, then Private IP - I'm thinking you are showing it as a local server. the master server must be able to resolve yoru IP adress, and 192.168.0.x just isn't gonna resolve.

Unregistered
08/22/02, 11:11 am
I think I know why now.
I've made so many changes - in the suggestions above - and opening ports and redirecting on the router etc - but I think I was wasting my time. I found this in the routers FAQ.

Note that port forwarding applies to external users only - i.e incoming traffic from outside your LAN. Internet user inside your LAN cannot access your external public IP address and come back in; internal users should access the server on its local internal IP address, or you can set up an alias in a Windows hosts file. This also applies if you are using a URL (web address) which resolves to your public IP address - internal LAN users will not be able to use that URL - the packet is not 'bounced' back into the LAN by the forwarding rules - they apply to incoming external users only.


I'd be interested to understand the hosts file usage better, but for the moment I think I can get in to my own server using the 192 IP and maybe the world can get in on the 217 IP.
I think it works as I tried my 56K dialup and got in. Just need to see if anyone else knows I exist and manages to get in.

Thanks

William

BENSTER
08/22/02, 01:06 pm
Always use your internal IP address.

RE: HOSTS

Add the following line:

//connecting to my wolfy server via public IP address
192.168.0.x 217.xx.xx.xx



Replace 'x' with proper IP addresses.

BENSTER
08/22/02, 01:07 pm
OOps, I don't think hta twill actually work. You must have the URL on the public IP address.

Do a ping -a 217.xx.xx.xx

and it will give the name of your IP address, and you can substitue that in there. If you have dynamic, then it may not work at all for you.

Unregistered
08/22/02, 02:20 pm
I did the second suggestion ok and got the long IP 'name' but when I said before that I'd like to understand it better, I meant from scratch unfortunately.

What should this file be called. and where should it live, and do I need to reboot?

Thanks

William

BENSTER
08/22/02, 02:58 pm
No, you don't need to reboot.

this file is called HOSTS
Not HOSTS.
not HOSTS.TXT


In Win98, C:\windows contains: Hosts.sam Lmhosts.sam and Host
The .sam means sample. Here is hosts.sam

# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost


Search your winnt or win2k folders as needed for other OS's, I think win2k HOSTS is in the windows\systems folder...can't recall.

Bascially before your computer asks your DNS server, it browses the hosts files first. They can save time if you happen to use a certain URL often. If you don't have the IP address specified for the URL you entered, then it will goto the DNS server and look there.

This host file can also be use to redirect spam/advertising when pop=ups occur, or in page banners are present. This will save download time/bandwith. Down side - you get a small error message, and the window still pops up.

BTW - use # instead of // for commenting lines in above post.

Unregistered
08/22/02, 07:43 pm
Thanks for your help. Lots to practice with here.

William

BENSTER
08/22/02, 08:17 pm
Hope it all works out for you....I really went in circles with NAT and Quake 2.