VM pro refusing admin password

[Ach_Tech]

thread940-1752493
I'm having the same issue as describe in thread940-1752493, I have a new laptop and I did install IPO manager and VM pro, I can access VM pro from my old computer but can't get it working on the new one using the same account and pwd, the web interface 7071 is also working good.
can someone give me a clue please !!!!

 

[Okkie26]

Run VM pro client as administrator

 

[Ach_Tech]

Hello Okkie26,

i did, but still can't get it running.
Thanks

 

[Okkie26]

Run the firewall batchfile on your new pc.

 

[Ach_Tech]

how do i do that???

 

[Okkie26]

Click the batchfile and follow the instructions..

 

[Ach_Tech]

i created a rule in the firewall to grant VM pro traffic through the firewall but no changes.

 

[Okkie26]

Did you ran the batchfile?

Also, which OS are you using in the new lattop?

 

[Ach_Tech]

I ran the batch but can't test the output, the account is currently locked due to too many attempts, tell you the result later

 

[Ach_Tech]

I'm using Windows 7 on the new laptop

 

[KeroChan]

Also, Make sure that VM Pro is running on all accounts, go to services, properties and log on(I think) and make sure it doesnt only run for one user

 

[Ach_Tech]

Hello,
The service runs for all the users, I ran the batchfile but the situation has not changed yet, I'm now having the same error on my old computer.
This issue is driving me crazy

 

[Okkie26]

Are you running the correct version of VM pro client?

 

[kyle555]

I ran into something where referred authentication was on but seemed to break. If you're on a Linux VMPro 9.0 or above, it's a possibility.

 

[joe2938]

rather than a rule on the firewall shut it off completely on the laptop

 

[Ach_Tech]

Okkie26, I downloaded the software from the centerApp on the IP Office UCM web interface, I did try the version 9.1.3 and 9.1.6 and experieced the same issue.
Kyle555 I tried that also but it did not solve the problem.
Joe2938 I also tried without the windows firewall but it keeps sending the same error msg

 

[joe2938]

maybe go into the compatibility settings

 

[kyle555]

I had a real tough time with that referred authentication thing. It was on, but broke, so I couldn't get in. I had to change some referred authentication flag in Linux to 'n" and then clear userlist.dat and reboot the UCM and restart voicemail.

I think it was a bug in 9.1.1 or 2 UCM.

Much like the enterprise stuff, there's a LDAP server in the UCM/Appserver now and if all passwords are default, it kicks in. If not, you get to use different per-application admin passwords.

In theory, a good idea. Until it breaks

 

[Ach_Tech]

Hello Kyle555;
writing command lines in linux OS, no very use to it, can you confirm that the issue never came back after you did that?

 

[kyle555]

No, we reinstalled
But we couldn't get into webcontrol or get to admin/root in CLI. We could log in via CLI as administrator, but when typing "admin" and being prompted again, would always fail. So, the local linux account worked, but "referred authentication" for that admin part failed.

I could winscp in as adminsitrator and remove/rename my .bash_profile and that's the thing that runs the login script that makes you in that dumb CLI and not straight linux, so I could get a bash shell and su to root locally and not thru referred authentication like the dumb cli needs. Poking around some service initialize scripts, I found that under the hood that the presence of a 0 byte file with a name like "REFERREDAUTH" or something like that is the mechanism that the services look for. If a file of that name exists, the service starts with referred authentication. Be deleting the file and restarting VMPro, I made it start with the normal authentication and then nuked my userlist.dat so I could use a default password.

On the surface, that built-in LDAP is OK, but it always breaks. Was the same on system platform for the enterprise stuff. IPOFFICE-104479 is in 9.1.4 fixed in SP7
There was another fix in 9.1.3 where there was something about needing to manually relink the crypto libraries with ldconfig in the CLI which might be in too.

All to say, depending on your release, there could be any number of problems!