Quake one LAN server connection problem

[RD-Balogh]

I am trying to set up a Quake LAN private server to play with a couple of friends at home.

Server os is Linux Elementary OS 32bits.
Client os is win 8.1
Got it up and running with pqlinux, I see the server from my client but cannot connect.
Tried nquakesv (mvdsv), same issue.

Server is running on linux box.
Windows client sees the server. When I try to join I see standard messages of connection:

The Necropolis
you got the shells
trying...
trying...
..
host_error: cl_connect: connection failed

Linux box has no firewall installed.
That linux box is dual boot, so I booted up in Win7. Started quake dedicated server from there and I could connect from Win 8.1 client without any problem.

I prefer to run that quake server from linux. Does anyone have a clue why I cannot connect to it?

If all else fails I can run the server from windows but I can't stand it that I cannot get it to work from linux server lol

[Syluxguy28O3]

hah i'd just roll with windows.

[OMacKnight]

>Install gentoo

[Mr.Burns]

Just taking your server out of the equation for the moment, can your client machines to connect to and play on other Quake servers? So for example, if you fire up Quake on your Client PC and type connect quake.shmack.net, which is a server in the USA running standard ID maps, in your console and press return does it connect to the server and allow you to play?
If it doesn't connect properly then this could point to a firewall problem on the client pc's rather than just with your server.

Unfortunately although your netquake client will try and make an initial connection to the Quake server on 1 port (eg 26000) the clients then connect through any one of a multitude of different ports. In practical terms this often means that you have to allow your Quake client to use any port it needs.
If I recall correctly Spike's FTE QuakeWorld Server/client does allow you to specify a single port (eg 27500) and stick to it. Although this may be a product of my own imagination , Spike/Rook please feel free to jump in here and correct me if I'm wildly off on this


Kind regards

Monty

[Spike]

1. proquake tries to connect to port 26000 by default. nquakesv uses port 27500 by default. also, the protocol is completely different between nq and qw. they won't actually see each other even if you use the same port.
Yes, a couple of engines can connect to either type of server, but they do need to be told the correct port.
Yes, one server can host both protocols simultaneously. Its not without its faults, as it favours avoiding DoS attacks instead of 100% compatibilty (by default), and yeah, ports.

2. various NQ clients tend to bind to a random address. this means that on a dual-homed computer (two+ network interfaces), then its gonna fail for all but one of those networks. you can override this with the -ip command.

3. NQ servers need to tell the NQ client the correct ip address to use as well as the correct port. picking the right address is vital here too. hurrah for dual-homed hosts! again, try the -ip commandline argument.

4. windows with ICS active will happily act as a DHCP server, even before it has established a WAN connection, meaning the LAN gets an address first and ends up as the default (for quake, anyway). by default, linux does not do dhcp without a lot of esoteric reconfiguration. choice of default interface can be pretty random. I dunno.

5. QuakeWorld servers listen on all interfaces, and do not tell the client to connect to a specific ip instead. as a result, they are much more robust.

6. Your problem looks like the client can't see the server *at all*. Are you sure you can ping the server with the windows/linux ping command?

[RD-Balogh]

In reply to Mr.Burns. I connected from the client to quake.shmack.net without problems. Was able to play. So I assume the client and firewall are not the problem.

I will try the other suggestions with regard to port numbers.

Not sure I explained this the first time round. The server and client are in the same domain. It is a very simple LAN setup.

Cheers,
Mark

[RD-Balogh]

Thanks Spike for your suggestions.

nquakesv uses port 28501 (says so in the server config).
I set the port to that, still doesnt see it.

pqlinux uses port 26000. I see the server in the list (join local games), but when I connect to it, it fails to connect. Even if I set the port to 28501, when I scan for local games it finds that server. Wont connect however.

I used diff ports. 26000, 27500, 28500, 28501. Nothing works. I tried the connect command using the internal ip address 192.168.1.15.

Nothing.

Again, when I setup a quake world server in windows, I can connect from my client.

Weird.

Anyway, thanks for your suggestions and tips. If I figure it out, I'll let you know.

Cheers

[Cobalt]

Try the server with a command line including the ip address. IE: -ip 127.0.0.1

Also, apply the -ip command to the client as well, but use whatever the default gateway address is for your network.

There was also an IPX type protocal too that I think you can use for local net games, and it did not require an IP address, been so long and I dont think anyone has tried it in a long time.

[bluntz]

Are you sure iptables is not running on that OS?
if it is have a look at this .....
How to: Linux flush or remove all iptables rules - nixCraft

[Tremor]

Prolly wanna stay away from IPX. That was used in Novell networks back in the mid 90's. Implementing IPX on anything later than Windows XP is more of a hack than a fix. Abandon all hope ye who deal with IPX.

Give us your exact linux command line that you're running the server with.

[RD-Balogh]

Not thinking about running IPX lol.

Tried iptables thingy. No effect.
Tried running server with -ip (local ip). Now the server wont show up in the server browser (local games), but I CAN connect to it fine by connecting to the ip !!

So thanks for all your help, finally got it running!!!!!

exact commanline is ./pqlinux -ip 192.168.1.15 +exec server.cfg

and the server.cfg is:
sv_gamedir qw
deathmatch 1
hostname "MyHostname"
rcon_password xxxx
timelimit 20
fraglimit 30
pausable 0
maxclients 8
map start

I cannot connect to nquakesv locally but I don't care. pqlinux (proquake) runs fine.

Thanks again for all your support. You guys are great and made it possible for us to relive old times playing LAN quake!!