RemoteApp Published App won't accept credentials
We are running RemoteApp on a Windows 2008 R2 server. We are publishing 3 apps, one of which is Excel. We have 5 office worldwide. One of our USA offices is having problems connecting to the Published Apps. We are able to logon to RemoteApp with no problem. When we launch any of the Published Applications, we are prompted for user credentials. When we enter the credentials, we are receiving an error, "The logon attempt failed." The clients are all running Windows 7 and IE11. Something seems to have changed for this site, because we were able to launch Published Apps from this network previously. Published Apps are working for all other locations.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Do you have local Domain controllers to authenticate users? Did passwords recently change and are all domain controllers fully syncronized?
Scott gorcester
Scott gorcester
Thanks for your reply Scott:
I do have a local Domain Controller. No passwords have changed. Domain Controllers are fully synchronized.
Another interesting thing, I just tested two of my 2k3 member servers, and I am able to connect to the Remote App without any problem. Both of these servers are are authenticating on the same domain controller as my Windows 7 machines.
I do have a local Domain Controller. No passwords have changed. Domain Controllers are fully synchronized.
Another interesting thing, I just tested two of my 2k3 member servers, and I am able to connect to the Remote App without any problem. Both of these servers are are authenticating on the same domain controller as my Windows 7 machines.
Look at this......
While troubleshooting a problem with the SSO-feature lately, we got an error message saying “The logon attempt failed”.
The solution turned out to be rather simple. While the default logon page for RD Web Access indicates “Domain/user name” for the user name field, using only the user name works fine:
This works fine as long as your not using RD Gateway and SSO, then the error message mentioned will occur when trying to start a RemoteApp.
When RD Gateway and SSO are being used, you must supply the domain as part of the user name (domain user name), else the SSO-feature will break.
While troubleshooting a problem with the SSO-feature lately, we got an error message saying “The logon attempt failed”.
The solution turned out to be rather simple. While the default logon page for RD Web Access indicates “Domain/user name” for the user name field, using only the user name works fine:
This works fine as long as your not using RD Gateway and SSO, then the error message mentioned will occur when trying to start a RemoteApp.
When RD Gateway and SSO are being used, you must supply the domain as part of the user name (domain user name), else the SSO-feature will break.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial