S
Scott
Hey folks!
I have been having an issue with rdp - a random issue really - and I
am hoping that I can find at least ONE person that has experienced the
same. In fact, I am not even looking for a solution anymore (though
any suggestions would be appreciated) ... just someone who can feel my
pain.
The issue is simply this - 10% of the time that I connect to a client
via rdp, I have to disconnect and reconnect (following a reboot of the
host), because visually at least, the performance is unbearable. When
I am working from home, I connect to my vpn server over a dsl line.
Once connected, I launch an rdp session (mstsc) and connect to one of
my machines via ip address. Roughly 1 out of every 10 connections (all
successful) will be seriously hampered by what appears to be some kind
of performance issue - simply, the result of any actions performed on
the remote machines is not immediately seen. If I click on the start
menu, it could take several minutes to see it launch (forget trying to
open a menu from there!). At this point, I have to reboot the machine
in order to be able to make a smooth, usable connection to the machine
(simply logging off and reconnecting to the machine does not work).
I have the same degree of success (or lack thereof) if I am connecting
to a machine within my own network - connecting to machines from
within the same building, floor, etc. And now, we have users in
Bangaloore, India who are making vpn connections to our network, and
once connected, launch rdp sessions (mstsc) to virtual machines. Their
experience has mirrored mine in much the same way (though I imagine
for them it is even more painful since they are connecting over a
greater distance).
So am I the only one who is having this experience? Has anyone heard
of a similar experience? I have checked event viewer, local resource
usage, and so on, and cannot find any "smoking gun" pointing to the
problem. Very frustrating!
Thanks in advance!
Scott
I have been having an issue with rdp - a random issue really - and I
am hoping that I can find at least ONE person that has experienced the
same. In fact, I am not even looking for a solution anymore (though
any suggestions would be appreciated) ... just someone who can feel my
pain.
The issue is simply this - 10% of the time that I connect to a client
via rdp, I have to disconnect and reconnect (following a reboot of the
host), because visually at least, the performance is unbearable. When
I am working from home, I connect to my vpn server over a dsl line.
Once connected, I launch an rdp session (mstsc) and connect to one of
my machines via ip address. Roughly 1 out of every 10 connections (all
successful) will be seriously hampered by what appears to be some kind
of performance issue - simply, the result of any actions performed on
the remote machines is not immediately seen. If I click on the start
menu, it could take several minutes to see it launch (forget trying to
open a menu from there!). At this point, I have to reboot the machine
in order to be able to make a smooth, usable connection to the machine
(simply logging off and reconnecting to the machine does not work).
I have the same degree of success (or lack thereof) if I am connecting
to a machine within my own network - connecting to machines from
within the same building, floor, etc. And now, we have users in
Bangaloore, India who are making vpn connections to our network, and
once connected, launch rdp sessions (mstsc) to virtual machines. Their
experience has mirrored mine in much the same way (though I imagine
for them it is even more painful since they are connecting over a
greater distance).
So am I the only one who is having this experience? Has anyone heard
of a similar experience? I have checked event viewer, local resource
usage, and so on, and cannot find any "smoking gun" pointing to the
problem. Very frustrating!
Thanks in advance!
Scott