Remote Desktop:
Question: I am struggling with the remote desktop interface again. I don’t think it is just because it is falling asleep. I am only really able to get 1-2 clicks in before it freezes again and I have to wait another 5 minutes for it to decide to kick me off so I can log on again. When I return to the interface it is where I left it, but it kicks me off again soon after. I am never going to finish the lab at this rate. Is this happening to anyone else? Any tips to fix this?
Response Per IT Staff: There is no internal forced timeout/disconnection mechanism within the ArcGIS Remote Access pool, but as an entirely network-dependent service, any network interruption lasting more than a few seconds can cause a disconnect. If a session becomes disconnected while using it, then typically some external force precipitates it: network drops, inadequate bandwidth, wireless interference, VPN drop, computer sleep (which would cause a network drop), etc. There is an auto-logout timer of 20 minutes where a Windows session will log out after a session disconnect, but again, nothing that would force a disconnect in and of itself. Users working from home and experiencing disconnect issues are encouraged to examine their home network setup; wireless users in particular may have better experience when using a wired connection (most home routers have at least one Ethernet jack), particularly when wireless connectivity is weak, of low bandwidth, or in an area with high interference or many competing signals. The individual computer’s wireless card, age, protocol capabilities (802.11a/b/g/n and so forth), software drivers, antennae, etc. can all play a role in this, so using a wired connection can eliminate a lot of these variables. If the connection is more stable over a wired connection, then an audit of the home wireless environment would be required to know what issues were present in order to return to wireless use.