Announcement

Collapse
No announcement yet.

ProQuake 4.44 links not working - Trying to get QRACK prob fixed on chi

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • R00k
    replied
    Yes, I just connected with Qrack from my end. Everything works fine!
    Your host should document what's different so others can benefit, unless you switched hosts. I ping 35-42 there so that's even better

    Leave a comment:


  • kathos
    replied
    Scott was able to connect with QRack 1.90.

    Leave a comment:


  • kathos
    replied
    Try connecting to: 72.51.60.63

    Let me know how it goes.

    Leave a comment:


  • R00k
    replied
    Ya, indeed. Krix is special at anything, so he doesnt count.
    lol unban:
    66.64.*

    did you already try going back to ProQuake 3.50?
    Last edited by R00k; 08-11-2010, 10:10 PM.

    Leave a comment:


  • =peg=
    replied
    Tried clearing the ban-list? (at least temporarily).

    Leave a comment:


  • kathos
    replied
    They told me the machine is not behind a firewall, but we will move the server to another machine to test with QRack.

    It's odd because Krix can connect to chi using Qrack, while many others can't...

    Leave a comment:


  • kathos
    replied
    I will do so tomorrow. Thanks

    Leave a comment:


  • R00k
    replied
    rename your crmod_progs.dat back to progs.dat too! then do an rcon restart

    Leave a comment:


  • Baker
    replied
    I have done some testing and I'm thinking it is the firewall on the server doing this ...

    I can't get JoeQuake, DirectQ, FitzQuake or even older Qracks to connect to chi. And ProQuake connects right in.

    But weirdly enough ... Enhanced GLQuake connects right in too (aguirRe's engine). And so does DarkPlaces.

    I'm thinking something is really slowing down the client-server handshake. And probably causes the handshake Qrack/JoeQuake are doing to be too slow.

    Have the server host make sure all UDP ports on the firewall are open for Quake. This IS almost certainly the issue.

    Leave a comment:


  • Patton
    replied
    Doing the same thing Kathos. Not working

    Leave a comment:


  • kathos
    replied
    I renamed the progs dat, so the pak0.pak progs dat is loaded now (no more commands working), so whoever has QRack test it out so we can figure out this problem.

    Leave a comment:


  • kathos
    replied
    Originally posted by R00k View Post
    Kathos, do you have ftp access to your server? Try renaming the crmod progs.dat to crmod_progs.dat, and let the /id1/pak0.pak progs.dat load up by reloading the map and see if you can connect with Qrack, if so then it's a conflict between Qrack and Crmod 6.40, not Qrack with a ProQuake server. I can then take steps to resolve the conflict. Otherwise, I will have to try another angle.
    I will try this tomorrow.

    Leave a comment:


  • R00k
    replied
    Kathos, do you have ftp access to your server? Try renaming the crmod progs.dat to crmod_progs.dat, and let the /id1/pak0.pak progs.dat load up by reloading the map and see if you can connect with Qrack, if so then it's a conflict between Qrack and Crmod 6.40, not Qrack with a ProQuake server. I can then take steps to resolve the conflict. Otherwise, I will have to try another angle.

    Leave a comment:


  • rev
    replied
    who's with me man?!?!

    JILL!

    Leave a comment:


  • Patton
    replied
    Originally posted by metchsteekle View Post
    Looks like that means the world ends today stolen, grab the guns and take over the roads!
    I see where you are headed and I like it...

    but I'm not gonna do what everyone thinks im gonna do and FREAK OUT!

    I just wanna know who is with me??

    Leave a comment:

Working...
X