rip|TEAM

Every time I try to log into the server I get a message that says

Server is a different version
COD_WaW MP

Anyone know what I can or should do?

thanks

what patch level are you running?

yes make sure you have the 1.1 patch

I've already got the patch, but it still gives me that same message...any ideas?  sure appreciate the help.

how about punkbuster enabled?

yep, got punkbuster on to...not sure if I would need to update it?  Still can't get in though.

At this point ....   a full reinstall?

My guess is something is corrupted.

With the 1.1 patch ready I would...

-Remove the game ( with add/remove programs)
-Reboot
-Install game
-Install patch

I have not hard of any others having the same type of problems ... 

Are you palying CoD5 - World @ War  ???????????????


OR

CoD4 - Modern Warfare ???

wow ... I'll be impressed if that's what the problem is Fork. Interesting take.

Nothing else seems to work.  It could be that he is playing a console.
I don't know anything about console servers - finding one direct connect, etc. so I didn;t suggest that.
I just have the reg X-Box that I haven't powered up in over a year.
?

well I did a search on Google and I don't know if will work but it helped some other folks.

Here is the fix:

Update the server's time and timezone to ensure they are correct.

Problem solved.

***DUDE !!!!!!! it works !!!!! i can not thank you enough for this...i dont know why, but it fixed my NO OR BAD CHALLENGE FOR ADDRESS error..... ***

HOW DO YOU CHANGE THE TIME ZONE:

The same way you would change the time/timezone on your workstation, if it's a Windows server: right-click on the clock in the system tray, and choose Adjust Date/Time. If you don't see the clock, right-click the Taskbar, and choose Properties, then check the Show the Clock checkbox. Be aware that you need Administrator or Power User privs to do this.

To keep a server up to date, the best approach is to set a time server other than the one that it starts out with. Standalone Windows servers are configured, out-of-the-box, to synchronize their time with a Microsoft time server. I have found these to be less than reliable, so if the server is standalone (i.e., not in a Windows domain), I always set an authoritative time server using the National Institute of Standards and Technology (NIST) atomic clocks. The 2 I use are time-a.nist.gov, and time-b.nist.gov. These sucker are always up and always accurate...unless NIST gets nuked. BTW, if the server is in a Windows domain, you don;t need to do anything of this, as it always uses the PDC as the authoritative time server. You do, however, have to do this with the PDC, as it's also looking to Microsoft's crappy time servers.

Microsoft has a long-winded way of setting the authoritative time servers, but I've always used this process with great success. Note that you still need local Administrator or Power User privs.

1. Open a command prompt and enter:

Code:
net time /setsntp:time-a.nist.gov,time-b.nist.gov <enter>
net time /query (this will show you that it got set properly)
net stop w32time
net start w32time2. After this, go to the System event log, and you should see an Event ID: 37, Source: w32time entry that says
Quote:
The time provider NtpClient is receiving valid time data from time-a.nist.gov (ntp.m|0x0|youripaddress:123->129.6.15.28:123). 

3. If you don't see this entry in the event log, then your firewall (somewhere) is probably blocking port 123, the SNTP (Simple Network Time Protocol) port...which is probably why your server was off to begin with.

If you follow these steps, and get it functioning properly, you never have to worry about getting out of step, time-wise, again. It is also a very basic step in building a Windows server.




http://www.fpsadmin.com/forum/showthread.php?t=16267 (http://www.fpsadmin.com/forum/showthread.php?t=16267)

THANKS for the help guys...I'll check it out.