SmartCode Solutions Web Forum




Author Message
 Posted Friday, October 28, 2005
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: Saturday, October 29, 2005
Posts: 1, Visits: 4
I am trialing a vnc manager I run a windows 2003 Server headless server, and use it to control other machines using RDP and VNC. To access the server itself  I use RDP so  seems perfect to for vncmanager, unfortunately the rdp screen size option in vncmanager wont let me change it only has one entry which is always the same as the resolution of the RDP connection to the Server itself, ie if I connect to the Server at 1280 X 1024 it forces me to use 1280 X 1024 to connect from it to all other rdp connections making me use full screen for all of them. Is this by design or is it a bug, this does not happen on the standard vanilla windows RDP client or the remote desktops management console. I have tried both 2.5x and 3.0 and they both exhibit the same problem.

Lucian

Post #582
Add to Twitter Add to Facebook
 Posted Friday, October 28, 2005
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: Yesterday @ 4:49 PM
Posts: 1,248, Visits: 2,125
Lucian,
this is not a bug. And I probably can explain why you are getting different results with the VNC Manager and native client.

In the VNC Manager the RDP connection properties screen has a combobox with resolutions. The list of the values presented in the combobox is the list of screen resolutions supported by the graphics card. And when you login to a remote computer via RDP, the Terminal Server installs a special graphics driver and reports only one resolution - the screen size of your RDP client. You can confirm it by opening the Display properties of a desktop you are viewing via RDP session. That's why you are getting the behavior you described.

On the other hand, native RDP viewer doesn't enumerate current screen resolutions supported by a graphics card and has that list hard-coded.

We are probably will move to the "hard-coded list" scheme too some time after next week to be released v3.0 release.




Kindest Regards,
SmartCode Solutions Support

Post #583
Add to Twitter Add to Facebook
 Posted Tuesday, November 15, 2005
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: Tuesday, November 15, 2005
Posts: 0, Visits: 1
I'm going to disagree and say this is a bug. When I use the built-in Remote Desktop client from Microsoft, I have a choice for the resolution that I connect to a remote system with.

I am currently trying out VNC manager and this is currently a 'deal breaker' for me. If I can't designate the resolution for the system I'm trying to RDC to, the software is pretty useless to me. I understand that VNC comes uses the resolution on the remote system, but RDC doesn't have this limitation.

Please let me know how to work around this.

Thanks,
Eric
eanderso@adobe.com
Post #613
Add to Twitter Add to Facebook
 Posted Tuesday, November 29, 2005
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: Yesterday @ 4:49 PM
Posts: 1,248, Visits: 2,125
Please let me know how to work around this.

Eric, this design flaw (I still tend not to call it a bug, since this RDP resolution behavior works the way we wanted to implement it) is going to be fixed in the v3.1 release, which should be released with-in 1.5-2 months time frame.




Kindest Regards,
SmartCode Solutions Support
Post #628
Add to Twitter Add to Facebook
 Posted Thursday, June 15, 2006
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: Yesterday @ 4:49 PM
Posts: 1,248, Visits: 2,125
The issue has been fixed in upcoming v3.5.17.0 build.



Kindest Regards,
SmartCode Solutions Support
Post #903
Add to Twitter Add to Facebook


Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse