Remote Desktop

InternalPub.RemoteDesktop History

Hide minor edits - Show changes to markup

December 20, 2006, at 03:45 PM by sprinkle -
Changed lines 4-7 from:
  • To remote desktop to hermes.eecs.berkeley.edu
  • To remote desktop to ransom.eecs.berkeley.edu (in 333 Cory)
  • To login to a linux/unix machine
to:
  • To remote desktop to hermes.eecs.berkeley.edu (departmental machine)
  • To remote desktop to ransom.eecs.berkeley.edu (housed in 528 Cory)
  • To remote desktop from a linux machine
December 20, 2006, at 03:44 PM by sprinkle -
Changed lines 23-24 from:

The ransom.eecs machine is a powerful simulation machine with dual processors, a large quantity of RAM and hard drive space. It is a MS Windows Terminal Server, which means that it can support logins to the desktop for multiple users concurrently. For login information and policies, see Jon Sprinkle's Ransom.eecs page.

to:

The ransom.eecs machine is a powerful simulation machine with dual processors, a large quantity of RAM and hard drive space. It is a MS Windows Terminal Server, which means that it can support logins to the desktop for multiple users concurrently. For login information and policies, see Jon Sprinkle's Ransom.eecs page.

Changed line 26 from:
  1. Remote desktop to a machine with a static IP (e.g., hermes.eecs.berkeley.edu) specifying the entire machine name
to:
  1. Remote desktop to a machine with a static IP (e.g., hermes.eecs.berkeley.edu) specifying the entire machine name
Changed lines 29-30 from:

To remote desktop to hermes.eecs.berkeley.edu

  1. Remote desktop to hermes.eecs.berkeley.edu
to:

To remote desktop to hermes.eecs.berkeley.edu

  1. Remote desktop to hermes.eecs.berkeley.edu
December 20, 2006, at 03:43 PM by sprinkle -
Changed lines 8-9 from:

To remote desktop to your local machine, which is running WindowsXP

to:

To remote desktop to your local (Berkeley) machine, which is running WindowsXP

Changed lines 22-24 from:

Jon Sprinkle's Ransom.eecs page

to:

The ransom.eecs machine is a powerful simulation machine with dual processors, a large quantity of RAM and hard drive space. It is a MS Windows Terminal Server, which means that it can support logins to the desktop for multiple users concurrently. For login information and policies, see Jon Sprinkle's Ransom.eecs page.

To remote desktop to an on-campus machine from off campus

  1. Remote desktop to a machine with a static IP (e.g., hermes.eecs.berkeley.edu) specifying the entire machine name
  2. Once on the local machine, login to your on-campus machine using the Remote Desktop Connection

To remote desktop to hermes.eecs.berkeley.edu

  1. Remote desktop to hermes.eecs.berkeley.edu
  2. Use your EECS username/password pair to login
  3. If you were previously logged in, you will resume your session
  4. If you were not logged in before, then a new session will be created.
  5. From this point, you can access your network resources as if you were on campus (e.g., H:\ drive, or remote desktop'ing to other machines).

Using remote desktop with linux and MacOS

In most installs of linux, the program rdesktop is capable of interfacing with the Microsoft Terminal Server as a Client, and is the equivalent of mstsc, the program which is commonly known as "Remote Desktop." You should connect using a string like, (:source:) $ rdesktop rdp://ransom.eecs.berkeley.edu (:sourcend:)

December 20, 2006, at 03:40 PM by sprinkle -
Changed lines 10-12 from:
  1. If you are not on the EECS network, then you must remote desktop to an on-campus computer first
  2. If you are not using Windows XP or newer, you must download the remote desktop client for your operating system (see details from Microsoft, or download from the sww drive).
  3. Open the remote desktop client by using
to:
  • If you are not on the EECS network, then you must remote desktop to an on-campus computer first
  • If you are not using Windows XP or newer, you must download the remote desktop client for your operating system (see details from Microsoft, or download from the sww drive).
  • Open the remote desktop client by using
Changed lines 16-21 from:
  1. Choose your destination machine name (e.g., sibelius or charminar)
  2. Login using your username/password, and you will be connected to your console, if you are still logged in or no one is logged in.
    1. If someone else is logged into the machine, you may be asked to log them out, meaning that they will be forced off, without saving their files.
    2. This will normally not be the case for your desktop computer.
to:
  • Choose your destination machine name (e.g., sibelius or charminar)
  • Login using your username/password, and you will be connected to your console, if you are still logged in or no one is logged in.
    • If someone else is logged into the machine, you may be asked to log them out, meaning that they will be forced off, without saving their files.
    • This will normally not be the case for your desktop computer.
December 20, 2006, at 03:35 PM by sprinkle -
Changed lines 16-21 from:
to:
  1. Choose your destination machine name (e.g., sibelius or charminar)
  2. Login using your username/password, and you will be connected to your console, if you are still logged in or no one is logged in.
    1. If someone else is logged into the machine, you may be asked to log them out, meaning that they will be forced off, without saving their files.
    2. This will normally not be the case for your desktop computer.
December 20, 2006, at 03:35 PM by sprinkle -
Added lines 1-16:

Information on how to:

  • To remote desktop to your local machine
  • To remote desktop to a machine from off campus
  • To remote desktop to hermes.eecs.berkeley.edu
  • To remote desktop to ransom.eecs.berkeley.edu (in 333 Cory)
  • To login to a linux/unix machine

To remote desktop to your local machine, which is running WindowsXP

  1. If you are not on the EECS network, then you must remote desktop to an on-campus computer first
  2. If you are not using Windows XP or newer, you must download the remote desktop client for your operating system (see details from Microsoft, or download from the sww drive).
  3. Open the remote desktop client by using

(:source:) START->Program Files->Accessories->Communications->Remote Desktop Connection (:sourcend:)

December 20, 2006, at 03:31 PM by sprinkle -
Added lines 1-4:

Ransom Server

Jon Sprinkle's Ransom.eecs page