I had need to change the network name of my Admin Kit machine. Now, I cannot connect to the Admin Kit at all, even if I'm sitting at the machine trying to connect through localhost.
The PC is running Server 2003, with no firewall turned on. It's running KAV, file anti-virus only, no anti anything else.
If I change the name back to what it was before, the admin kit starts working again.
Any ideas?
Was poking around on the server from home and it appears to be a SQL database error. I'll have to check it out in the morning, because I don't have RDC enabled on that machine
QUOTE(nadams @ 3.01.2008 21:07)

Was poking around on the server from home and it appears to be a SQL database error. I'll have to check it out in the morning, because I don't have RDC enabled on that machine

It appears that the Admin Kit can no longer find it's own database because the server name changed. Where is the pointer for the database stored in the admin kit? All I need to do is edit where its looking for the database.
I've opted to rebuild the server from scratch. I've found remnants of its previous duty (a WSUS server) all over, and couldn't get KAK fixed. So, it's currently reloading Server 2003 for a nice, clean install