I have this scenario
1. Server 1 is in the "EX1" domain using "EX1/User.test" to login
2. Server 2 is in the "RT1" domain using "RT1/RT_User.test" to login
Both server does not trust each others, for security concerns, that's the way we are.
We created a network path on Server 1 to be accessed by "EX1/User.test" from Server 2, and it works, when I save the credentials on Windows Credentials Manager.
Then, we create a script which will be pushing files from Server 2 to Server 1, when I run the script manually it works good, but once we add this script to windows scheduler it fails
1. Seems like windows scheduler is using the local user instead of the one stored on windows credentials, and did not find a way to change due to the other domain is not accessible/visible
2. I proceed to create a c# app, using the local user, I read the file and convert to a stream reader, and making Impersonation, login to server 2 using the credentials for it, and still failing, the error is "Bad user or wrong password", seems
like it's not accessing the other domain some way like windows does.
Any suggestion ?
