Run a teststand execution remotely

[tlkr01]

Hello,

I execute several testcases remotely on three computers.

A physical user logs in during the start up process of the target computer.

After two minutes the screen of the monitor turns off and the screen will also be locked. So a user has to login to use the computer again. 

It looks like the remote connection doesn't work after an idle time of about 30 minutes. I get the error that the ip Address is not accessible.

After a retry the connection works again.

Now I tried to change the identity in the properties of the NI TestStandRemoteEngine in ComponentServices/Computer/DCOM Configurations from the interactive user to a specific user. 

But with this configuration I always get the error that the ip address is not accessible.

Can someone help?

Best regards,

Thomas

[Oli_Wachno]

---

@tlkr01 wrote:

[...] 

It looks like the remote connection doesn't work after an idle time of about 30 minutes. I get the error that the ip Address is not accessible.

[...]

---

My gut feelings tell me that this is rather a WinOS issue... maybe some kind of PowerSaving mode kicks in here...

To diagnose:

• When after those 30mins you cannot access the Remote Engine anymore, what happens if you send a ping to the remote machines' IP adress?
• If it doesn't time out, will the Remote Engine become accessible afterwards?