t510 Disconnecting RDP Sessions

[tditechsolution]

Hello,

Just deployed our first t510 and I have to say I was massively impressed at how easy it was!!!  We are using it to RDP to a Windows 7 VM and I was told by staff that it just disconnects during the day.  Realizing this could be any number of issues, I wanted to see if what logs or events or anything I can obtain from the t510 that would help me diagnose the issues.

Thanks!

[CraigE]

Just off the top of my head:

When we were having issues with disconnects, it turned out to be conflicting IP addresses. Make sure that you're using DHCP and that there's plenty of addresses in your scope.

Maybe not the issue, but it certainly was for us.

[tanelorn26]

Hi,
Are they disconnecting during idle time? or are they disconnecting during active use?

[rmayer]

Is the disconnection happening without an error message?
Maybe also the Server Log might give a clue.

[tditechsolution]

Thanks!  I suppose there could be a conflict, although my DHCP logs would have told me but then again, I've seen stranger things happen...I'll check though and make sure...

[tditechsolution]

That's a good question and one I should have thought of...I will find out!

[Stuckeya]

Hi,

Can you advise what operating system you are using?

The T510 can use WES2009, WES7, Thinpro or Smart Client.

For different operating systems, I may be able to suggest differnt things.

Regards

Andrew S

[EricOlsen52030]

We had the same problem.  Contacted HP support which gave these instructions which worked great:

1. On the thin client get into the Administrator mode and then open the xterminal.

2. Type regeditor and hit enter.

3. That will open the Thinpro Registry Editor.

4. Under Registry tab, select "Connection type", and under connection type select "freerdp", and under freerdp select "connections", and under connections, expand the UUID which will besimilar to {9d84f354-4e7b-4564-88a8- 9635473c20b7}, and under that highlight "timeoutwarning". On the right side, you will see the key Description.

The value will be set to 4000 by default. Change the value of timeoutwarning from 4000 to 0. Save and quit.

[NedProd]

Hi, 

I have exactly the same problem as described above,  

When i change the timeoutwarning to 0 it does not help. 

So i tried to change the timeouterror setting to 0 but that is not allowed by the system.  

Any idea on how to solve this ?  

[Stuckeya]

ThinPro and Smart Zero implement a timer feature that tests if the server is still reachable from the thin client.

The client will test and report if is has not been able to contact the server for the nominated period.

MSTSC does not implement this feature so will not give similar error.

If you are seeing this error, you have network issues between the thin client and the RDS server. Users will be impacted by these network issues and the ThinPro FreeRDP client is trying to warn you.

If you have bumped the counters out to a larger value and still see errors, you really have network issues.

Regards

Andrew S.