Link to home
Start Free TrialLog in
Avatar of pcmm
pcmm

asked on

VB script error when using remote desektop to get to a machine

I have a user using RWW in Windows 2003 SBS.  He can connect to the server's desktop, but not his own.  when he tries to connect,  he gets the following error shortly after logging in.

VBScript: Remote Desktop Disconnect
An internal error has occurred

I've played around a bit and from other PC"s I can connect successfully to the desktop that he fails to connect.  So far I can only have him connect successfully when he uses the option to set the screen size to "1024 x 768".  When He does that the connection is stable.  The only thing I can see as possibly being the issue is the video driver.  on the "source" desktop (the one being connected to ) he is driving a 24 inch monitor and the problem PC that is attempting to connect is running a 17 inch wide screen LCD.  I can't seem to find the common ground as to what is causing the error listed above.  If anyone has run across this and rectified it,  please, some help would be appreciated
Avatar of Olaf De Ceuster
Olaf De Ceuster
Flag of Australia image

Did you update to RDP version 6? Latest version can be downloaded with windows update.
Olaf
Avatar of pcmm
pcmm

ASKER

the latest RDP update is part of SP3 for XP.  no update required that way.  I'm stuck on this one.  It's stable if he drops the resolution down to 1024x768 ( in the RDP connection) but higher resolutions cause the VB error as soon as he tries to open any application.  strange.  I can't help but suspect a video/driver issue on the client PC.  When I connect to the same client PC (the one RDP'd to) my connection is stable when using the default "Full screen" mode.

One other possibility I've noted through further testing is his response times when I ping the RWW server are in excess of 700ms.  This is on a high speed wireless internet connection ( no ADSL or Cable in the area).  I wonder if part of the issue is the connection given the excessively high latency on his connection
You can check to see if the Internet connection is the guilty party by dropping the mtu value to about 1200 and see if it still happens. Otherwise I would agree with a VGA driver problem.
Olaf
ASKER CERTIFIED SOLUTION
Avatar of ee_auto
ee_auto

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial