I have a proprietary application that is installed on the client and goes to our data center.
At our headquarters: This s/w authenticates against one domain in our Australian office and works fine with all their remote sites.
Our US remote sites have their own domains. We have Trust established with the US corporate domain and no corporate domain controller located at the remote sites, just VPN and T1 connections. The app still gets applicaiton failed to launched however if we right-click and force log on with the corp domain\userid it runs.
With the Trust built, you would think a user, logs in w/their corp. acct and password and chooses the corp domain (even though the PC originally resides on another domain) and access the application but it does not.
any suggestions on fixing that besides joining the client to the corporate domain?
Thanks
At our headquarters: This s/w authenticates against one domain in our Australian office and works fine with all their remote sites.
Our US remote sites have their own domains. We have Trust established with the US corporate domain and no corporate domain controller located at the remote sites, just VPN and T1 connections. The app still gets applicaiton failed to launched however if we right-click and force log on with the corp domain\userid it runs.
With the Trust built, you would think a user, logs in w/their corp. acct and password and chooses the corp domain (even though the PC originally resides on another domain) and access the application but it does not.
any suggestions on fixing that besides joining the client to the corporate domain?
Thanks
