Try deleteding all your configs and try again

try another server, i get it on random servers..

had the same prob few days ago...
sometimes, re-entering the cd key is enoug. But the only thing that helped me was entering this in my autoexec.cfg:
seta net_master0 "192.246.40.28:27650"

thx man, it works !!!!

:x

Check your DNS config. Looks like your client doesn't resolve the IP addresses correctly.

Have a read through http://ucguides.savagehelp.com/Quake4/FAQ_Multiplayer.htm

or just wait :)

also check config for com_guid and delete that line if you come across it.

Your problem has already been answered, but to illustrate what's going on here anyway:
Does this happen on all servers? This will happen when the server you're connecting to receives no information from the master server about your client. when you connect, your client sends your "quake4key" to id Software's master server. the hostnames of the two (or more) master servers are hard coded into the Quake 4 code. When it [Quake 4] cannot look the hostnames up via DNS, then you'll need to manually specify the master servers as you did above. Reasons for not being able to reach the servers via DNS include: network failure (local or remote), network misconfiguration (local).
If the problem is not resolved within two days, then you are likely suffering from a local DNS error. This could be caused by your local DNS client malfunctioning, your DNS servers (most likely handled by your Internet Service Provider) malfunctioning, or your "resolver" client malfunctioning. (do you have the master server forwarded to the loopback address (127.0.0.1, commonly) in your hosts file?)
If, however, you believe DNS to be working fine, or you've set the master servers accordingly in your configuration, via the commands:


seta net_master0 "192.246.40.28:27650"
seta net_master1 "192.246.40.244:27650"

and you still receive this error, then the issue is: a configuration error, a network configuration error, or network failure. If the problem persists longer than two days, then you may rule out the latter option. If there is a network configuration error, then there may be static route entries on your machine, your local network, or your ISP's network that are preventing you from reaching the master server via UDP traffic, or even reaching it entirely. Sometimes there are local networking devices which use DHCP to lease addresses to client machines, and sometimes these devices malfunction, giving wrong netmasks to the client. And sometimes there are human errors in entering the netmask. Be sure that if you're using the 192.168.0.0/16 private network that you have not set your network mask to anything other than 255.255.0.0 or 255.255.255.0 (unless you know what you're doing). If this fails, then you may want to delete your configuration and cdkey to eradicate those pesky punkbuster entries and whatnot. This pretty much covers every authentication problem you'll encounter. If not, let me know.

x

ul ;] :]

ok