Can't log into Manager 4.0

[onsetcomp]

I upgraded to IPO 4.0 today and had been logging in without a problem. I installed the new Delta server software and had no errors. I went to try the new System Status software (since Call Status is no longer supported) and couldn't log into the IPO so I tried logging in again to the 4.0 manager and now it keeps displaying "Failed to log into IP Office, Cause: Access Denied".

I've rebooted and I'm positive about my name and pw. As a test I was able to log into the IPO with a copy of the 3.1 manager software using the same username and pw (I don't dare change anything with an older manager program however).

Can't be a firewall port issue since this is a local log in (and this is Win 2k without a fw).

What magic is different with the Service User Name and Service User Password in the new manager other than it sending hashed data to port 50804? Is there a "Service" that needs a password entered now?

Suggestions? Please don't reply with downgrade or bash 4.0 as every version of IPO has it's problems.

-E

 

[sizbut]

Please please please read either the Manager help file or the Technical Bulletin for IP Office 3.2. The name and password used for 3.2 upwards are different from that used for 3.1 and previous. You probably need to try the default Administrator / Administrator.

 

[onsetcomp]

Thanks for the info - the Administrator / Administrator did work for getting back in to the Manager program. Something seems to be missing though as I do not have the fields for changing the PW on my System tab (as shown in the Manager help file). I can edit and save/upload now

If I try to open the File/Advanced/Security program it too asks for a user/pw and neither the Administrator/Administrator or Administrator/orig pw will work (access denied).

I searched and read the Tech Bulletin on 3.2 and didn't read anything on the new magic default pws.

Shouldn't I be able to change pws on the System tab?

-E

 

[onsetcomp]

WooHoo - Thanks for 3.2 Tech tip. I found the default new security settings in the 3.2 orig release notice and that fixed it.

Thank you

-E