AVAYA APP Server Cannot Login to WinSCP or Putty with Administrator Password 3

[jinxs]

Hi all,

I have set up a new application server R11.1 . I was trying to get the .wav files over that I have pre recorded though google text to voice for the auto attendants and I cannot log into putty or WinSCP with the Administrator password.

What I can log into - I can log into the application server using the Administrator password on port 7070 and 7071, I can log into the application server with manager using the Administrator password

What I connect to the app server using putty and attempt to log in using the Administrator account and password I get access denied. When I try to connect to the application server via WinSCP I am unable to connect due to incorrect password.

When I go directly to the virtual machine I am able to log in using root . I am unable to log in with the Administrator Account.

What am I missing?

Thanks in advance.

AJ-

 

[budbyrd]

Use this FAQ to get root access via other programs. It is turned off by default.

https://www.tek-tips.com/faqs.cfm?fid=8147

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[jinxs]

Well that worked like a charm. Thank you .

 

[budbyrd]

Your Welcome.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[IPGuru]

I Thought they had removed that stupidity on 11.1


Do things on the cheap & it will cost you dear

Avaya Remote Support Engineer (A.R.S.E)

 

[derfloh]

I guess with 11.1 SP1

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[budbyrd]

The big problem that I had was on an early version of 11.1 that wouldn't reload a backup from 11.0. That is when I wrote up the FAQ. I would hope they would have fixed that by now.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[critchey]

I know some versions of R11.0.4.X had this issue. I believe it was resolved with R11.0.4.5 update. Not sure if that change made it into R11.1 or not as I am still reluctant to use R11.1 much (its still crap imo).

The truth is just an excuse for lack of imagination.