cannot login - timeout

I am having trouble logging in to my AMS using the ADNM from any PC other than the one running the AMS. The error I get is:
This operation returned because the timeout period expired

Here’s the funny thing though. I get that message when I enter the correct username and password, and it takes a while to, indeed, timeout. If I enter an incorrect password, I get the following message almost immediately:
Access is denied

Can anyone tell me why my (valid) request for login times out instead of letting me in? From the same PC that the AMS is running on, I can login just fine. Not even as localhost, but by the server’s workgroup name, just as with any of the other PCs I try to login from. The login always times out.

I am running the Dec 2008 4.8.952 build of ADNM / AMS.

I have just tried uninstalling the entire AMS and reinstalling it to no avail. Still cannot log in from any remote PCs.

Any help would be appreciated! Thanks,
Josh

SOLVED!

I’m posting this just in case anyone else is having the same issue of not being able to login to the AMS through an ADNM console installed on another computer.
I suspect the problem is related to avast doing a reverse dns lookup of the remote PC trying to connect to the AMS. The reverse DNS lookup times out, and the error is sent back to the remote console.

This is occuring for me because of an infamous problem with the DLink DIR-655 firmware not doing dns relay correctly, causing such reverse dns requests to timeout instead. Reconfiguring my DNS setting on the PC running the AMS has solved the issue. I can now log in to the AMS from any PC with the adnm console installed.

Thanks for the heads up. Sort of a weird problem. Hopefully it will help someone else out!