Answer the question
In order to leave comments, you need to log in
Terminal server 2k8R2 and thinstation
Good afternoon.
I just can't beat some strange glitch with connecting to the 2008R2 terminal server, I hope the community can help.
There are several thin clients with different versions of Thinstation (from 2.2 to the latest 5.1) and different rdp clients (rdesktop and freerdp). In terms of hardware, clients are old PCs, with network boot (pxe). Memory in different ways, but everywhere more than 256 (on one machine 1GB).
All this economy worked well with a terminal server under windows 2003. However, the server began to bend, they installed a new one and decided to update the software at the same time. The new server is running Windows 2008 R2 Standard. The server is in the domain, the only roles added are the terminal server and the license server for it.
And thin clients began to hang. All what is, all versions. Minutes 5-10 the user works and the session hangs up. On some clients it offers to reconnect, on some it doesn't, it just hangs. It is the rdp-client itself that hangs, thinstation works quite well for itself (you can go to the console).
I tried loading the thinstation client into icewm and calling the client from the console. Both at breakage write Connection reset by peer. There is nothing in the server log about this.
At the same time, from a laptop under ubuntu, the terminal session works all day long (remmina with the freerdp plugin).
I'm running out of ideas what else to try. Well, do not put it on XP clients with the only task - to run mstsc.
Answer the question
In order to leave comments, you need to log in
Maybe the root of the problem is changing the RDP version? It was 5.x (win2k3), it became 7.x (win2k8) and third-party clients cannot work with it “correctly”?
goo.gl/rcqSa
Some Windows XP users had similar symptoms. Thrown out of the session, and it was impossible to connect to the terminal server until you restart the computer.
It went by itself.
Similar problem. Users connect to Windows 7 virtual machines on hyper-v 3.
I myself sit on a virtual machine through a thin client, everything works fine for a couple of months without freezes.
Others even during activity have a gap and a white cross on a black background, or a cursor on the desktop background. The cursor runs reaction zero.
There are suspicions that the matter is in Windows. One changed another copy of vm, the problem went away.
I loaded a problem-free VM from a problematic thin piece of iron and session breaks repeated. From here the conclusion is that in this case it's not the OS.
Inserted into a problem thin piece of iron network from good thin. Let's see what will happen. Configs are still good too.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question