Author Topic: ADNM console stopped working (can't log in)  (Read 4243 times)

0 Members and 1 Guest are viewing this topic.

mat

  • Guest
ADNM console stopped working (can't log in)
« on: January 09, 2006, 10:04:16 AM »
I've been using ADNM for 2-3 months now, never had a problem until this morning, but now I can't connect to it anymore, the console tells me "Unable to connect as Administrator or connection error".

Nobody else has access to this so I know the password hasn't been changed. Also, the error pops up much faster when I enter an incorrect password.
I did a netstat -na and I can see that the service is listening on port 16111, and a nmap from another machine sees it as open, so it looks like the management server is up.
I can't see anything that looks relevant in the event viewer.

As far as I can tell, the only recent change to this machine has been the application of the WMF exploit fix to the system, but I don't see why this should interfere with this, and I *think* it was still working after the patch.

frederi

  • Guest
Re: ADNM console stopped working (can't log in)
« Reply #1 on: January 09, 2006, 03:35:00 PM »
We have the very same issue here every day since august :)

Try to reboot the AMS server, if you can.
I still haven't found how to avoid this daily reboot :/

mat

  • Guest
Re: ADNM console stopped working (can't log in)
« Reply #2 on: January 09, 2006, 05:07:51 PM »
I did try to reboot, also tried to restart the service, it didn't change a thing.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: ADNM console stopped working (can't log in)
« Reply #3 on: January 09, 2006, 05:10:06 PM »
How long does it take for the error message to appear?
If at first you don't succeed, then skydiving's not for you.

mat

  • Guest
Re: ADNM console stopped working (can't log in)
« Reply #4 on: January 09, 2006, 05:26:09 PM »
It took about 10 seconds if I remember correctly.
It's working again now, I didn't touch anything since the last failed attempt (no reboot, no service restart, no patches, just locked the server).