New Installation - Cannot Get a Console Connection

Hello. I do have a tech. support request in as of a few days ago, but maybe someone here can help me in the meantime. I am planning to buy ADNM for my network of 25 or so computers. I am running on a demo license right now.

So, I installed ADNM on one of my servers, a Windows 2000 Advanced Server machine with dual P3-700’s and 640MB RAM. I installed ADNM with MSDE because, even though I own SQL Server 2000 and use it on others servers, this server had no SQL Server on it. I ran through the installation steps with no problems and no errors. I created a security certificate, created a mirror, etc. I rebooted following.

That is the background. Here is the problem: Now that it is installed, I want to login to the console, but my login is not working. Like I mention in the subject, this is a new installation, so I am expecting to have the default username and password work. So I am launching the console, and Detect Servers found the name of the server with ADNM on it, and for User Name I have Administrator and for Password I am entering admin. I click OK, it hangs for 20 seconds or so, and then returns with the error message: “This operation returned because the timeout period expired. Unable to login as Administrator or connection error.”

I do not think the problem has anything to do with the username or password because if I try something else as the password, it very quickly returns with “Access is denied.” I therefore think that the password is getting accepted and the problem has something to do with the connection between the client and the server. But then again, I am using the console on the same machine as the server and not going through a firewall or anything like that.

Next just to try I installed the console on my own PC. I get exactly the same behavior.

Any thoughts on what might be wrong or any troubleshooting tips? Any help would be much appreciated because I want to move away from my Symantec product as soon as possible!

Thanks.

John Caruso

I have solved this problem. Nothing was really wrong; it just took one more reboot of the server to get everything up and running, which I had not tried before because, well, it is not normal to need two reboots after an installation. But now everything is fine, and just to be sure that it was not running on some boots but not others, I rebooted my server three more times and was able to login each time, so I am satisfied now that it is going to be reliable.

JMC

That’s quite strange because… AMS installation usually doesn’t require ANY reboot (not even one). :-\

Never mind. Need to learn to RTFM. :frowning:
-Sin

Huh?
Is there a reason for reviving this 2+ years old thread? :slight_smile: :slight_smile: