Can't Connect To bigfoot.quake1.net

[Quaker Oats]

Yessir, I'm getting this screen, just like in the sticky:



But I'm using GL ProQuake, so... yeah. I don't recall this happening with any other server. I haven't tried a whole bunch, but I can connect to every one I try except this one.

I live on the east coast, if it's any consolation.

Thanks for reading!

[bluntz]

Yessir, I'm getting this screen, just like in the sticky:



But I'm using GL ProQuake, so... yeah. I don't recall this happening with any other server. I haven't tried a whole bunch, but I can connect to every one I try except this one.

I live on the east coast, if it's any consolation.

Thanks for reading!

That does not look like glquake, it looks like winquake

[LambentHammerBurst]

Yeah the whole "(WINQUAKE)[1.09]" in the corner clearly states you're not using glquake at all.

[Baker]

That isn't his screen shot, he said "it looks like this".

1) Are you able to connect to other servers and just not Bigfoot? I mean like can you connect to other servers right now (i.e. yesterday doesn't matter, does connecting to other servers today work).
2) What happens when you type "test2 bigfoot.quake1.net" in the console.

This hopefully will narrow down the issue.

[foq]

What version of glpro? Even the old standard glpro 3.5 should work with this, but you might want to try proquake 4.

ProQuake 4: The official continuation of ProQuake

[Quaker Oats]

That isn't his screen shot, he said "it looks like this".

1) Are you able to connect to other servers and just not Bigfoot? I mean like can you connect to other servers right now (i.e. yesterday doesn't matter, does connecting to other servers today work).
2) What happens when you type "test2 bigfoot.quake1.net" in the console.

This hopefully will narrow down the issue.

1) Every other server, I can connect to and always have been able to connect to. I've never been able to connect to this server, not at least since I first tried about 8 months ago.

2)

What version of glpro? Even the old standard glpro 3.5 should work with this, but you might want to try proquake 4.

ProQuake 4: The official continuation of ProQuake

Version shows in screenshot, so I should be all set on that.

[Baker]

The connection handshake isn't being completed. It does seem weird that only this server would be affected.

The test2 result and the fact that you are able to complete part of the connection handshake means you are at least able to communicate with the server.

It is a little weird that you can connect to other servers and a little weird that others players using ProQuake able to connect to bigfoot.

[Quaker Oats]

The connection handshake isn't being completed. It does seem weird that only this server would be affected.

The test2 result and the fact that you are able to complete part of the connection handshake means you are at least able to communicate with the server.

It is a little weird that you can connect to other servers and a little weird that others players using ProQuake able to connect to bigfoot.

Gah, I've tried different versions of ProQuake too, none of them seemed to work. Oh well, it's not a huge deal, I ping pretty high at that location anyway. I guess if something ever comes to mind about what might be causing this problem, I'll give it a try.

[Baker]

Gah, I've tried different versions of ProQuake too, none of them seemed to work. Oh well, it's not a huge deal, I ping pretty high at that location anyway. I guess if something ever comes to mind about what might be causing this problem, I'll give it a try.

It is a huge deal to me. It's 2011 and the Quake engine has been open source for over 10 years.

Although my to-do list is still a towering list of things that I intend to complete by Quake Expo, I am considering trying to tackle this issue hopefully once and for all.

I do not believe it is the client at fault. Still, ProQuake server needs to evolve a little and I'm rather tired of occasional connectivity issues like this. I am also considering stronger client network connectivity self-checks. We'll see ... I have so much to do and while I have a lot of time for a bit longer, my to-do list isn't short. Still, I'm determined to plow through it ... and have been doing exactly that lately. Still, adding more to my to-do list is a bit risky ...

[Quaker Oats]

Haha, alrighty well if something arises in the future that may help my issue, then you know where to post.

[Mr.Burns]

If it helps, I'll mention it to one of the Admins in Biggy's server and see if they can think of anything that might be causing your problem.

Kind regards

Monty

[Lerster]

FileSwap.com : quake_error.jpg download free

proquake crashed on my yesterday, SZ_GetSpace: Overflow without allow overflow set.

After i re-entered it i got icon's on zero, shmack 01, and a bunch of places.

So i closed and reopened it again.

Then finally it let me back onto zero where ppl where ctfing last night.

I don't know it this is relavent to this topic, b/c i didn't do any of these (test2) or whatnot stuffs.

Anyways, it was weird tho.

[leopold]

FYI, got the same problem with quakespasm 0.85.4 which claims to have the NAT fix. darkplaces, proquake, joequake, qrack connect fine.

Linux machine here, behind a NAT-ing router.

[leopold]

ok, solution for me is to set the NAT ruleset to leave the source port untouched. Now quakespasm works.

[Mr.Burns]

If it helps, I'll mention it to one of the Admins in Biggy's server and see if they can think of anything that might be causing your problem.

Kind regards

Monty

I don't know if it will help but I had a word with Peg on your behalf (as promised) and he couldnt think of any server side issues such as ban hammers and so forth, which suggests it may be some NAT issue perhaps?

Hope this helps

Monty