VirtualBox

Ticket #4736 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Please correct and add to 3.0.4 manual

Reported by: ToddAndMargo Owned by:
Priority: minor Component: other
Version: VirtualBox 3.0.4 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

Hi All.

Please consider the following corrections and additions to 3.0.4's manual:

Page 93:

Current: You can use any standard RDP viewer, such as the one that comes with Microsoft Windows (typically found under “Accessories” -> “Communication” -> “Remote Desktop Connection”) or, on Linux system, the standard open-source rdesktop program to connect to the virtual machine remotely.

Proposed: You can use any standard RDP viewer, such as the Microsoft Terminal Services Connector (MSTSC) that comes with Microsoft Windows (typically found by pressing <win><r> and typing "mstsc" in the run line or by browsing to "Start" -> "All Programs" -> “Accessories” -> “Remote Desktop Connection”) or, on Linux system, the standard open-source rdesktop or krdc programs to connect to the virtual machine remotely. Note: "krdc" allows for scaling.

Reason: 1) MSTSC is found directory under Accessories and not in Communication (XP, Vista, W7) 2) Those of us who use MSTSC a lot refer to it by name, "MicroSoft Terminal Services Connector" and not by “Remote Desktop Connection”. The change is to reduce confusion 3) "krdc" allows for scaling, the lack of in rdesktop being a huge annoyance.

Page 93:

Current: You should use the IP address of your host system as the server address. The VRDP server uses the standard RDP TCP port 3389 by default

Proposed: You should use the IP address of your host system as the server address. The VRDP server uses the standard RDP TCP port 3389 by default. COMMON ERROR: using the IP address of your Virtual Machine instead of your host machine.

Reason: 1) this was my screw up. I deal a lot with Terminal Services and thought I was doing the same thing. The manual is clear. I am just making it clearer for those like myself who think they are seeing something else due to their experience with Terminal Services

Page 94:

Current: hosts the default RDP port (3389) could be already used by the Windows RDP server, in this case you should choose another port for your VM(s). You should specify -N command line option with rdesktop to be able to use NumPad keys: rdesktop -N host_system_ip.

Proposed: hosts the default RDP port (3389) could be already used by the Windows RDP server, in this case you should choose another port for your VM(s) (consider using ports 5000 through 5050). You should specify -N command line option with rdesktop to be able to use NumPad keys: rdesktop -N host_system_ip[:port]. When using krdc, NumPad is automatically synchronized: krdc --window --high-quality rdp:/host_system_ip[:port] (Do not forget the "rdp:/:.) COMMON ERROR: using the IP address of your Virtual Machine instead of your host machine.

Reason: 1) Without a suggestion, you can confuse the reader, especially if he is new to ports and firewalls. And ports 5000-5050 are typically not used 2) [:port] is added to assist the reader. He can go nuts trying to figure out were to put the port without this 3) the usage comment on krdc is to assist the reader. I went nuts the first time I used krdc, until I figure out I had to use "rdp:/"

Page 96:

Current:

  1. On the client machine, fire up the RDP viewer and try to connect to the server.

Assuming a Linux client, try the following: rdesktop -a 16 -N my.host.address

Proposed:

  1. On the client machine, fire up the RDP viewer and try to connect to the server.

Assuming a Linux client, try the following: rdesktop -a 16 -N my.host.address[:port] or, krdc --window --high-quality rdp:/my.host.address[:port] COMMON ERROR: using the IP address of your Virtual Machine instead of your host machine.

Reason: 1) to assist the reader with port assignments and krdc usage. rdesktop, not supporting scaling, can be a pain in the neck at times.

Thank you for your consideration, -T

Change History

comment:1 Changed 5 years ago by ToddAndMargo

One more addition:

Page 96:

Current: (With rdesktop, the -a 16 option requests a color depth of 16 bits per pixel, which we recommend. Also, after installation, you should set the color depth of your guest operating system to the same value. The -N option requests the Num- Lock state synchronization, which is required for a correct handling of NumPad keys.)

You should now be seeing the installation routine of your guest operating system.

Proposed: (With rdesktop, the -a 16 option requests a color depth of 16 bits per pixel, which we recommend. Also, after installation, you should set the color depth of your guest operating system to the same value. The -N option requests the Num- Lock state synchronization, which is required for a correct handling of NumPad keys.)

For a Windows operating system:

<win><r> mstsc my.host.address[:port]

You should now be seeing the installation routine of your guest operating system.

Reason: 1) gives Windows users help 2) includes how to add the port number

comment:2 Changed 5 years ago by umoeller

  • Status changed from new to closed
  • Resolution set to fixed

Thank you for the suggestions. We've changed the manual accordingly; not in time for 3.0.4 and neither for 3.0.6 beta, but it should make 3.0.6 final. Thanks again!

comment:3 Changed 5 years ago by ToddAndMargo

No problem. Thank you for taking my input.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use