mrbiscuits
New Member
Alright, this might not be wanted here, but I think it fits well with the discussion on the "read second" post, sorry if it belongs somewhere else, though it is a story that has steps for someone who has a dreadfully similiar problem.
I heard about L:O after wishing to play Ye Olde browser legions. Heard about garage games' closing doors, and thats too bad, but anyway it led me to here.
I downloaded the game, started up, and got the 'contacting auth server' forever error, outlined in the read second post. After reading that post I decided it was my time that was messed up, and it took me a whole day, and many DOH!'s to figure out the fix.
First off, I had to synch my time with the interweb. (I'm on Win XP, though I hate it.) I double click the clock in the lower left side of the screen, opened up the date and time properties, clicked on the internet time tab, and tried to synchronize the time with the windows time site. It failed, giving me 'The RPC server is unavailable." I tried the rest of the time sites to get synch the time with and all gave me the same reply.
Time for google.
I search "internet time synch rpc", and get a wide variety of posts - lots of people have the same problem as me. All of the fixes don't work, except two, which I nab. It something to do with the Windows Time Service no working right.
I go into services.msc (Start > run > services.msc) and scroll down to the Windows Time Service. I make it so it starts automatically, and upon fail restart.
Problem is still there.
There is another solution, which uses the command line. Go to CMD (start > run > cmd) and type in the following lines: (nabbed from http://social.technet.microsoft.com.../thread/d9c65d89-4691-4212-8991-616f01183d70/)
net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time
This restarts the windows time service, and simultaneously succesfully gets the time for you. Keep in mind that after this, the rpc error will probably still come up - just know that your time is correct.
The case with me though, was still weird. Legions (as well as a multitude of other programs requiring time) still don't work.
After the next 5 hours, a long sleep, and a reboot, I figured it out.
The windows time synch does not synch your date. It synchs the time. The morning after the troubleshooting I got on the computer, and looked at the time, to see if it would work.
My year was set to 2010. It's 2011.
End of story.
I feel stupid.
I heard about L:O after wishing to play Ye Olde browser legions. Heard about garage games' closing doors, and thats too bad, but anyway it led me to here.
I downloaded the game, started up, and got the 'contacting auth server' forever error, outlined in the read second post. After reading that post I decided it was my time that was messed up, and it took me a whole day, and many DOH!'s to figure out the fix.
First off, I had to synch my time with the interweb. (I'm on Win XP, though I hate it.) I double click the clock in the lower left side of the screen, opened up the date and time properties, clicked on the internet time tab, and tried to synchronize the time with the windows time site. It failed, giving me 'The RPC server is unavailable." I tried the rest of the time sites to get synch the time with and all gave me the same reply.
Time for google.
I search "internet time synch rpc", and get a wide variety of posts - lots of people have the same problem as me. All of the fixes don't work, except two, which I nab. It something to do with the Windows Time Service no working right.
I go into services.msc (Start > run > services.msc) and scroll down to the Windows Time Service. I make it so it starts automatically, and upon fail restart.
Problem is still there.
There is another solution, which uses the command line. Go to CMD (start > run > cmd) and type in the following lines: (nabbed from http://social.technet.microsoft.com.../thread/d9c65d89-4691-4212-8991-616f01183d70/)
net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time
This restarts the windows time service, and simultaneously succesfully gets the time for you. Keep in mind that after this, the rpc error will probably still come up - just know that your time is correct.
The case with me though, was still weird. Legions (as well as a multitude of other programs requiring time) still don't work.
After the next 5 hours, a long sleep, and a reboot, I figured it out.
The windows time synch does not synch your date. It synchs the time. The morning after the troubleshooting I got on the computer, and looked at the time, to see if it would work.
My year was set to 2010. It's 2011.
End of story.
I feel stupid.
