have no glue what to do next. Everything was fine on my side with RTCW and WildWest, but since a few days I`ve massive problems.
Any time I wanted to connect to a 1.5 server, I get the message "client unknown to auth". If I connect to a 1.6b7 server, it works fine......
My config : Windows XP with a vigor 2000 DSL router open Ports : 27950, 27960,27965,27952, 20112 (UDP/TCP) No XP firewall, but my firewall is named OutPost.
What I`ve tried : Deinstalled RTCW and WW and ASE. After reinstall, same effect, no connect to 1.5 servers, but to 1.6b7 servers. And i`ve updated punkbuster.
Any ideas ?
The onliest thing I`ve found in the internet was that i have to ping authorize.quake3arena.com that must be possible. I cannot ping this address. Is this the master problem ?
next step would be the reinstall of the whole system....... ???
o.k. I`ve tested a few 1.6b7 servers, I am just able to connect to the loneWolf V1.6b7 server.... But this without any problems....
What is different with Lone Wolf regarding the other WildWest servers ?
Pooh wish I could help ya.
When you reinstalled RTCW what version? If its GOY make sure you update the two patches. Then you need to load WW from the beginning 1.5 After this you then load in the 1.6 version. I think I read somewhere you cant just load 1.6 and have it work correctly.
Installed : RTCW Update Full Patch 1.40 Update Patch 1.40 -> 1.41 Installed WW1.5 Copied wwb6 Copied wwb7a Updated Punkbuster with pbweb.exe
mm sorry your having problems pooh :(
I don't think re-installing is gona fix your problem, since this error means either: 1) you cannot connect to the wolf auth server, or 2) the server your trying to connect to cannot, or both
I don't know exactly how the auth process works, and so cannot understand why you can connect to some servers and not others.
can you connect to LoneWolf 1.5 & 1.6 ?
can you try connecting to servers with your firewall turned off
strange behaviours : (same at enabled or disabled Firewall) starting from ASE : Lone Wolf 1.5 : client_unknown_to_auth Lone Wolf 1.6 : Connecting without problems DutchGame.NL : wrong password :-) Rockridge : client_unknown_to_auth REV Clanserver : client_unknown_to_auth Boot Hill : client_unknown_to_auth DutchGame.NL=WW=16b7 : client_unknown_to_auth pOOh`s WW1.5 : client_unknown_to_auth Easyconnect WildWest1.5 : client_unknown_to_auth
Punkbusterclient : V1.069|A1336 Enabled
I`ve also a next strange behaviour : When I start RTCW MP directly (not with ASE), and i wanna get the server list, then just 9-10 servers appear.... normally there should be a few hundreds.... When I start Wildwest directly (not with ASE) and I wanna get the server list, then I get no server ? Normally I see the same as I see in ASE.
@Hewy : The auth server for Wolf ? Is this authorize.quake3arena.com ? Or which server should I be able to connect ?
Hewster is correct, reinstalling WW or RTCW will not make any difference. This is a connection issue. This is something I found a while back.
Iggy Skrivet: 12 Okt 2002 11:13 Ämne:
saxat från slumpvis valt forum:
***Client unknown to auth, means that the q3/rtcw authorisation server did not recognise your CD key, or it already had someone using that CD key. This tends to happen when you timeout or crash while on a server, as it takes time for the authorisation server to determine that you are timed out and nolonger in the game. The auth server is also prone to 'going bonkers'. It will, more often than not, sort itself out if you leave it a short while and then try to connect again. Of course, the other side of the coin is that your CD key may have fallen into enemy hands or you have a home network at home with 2 ppl using the same copy of rtcw?"
forumplanet.com/planetwolfenstein "However, the "Client Unknown to Auth" error has some unique ways of occuring that aren't mentioned in that post. I'll try to describe them here.
There are three possible things you can verify. An error in either of them couldgive you the "Client Unknown to Auth" error. This will require some basic TCP/IP knowledge. Please ask if you don't know what I'm talking about.
Background: When connecting to a RtcW server, your RtCW client will announce its exsistence to the Wolf Authorize server by sending a message to 126.96.36.199 at port 27952/udp. The server you're connecting to will check the Authorize server if this message has been sent. If this is confirmed, the game server will let you connect. 1.If your client thinks, however, that the server you're connecting to is on the same subnetas the client, your RtCW client will notsend an auth message to the Authorize server. The best way to check this is to install a packet sniffer or network analyser on your PC and look at the traffic (Ethereal is a free analyser, but I think Microsoft also ships one with 2000).
Another, less direct, way is to enter "ipconfig/all" at a command prompt. This will give you the IP addresses of allyour interfaces, also the more obscure ones you might have forgotten about. If the address of the server you're trying to connect to matches any of the subnets configured on your interface(s), no auth message will be sent. So, take a good look at your local IP configuration.
Option 1 (or something in that direction) is the most likely if you have a very constant and specific set of servers you cannot connect with. 2.Less likely is that your PC can not or not always resolve the name "wolfauthorize.idsoftware.com". This could either be an incorrect entry in your hosts file (on W2K systems located at %systemroot%system32driversetchosts). This file should be non-existent or empty. Check the resolving by entering "ping wolfauthorize.idsoftware.com" in a command prompt several times. The ping will fail, but you must get the IP address "188.8.131.52" as a destination. If this one fails, either constantly or intermittently, there is a problem with your name resolving and you have to fix that. 3.The network path from your client to the Authorize server can be congested. If this is the case, your auth packets might get dropped on the way. This shouldclear up eventually, but might be a reason for intermittent authorization problems. Check it by using a program like "Ping Plotter", or traceroute, to trace the path to "wolfauthorize.idsoftware.com". Again, id have justly firewalled the server, so you won't reach the final destination, but the packet loss on the way to there is a good indication of the overall route quality.*** Lekdevil.NL
Thanks everyone for helping me...... (also HFX Rebel)
sooooo my friends :
Nearly everything is working again, but i`ve done nothing. So I have now 1.6 installed as before, but I ->can<- connect to every server.... So far, so good...
Buuut : Same behaviour inside Wolf MP. That means, starting WildWest directly, and I go to the browse server menu, I see, that there are 11 servers, but I get no list back.
@Iggy : I cannot ping wolfauthorize.idsoftware.com but it`s a apparent network problem outside my local network : (see attachement)
EDIT: made this post before your last reply pooh.. I'm glad its fixed :) see my last sentence about limited servers :/ mm interesting stuff Iggy, although in this case I don't think much of it applies, since he can connect to LoneWolf 1.6 We need to talk to Danny, and ask what is different in his setup between 1.5 and 1.6 pooh, did you delete the remaining folders after you uninstalled WildWest & RtCW ? if not, try this: delete the wolfconfig_mp.cfg file in the WildWest folder & the main folder delete the rtcwkey file in the main folder run Wolf (note all your binds / graphics setting will be set to default) goto the CD key menu, and enter your CD key. exit wolf, find your rtcwkey file, right click, and set as read only. Now try connecting to a WildWest server. btw, I too am only getting 11 servers listed in RtCW.. I think there is a problem with the master server AGAIN ! Hewster
HewsterEDIT: made this post before your last reply pooh.. I'm glad its fixed :) see my last sentence about limited servers :/ mm interesting stuff Iggy, although in this case I don't think much of it applies, since he can connect to LoneWolf 1.6
Understood. I had this same problem myself a while back where I could not join one specific server (don't recall which server it was) but I don't remember what I did, if anything, to make it go away.