How do I connect to a server?

[justin12399]

Ok so I launched quake and I typed in the console: connect bigfoot.quake1.net and It sayed connection accepted.

What do I do after that?
And yes I am a

[Mr.Burns]

Hi justin,

I'm no expert but it sounds as though your quake client is making the initial connection and then there is a break in comms and the server can not send packets back to you. Its my understanding that there was a very similar set of symptoms to this noticed when players used older quake clients to play either through a NAT'd address or behind certain firewalls.
If you haven't so already you might try downloading and running the latest version of Proquake (from this very site) which has a lot of these bugs fixed by the mighty Baker. If that still does not allow you to connect then come back to us with more detail and being a helpful bunch I'm sure someone will try and help you.

Hope this helps

Monty

[wicked_lord]

Update client, as mr burns said.

[Mindf!3ldzX]

Yes, that sounds like the client side NAT bug

[wicked_lord]

Stewbies!! Stew and newbies!

[justin12399]

I downloaded ProQuake 4 and it kept saying after i connected:
Trying...
Still trying...
Still trying...
Connection Failed

[Mr.Burns]

Hmm that's odd. Have you tried connecting to different servers? Bigfoot is a fun server, based in Germany as I recall, and is packed with custom maps. perhaps try and connect to another server such as flanders.quake1.net or quake.shmack.net. If you can connect to either of these then this suggests that the problem might not be comms based.

If you still can not connect, your could try running the new Proquake 4 executable, which usually cures most of these problems with a few settings changes. A couple of things that may help:

1. Add your internal ip to the command line you use to start Proquake 4. For example:

glpro451.exe -nocdaudio [COLOR="DarkOrange"]-ip 192.168.1.n[/COLOR] -noipx -width 640 -height 480 -bpp 32 -heapsize 131072 -game proquake

Where 192.168.1.n is your internal IP number.

2. Check your firewalls, if you have them, to ensure that they are not blocking the return traffic.

3. Check your router for the same. As a test, you could try to route all UDP traffic to the internal IP address of your gaming pc.

5. As another test, if you have a DMZ on your router you could try and put your PC in to that Zone and see if you can connect. This is not the most secure option but may help you isolate where the problem lies.

Hope this helps

Monty

[Mindf!3ldzX]

make sure you gave the exe permission to access both private and public networks , both. It happens the first time you run any application that uses the network....

[wicked_lord]

I dont miss having this issue one bit.. Haha think goodness for fixes!

[morrowind]

With the client prior to proquake: After it says connection accepted, type "ping"
in the quake console.

It's something to do with the machine not sending the initial ping back to the server. Personally I had the same issue. And right now I'm using winquake because my proquake is doing the same thing to me (connection failed).

When I look at the packets with proquake absolutely no packets are leaving the game.

So for now, use ping?

[Mr.Burns]

To be honest, the "type ping in console" method has never worked for me when I had the same issue, but if upgrading to PQ4 is not an option, and none of the above resolve your problem, then if ping works for you then by all means go for it

[wicked_lord]

What os and anti virus or firewalls are you running? Any information you provide is helpful, other then you cant connect.