"Christmas - the time to fix the computers of your loved ones" « Lord Wyrm

Phosphor

Cobase 18.03.2006 - 20:55 1719 22 Thread rating
Posts

Cobase

Mr. RAM
Avatar
Registered: Jun 2001
Location: Linz
Posts: 17885
"Unable to connect" :(

prayerslayer

Oar. Mh.
Avatar
Registered: Sep 2004
Location: vorm Sucher
Posts: 4073
Zitat von Cobase
Ich kann mich auf keinen eurer Server connecten. Habt ihr den Port 1626 in der Firewall bzw. dem Router freigegeben?

jetzt schon.

//edit: jep, @Titus: geht no immer net :(

TitusTheFox

The Oilman
Avatar
Registered: Aug 2004
Location: Oiltown
Posts: 1256
jetz müssts aber gehn

prayerslayer

Oar. Mh.
Avatar
Registered: Sep 2004
Location: vorm Sucher
Posts: 4073
Zitat von TitusTheFox
jetz müssts aber gehn

nope, kann no immer net connecten :(

Cobase

Mr. RAM
Avatar
Registered: Jun 2001
Location: Linz
Posts: 17885
Verflixt und zugenäht, wieso geht das nicht. :o

prayerslayer

Oar. Mh.
Avatar
Registered: Sep 2004
Location: vorm Sucher
Posts: 4073
mir gehts auch net ein...

Zitat
Simplest (Method A):

1. Run one instance of the game with Network Mode set to Server (commonly known as the session Host)

2. Set the Network Mode of the other machines to Client and enter the IP address of Server machine for each. If all machines are within the same house or office, use the local IP address (LAN)

3. Start the Server instance first. The Clients should connect within a couple of seconds upon clicking Start, if things are working.

Running a public Server (Method B):

1. On the Server machine, enter a Server Name, and check Publish. This will cause the Server to ping a Lobby application (running on the Web server) periodically during the game with game session statistics (players, bots, match limits, etc).
2. When the client instances click Refresh on the Global Server browser, it will display a list of all Servers currently running that are "Published" Clicking on one of those Servers will populate the IP and Port fields. If the server is password protected, you will need to enter it yourself.

3. This arrangement assumes the Server has a valid internet IP; or if it is behind a NAT device like a router, it should have the listening port (default 1626) forwarded to it. UDP doesn't work if the Server is behind a NAT, haven't figured out why, but I would recommend keeping UDP un-checked in all cases (meaning uses TCP protocol).

4. Please don't "Publish" your server unless you have properly setup your router (otherwise players will see your server but will not be able to connect to it).

portforwarding is eingeschalten, kA warums net geht...

whitegrey

Wirtschaftsflüchtling
Avatar
Registered: Dec 2000
Location: 95% Wien 5% Linz
Posts: 7303
nen freien Port ala '80' auch schon probiert - bzw. kann wer testen ob es lokal überhaupt funzt?

wenn es mal rennt bin ich dabei, erinnert mich GFXmäßig ein wenig an das gute alte (ungeschlagene) Q2 :)

T3XT4

Beißer
Registered: Jan 2003
Location: .
Posts: 3794
also lokal funzts bei mir..

edit:
Habs grad mit einem Freund probiert..
funzt bei mir (als server) ohne Probleme.
Bearbeitet von T3XT4 am 18.03.2006, 23:25
Kontakt | Unser Forum | Über overclockers.at | Impressum | Datenschutz