Personal tools
Home Classes SEASnet Terminal Server Terminal Server (Remote Desktop Connection)

Terminal Server (Remote Desktop Connection)

Remote server is restricted to students officially enrolled in engineering courses.

It is Automatically turned off at the end of each session and turned back on when the new session starts.

SEASnet Terminal Server (aka Remote Desktop Connection)

INFORMATION

SEASnet's terminal server, a Dell PowerEdge 6650 2.8GHz quad processor machine is configured for remote access to SEASnet computing resources for all HSSEAS students. The server is designed to provide access to the SEASnet lab resources from any Windows or Macintosh OS X computer with a high speed internet connection. All that is required is a terminal server client application (Windows versions from XP on have Remote Desktop built-in, MAC OS X users will have to download and install from Microsoft). Information for obtaining the terminal server client software is included below.

Computer serverThe terminal server client opens a remote window into the server that enables the user to run applications on the server from a window that appears to the remote PC as a local window on a SEASnet lab PC. Please note that all the restrictions regarding software in the SEASnet lab will apply to the terminal server as well. (Single * programs found at: http://www.seasnet.ucla.edu/classes/seasnet-computer-labs/application-on-windows-lab-pcs )

This means that all HSSEAS students can access SEASnet lab resources from your own notebook or laptop computer using the campus wireless network, from your own PC or OS X Macintosh in campus residence halls or even from home if you have a high speed internet connection such as cable modem or DSL. Performance from standard 56K modem connections is unknown.  The only restriction to Remote Desktop is that you must be registered in any Engineering Class during the current session.  Remote Desktop is automatically turned off at the end of each session / break and turned back on when the new session starts.

The server may be down occasionally as system maintenance requires. Please make sure you logout properly when you are done with your session.

How to login to the terminal server

In order to access the terminal server you will need to have Microsoft's Remote Desktop Connection software installed on your PC or Macintosh OS X.  Remote Desktop is already built-in to all Windows versions from XP Pro on.  You will need to download and install the software for other older Windows versions. You are licensed to access the server provided you are using the server for instruction or research purposes. The Remote Server is ONLY available to students enrolled in the current session.  Access is turned off "automatically" days after the session ends.  Should you require additional access time (due to extended Homework deadlines) past the end of the session, please have your instructor email Help@seas.ucla.edu and request an extension to your Remote Server access time.

If you wish to access the SEASnet lab machines from a UNIX machine you can find third-party open source software for UNIX based platforms at http://www.rdesktop.org

Logging into the terminal server (First time connection Configuration)

Once the software is installed on your system access the terminal server by following the steps below:

  1. Run the Remote Desktop Software by Clicking on Start / All Programs / Accessories / Remote Desktop OR Click on Start / Click Run / type in mstsc / Enter
  2. Connect to computer remote.seas.ucla.edu. ***IMPORTANT*** for first time users you must type in a domain name of SEASLAB before your username in the following format  seaslab\username.  Click here for directions on how to set login with the domain name.
  3. If you are having problems logging onto the remote server using Vista/Windows 7 or MAC, click here. If you get a Windows Credential Error, then you need to use the domain name as shown in step 2.
  4. Log on to SEASLAB using your SEASnet username and password (if you do not have a SEASnet account you can apply for one online at http://www.seas.ucla.edu/acctapp)

 

Users on the UCLA Campus  / Wireless / Dorm Networks

 

  1. Connecting from the UCLA Campus / Wireless / Dorm Networks - The UCLA Wireless / Dorm networks will either allow you access to ucla.edu webpages only or some will allow you access to other internet pages. The Campus Wireless / Dorm networks are not full access networks.  Cisco VPN will need to be installed / configured and used AFTER you connect to any Campus Wireless / Dorm networks in order for Remote Desktop to properly connect. 
  2. MAC OS X 10.6+ will have to configure the PPTP as listed at the below link: http://help.bol.ucla.edu/app/answers/detail/a_id/1186
  3. The Above Link for MAC OS 10.6+ PPTP requires you manually setup the Cisco VPN connection in your MAC OS Network, you'll need to download a PDF which has the necessary information for input with instructions on setting up the network. Information is found
  4. Visit http://www.bol.ucla.edu/software/ to download the Cisco VPN Client which MUST be used to access Remote Desktop from any Campus Wireless or Dorm Connections. There is both a Windows and MAC Cisco VPN Download, if your version of MAC OS doesn't have  a working Cisco VPN program, then please follow the steps given to setup a PPTP connection

INSTALLING CISCO VPN Client for your PC or MAC

  1. Browse to the BOL Webpage under software http://www.bol.ucla.edu/software for your OS Type and download / install the Cisco AnyConnect Secure Mobility Client.
  2. Windows - download / configure the Cisco AnyConnect Secure Mobility Client by following the instructions given at: http://help.bol.ucla.edu/app/answers/detail/a_id/1309
  3. MAC - from the following website https://www.bol.ucla.edu/services/vpn/all.html chose the type in installation from your current OS version.  MAC OS 10.7 - 10.8 + may require PPTP install
  4. Once installed Connect to UCLA via Cisco VPN Client and login with your UCLA credentials.
  5. Remote Desktop will now Work.

Connecting after setup from Campus / Wireless / Dorm Networks

  1. Connect as usual to your Campus / Wireless / Dorm network and verify by browsing to the internet.
  2. Run Cisco VPN / Cisco AnyConnect and login using your BOL Email credentials, you will get configuration that your connection is established.
  3. Run the Remote Desktop program and login using your SEASnet credentials. Work as usual.  When Remote session is over you can logout as usual (Click Start / Logout) This will end your Remote Desktop Connection.
  4. Disconnect connection from Cisco VPN Client.  If program is not present, then you must run program again to disconnect.  Failure to disconnect will result in all future Internet traffic to be processed via the UCLA Campus servers.  UCLA Campus monitors all internet traffic.

Setting Remote Desktop Session to allow for Drive Copy / Print to home printers

Remote Desktop can be configured to allow you to copy from your Home Desktop to the Remote Desktop and vice versa.  It can also be configured to allow printing from the Remote session to your home printers.  Please do the following BEFORE completing your Remote Desktop Login

  1. Run the Remote Desktop program
  2. CLICK on the Options / Show Options (MAC users may have to use their Remote Desktop menus)
  3. DISPLAY TAB - will allow you to set your Remote Desktop Screen size to either be FULL SCREEN or a smaller sized window
  4. LOCAL RESOURCES - Check Printers box under Local Devices and Resources - will allow you to print to any printer installed on your home laptop or computer
  5. LOCAL RESOURCES - MORE - Check Drives - will enable copy / paste functions from home to remote and/or remote to home computer.

IF YOU'VE PREVIOUSLY BEEN ABLE TO CONNECT TO REMOTE DESKTOP AND ARE NOW GETTING AN ERROR

 

  1. You may be getting an error because the domain settings are no longer in your login profile.  Please follow the instructions here to check for the domain settings.
  2. If you've previously been connected and now you can't, it may be because all Remote Connections are in use.  There is a maximum number of connections that are allowed at 1 time.  Please try again later.  If remote should still fail to work, come see us at the SEASnet Help Desk, or come login to any open lab.

You should know

  • Although SEASnet has tried to duplicate the lab environment not all software can be installed on the terminal server. Some of the older software does not work properly in this new environment.Some software is ONLY available on the Remote Servers.  To see a list of software available on the labs / remote server, please see: http://www.seasnet.ucla.edu/classes/seasnet-computer-labs/application-on-windows-lab-pcs
  • Make sure to logout when you are done with your session. To logout go to "Start -> Logoff". Idle sessions will be disconnected automatically after 15 Minutes.
  • You may print to a locally connected printer (i.e., your printer at home), but you will not be able to print to a network printer (such as a printer in the SEASnet labs). Many basic printer drivers already exist on the server; however, if the server does not recognize your printer, please email remote@seas.ucla.edu and provide us with the make and model of your printer. We will do our best to install your printer driver. To print to your local printer from an x-windows session you can use the command "elpr filename" (without the quotes).

Problems or Feedback?

Please report problems, questions or concerns to remote@seas.ucla.edu. Be sure to provide us with as much information as possible when reporting a problem. Any feedback is very much appreciated.

Document Actions