Archive for May, 2012

Reset Windows Server 2008 r2 Domain admin password

May 25, 2012

The process located here: http://hiltont.blogspot.com/2010/09/reset-password-in-windows-server-2008.html

Allowed me to reset the domain admin password when I had no other way into the system. It was awesome. I had called MS tech support and they will not help in these situations for security reasons. This saved me.

Advertisements

Avast Console Service not starting!

May 22, 2012

Grrr – this one really bugged me. I had a problem with a server running Avast Console. One day it just decided not to work anymore.
After many moments of hair pulling and gnashing of teeth I found there were two things that were just plain wrong. (Trust me I uninstalled and resintalled to no avail).

  • First – I went to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\avast! Administration Console\ImagePath and found that the path name to the console service did not have quotes (“”) around it. Fixing that got me a little further…
  • Second – the service logon credentials were set to a specific local account NOT to LocalSystemAccount like all the other Avast services. Changed that, plus the first point and the service started!

Next problem; The security certificate… Ahhhhh

Seagate Blackarmor NAS won’t connect to domain

May 22, 2012

So when you come to join the NAS to a Windows domain it comes up with errors like;
[NET_ERROR: No logon servers available to service the logon request]
or
[KINIT_ERROR: ‘Preauthentication failed’]
I looked on the message boards and didn’t find anything particularly useful until I read a suggestion that I should try a different user than the regular Administrator account.
I did, and hey presto it worked. I had another user with domain admin rights, used that and the NAS joined.
Can’t quite explain it but there you go, a fix.

VPN won’t connect (GRE – 47 issues)

May 21, 2012

So long story short I went through all sorts of research to finally find a fix;
Uninstall Symantec.
Well at least the firewall aspect of it anyway. I had been through reams of forums and no one touched on it! So eventually, tonight I had a client that “all of a sudden” couldn’t connect to the VPN. They said that nothing had changed so why did it stop working?
The reason is that Symantec in their infinite wisdom decided that blocking GRE (47) would be a great idea, but let’s let through 1723 just to throw them off the scent…
Thanks Symantec for keeping us on our toes.