My and my friend's attempts to get things going

[Martens]

Hello guys,

I have come here because I have tried a lot of things in order to get Quake working in cooperative with a friend of mine but failed each time.

Firstly, we both downloaded the same files to make sure it is all compatible. We're trying just normal quake for now.

We tried the following engines: Darkplaces, Tomazquake, and Qrack. In reality we also tried glquake and proquake but on those engines all the textures looked white, while the others worked well for both of us in singleplayer.

Since he is behind a router, I had him allow access for quake and unblock the default port that it uses.

So, I go into the games, and start a new multiplayer game using default settings excepting for the changing of Deathmatch to Cooperative of course.

Then what happens is that he simply cannot connect. The connection isn't found, but when Tomazquake is used, we get this: CL_Parseservermessage: illegible server message. He actually shows up as connected for a second and then is kicked.

I tried googling that but it seems to happen to a lot of games, therefore I wasn't able to find a solution which applies specifically to this.

At this point, we just want to get the game going on any engine that we can, but do not know what else we can try. I already did check my own firewall.

I also tried to enable and disable the friendly fire option and to start the game directly on e1m1, you know, just for the sake of trying.

We're at a loss here guys, got any tips?

[Phenom]

did you try adding "-listen 16" to the "host's" command line?

[foq]

The Quake server needs to be in the DMZ to work properly, and not have just port 26000 forwarded. Here's a snapshot from my router's setup:



You'll also want to makes sure the host PC is always at that IP, or the DMZ won't be pointed to it anymore. In XP, this can be done through start > control panel > network connections > *whichever your active ethernet device is, mine says Local Area Connection > properties > Internet Protocol (TCP/IP) > properties.

[Lerster]

from recollection i ain't tried in ages there used to be a quakeipx.exe or ipx something .exe for quake that u'd use for standard lan-lan gameplay.

My guess is for this day an age a new client dl such as the latest proquake: ProQuake 4: The official continuation of ProQuake first link for windows users on the right.

Should fix the white graphics.

But for this day an age you're probably better off if you just looking to dm, is try the CRmod server module: Clanring CRMod

Which can be found above.

One pc would have to run the CRmod. (if your pc has no firewall use yours) and he'd find you via local games.

I don't believe quake clients can do lan other then that IPX.exe that used to exist in quake.

I could be mistaken bout that tho as i ain't tried in years and when i tried ages ago i did the ipx route.

I am sorry to say i do not have a link to that client and likely it would have to be run in compatibility mode if it even existed still as its old.

But if one of you runs the crmod server, then u'd both load proquake or your selected client and search for games and you should find it.

Hope this helps, ~Cheers.

Oh its for cooperative... you'd prob need to ask one of the ones that runs the COOP servers online for the server client they are using and a config file from them... then run that.

There is no way to run coop by default in any game engine or old ipx server client to my recollection.

I may be mistaken. But anyways, goodluck.

[foq]

Progs 106 has a cooperative function, but it's pretty lame.

It sounds to me like they're trying to play over the internet, but if they're trying to get a LAN game going then it is indeed very odd that they can't connect.

[bluntz]

You need to run a separate server on a non default port so that there is no conflict with the port you are playing from.(or vise versa)
You can not run 2 instances of the game on the same port.
All the switches need to be set from command line or an autoexec.cfg in a subfolder. I believe the clan ring mod has an example how to in its docs.
After it is up and running on port 26001 ect.. Fire up your normal quake and connect.
For a coop server just run quake.exe -dedicated +coop 1
Look here Quake 1 and QuakeWorld Server setup - Planet Quake

[Efess]

This is false, there is no conflict of ports when you run a server from the default port. The listen port 26000 only accepts connections and sets up a stream using a different random port.

[bluntz]

This is false, there is no conflict of ports when you run a server from the default port. The listen port 26000 only accepts connections and sets up a stream using a different random port.

You Spoke to soon me thinks, not a listen server.
You run the server or your client on 26000 either/ or but not both.
NO self respecting Quaker I ever knew would EVER play on a listen server,but some do and I know who you are you sub 20 BASTARDS!!!
This is easy to do by making 2 shortcuts to quake.exe on the desktop.
For the server enter your lan ip for the hostname
For the client enter your lan ip :26001 for the hostname
This will keep the server set to accept connections on the default port and keep Efess happy.

[Efess]

You can host a dedicated server on your own machine and connect to it.. There's no port conflict, try it.

[bluntz]

Also putting the router into DMZ is a very bad idea,it opens ALL your ports.
A small block of addresses need to be assigned 16 or so should cover it.
I am not sure it is needed at all for lan if the rigs are the same work group.
just READ the setup guide I posted above.
Now I know that it can be done on the same port however it takes ipx protocol to do so as was posted by L3r it can be done.
Efess you may be correct you may be able to run 2 instances
on the same port for a while but the port conflict will add up quickly and fubar the server or the client loosing sync.

[Efess]

It's not a case of "may" being correct, this is how it is

There's no "conflicts adding up/fubaring/losing sync", it either works or it doesn't. Only one server can claim port 26000, any program can make as many UDP connects as it wants to that port without any problems. The client has a port of its own that the server responds to, which is why when you run "status" in the console, every client has a different random port.

[bluntz]

Only one server can claim port 26000.

Thats what I've been saying.
Well we agree that the server setup is right at least,What we are arguing now is how you setup your client. to play on the same box.

[bluntz]

Guess I gotta eat crow here
Seems Lan connect is broken ,if I bring up the multiplayer search local it shows up but you cant connect.
And assigning a different ip to the client does not fix it.
However connect localhost does as well as connect yourlaniphere.
I see now there was no conflict it was 1 server not 2.

[bluntz]

Please let us know your results

[foq]

can't connect

nice threadjacking btw