Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#102789 22-May-2012 16:26
Send private message

Hey guys,
I have a few users with a weird problem with terminal services. There are a few users with Windows 7/XP machines that if they leave the screen for a couple of minutes it takes about 15 seconds-30 seconds to respond. Yet on other computers it works straight away.

I'm wondering if it could be their cabling as they have had problems in this area. I'm not sure if ethernet doesn't pass frames for a while does it go into some kind of stand by mode killing the TCP session? I notice sometimes when I ping a device that hasn't passed traffic for a while the first couple of pings timeout and the 3rd onwards work at 1ms.

The server is 2008 r2 so we are using RDP 7.1. I've tried various server settings and they don't seem to change things.

Any ideas?




Speedtest 2019-10-14


Create new topic
sidkumar
84 posts

Master Geek
+1 received by user: 1


  #629283 23-May-2012 08:39
Send private message

It could be cabling. We have had weird poblems with TS/Thin Clients where sessions would freeze. When the cabling was changed from Cat3 to Cat5/e life was smooth.

Since it is not happening on all desktops, it is unlikely that it is server side issue. You mentioned Win XP/7, Is it happening on both?

The last resort would be to install wireshark on the affected PC and sniff the network traffic between the client and the server.



Regs
4066 posts

Uber Geek
+1 received by user: 206

Trusted
Snowflake

  #629599 23-May-2012 19:34
Send private message

probably something to do with the TCP autotuning options that exist in vista/7/2008. try the following for size:
http://blog.tmcnet.com/blog/tom-keating/microsoft/remote-desktop-slow-problem-solved.asp




Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

  #631070 27-May-2012 17:35
Send private message

Hey guys. I replaced the switch and router and the problem went away. I suspect it was the switch but surprising considering it was a Cisco 2900XL. The physical environment of their wiring closet is pretty bad so could have contributed maybe?




Speedtest 2019-10-14


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.