CS IT Support Wiki - User contributions [en]

Phishing and Spoofing-Masquerading Spam

2026-07-28T20:41:22Z

Steve410: /* ...if you receive Phishing/Spoofing email at your {{red|@jhu.edu}}, {{red|@jh.edu}}, {{red|@jhmi.edu}} or other {{red|non-@cs.jhu.edu}} (but still JHU-related) email address */

{{messagebox|
type=stop|
STOP! READ HERE FIRST: This page contains instructions for '''''Computer Science Department'' affiliates''' only|
2= 
If you are '''''not affiliated''''' with the ''Johns Hopkins University '''Computer Science Department''''', this is '''''not''''' the right resource for you. Instead, please see [https://wseit.engineering.jhu.edu/get-help/reporting-spam-at-hopkins WSE IT's page on Phishing and Spam email] for instructions on reporting spam to JHU IT. 
 
If you are a Computer Science affiliate, please read on...
}}

==Phishing==

:Phishing can generally be defined as ''non''-legitimate email you receive that tries to get you to provide the sender something personal. The sender is generally ''"fishing"'' for something from you, typically, one of the following...

*'''info''' (including personal info, login credentials, or alternate contact info, e.g. cell #)
* '''money''' (including gift cards)

:What are some elements that make up phishing email?

* It could be in the form of an ''html-based'' email with a ''login page'' embedded.

* It could be something as simple as someone emailing you requesting you to ''send them info'' directly.
**And sometimes, the sender might have first created an email address, like a gmail address, that looks ''similar'' to one you might already know... but not exactly the same.
**Or it might be a ''masqueraded'' sender address. See the Spoofing (Masquerading)/Spear Phishing section below.

* A phishing email might have a ''link'' to a ''login'' or ''info request'' page.

: The above are just some examples of characteristics of phishing emails.

: (Later in this page, we will provide you instructions for reporting phishing email to the appropriate groups.)

==Be Wary...==

:It is very important that you examine ''all'' incoming email to make sure it comes from a legitimate source.

:Your mail client should provide you a way to look at ''full mail or message headers'' so you can see if what you ''think'' is a legit address in the '''From:''' part of your message is actually the ''real'' address the sender is sending from.

:If you're unsure about an email, you should look up the person's email address off an official website (my.jh.edu, etc.) and use the looked-up address to contact the email originator to confirm the email request. Remember, these ''spammers might simply change even one character in their own email address'' from an email address you might already recognize.

:If your email has a ''link'' to a web page, the text for the link you see in your email may ''not'' be where the link actually takes you. '''Examine the link carefully.''' If you're at a computer, you might be able to hover your pointer over the link to see its true URL.

:Also, look for ''spelling'' or ''grammatical'' errors in an email. Sometimes, those could indicate that the email is not from a legitimate source.

==Spoofing (Masquerading)/Spear Phishing==

:'''Spoofing''' or '''Masquerading''' is when someone sends an email and it appears to come from someone else. It could be something as simple as someone changing the descriptive text part of the ''From'' line (where you put your full name) to whatever name they want... even a name you might be familiar with. Anyone can do it. So, no matter the descriptive ''From'' name... it's most important that you check the ''email address'' the sender is using. And in these cases, you could receive spoofed/masqueraded email in the form of a phishing email. Please see above for info on phishing email.

:'''Spear Phishing''' ''extends'' the masquerading, as spear phishing is a type of phishing spam where a spammer sends email that ''appears'' to be from someone you know/trust (via masquerading), but is actually from the spammer.

:: In the case of spear phishing, the spammer tries to get you to send them information (financial, etc.), as you might think you're actually sending it to the person you know/trust (and you're really not.)

::Spear Phishing is a ''very dangerous type of email,'' and it's easy to fall prey to it. It has become a common personal information-fishing tactic. And... it's also a very easy thing for a spammer to do.

::Spammers can make the '''''From:''''' address in your email look like '''''any''''' name or email address, like that of your trusted friend, family member, co-worker, etc. However, the actual e-mail was sent by the spammer. Examining the full mail headers for your email (different methods for each email client), can help you determine the actual sender's (spammer's) email address. (And it's also possible that the spammer's email address you see in the headers might not actually belong to the spammer, but rather another email address the spammer has stolen.)

:: If you receive email that looks like it comes from someone you know, but the '''''message content seems suspicious''''' in some way, '''examine''' the mail carefully, including the mail headers for the actual sender's email address, to be sure it's legitimate. If you receive email asking for ''personally identifiable information'', ''financial info'', ''login credentials'', etc., be wary, and make sure you are replying to the legitimate audience.

::''If you are not sure if the email is legit,'' contact the "sender" by an alternate means, e.g, by phone (a phone number you know is legit) or send a separate email to that individual (do not just click reply on the suspicious email) using an email address you know for that individual.

==Additional Tips To Identify Phishing==

:It is vitally important for all of us to be aware of all emails we receive to confirm their legitimacy... especially ones that are asking or phishing for sensitive info of any kind. Here is what you must regularly do...

* ''Examine'' the ''From'' email address. Be wary of official JHU emails that come from *''non*''-JHU email addresses.

*''Compare'' the name of the person sending the email with the email address. An email from our dept chair, Randal Burns, shouldn't come from georgesmith@gmail.com (and outside address) or even gsmith1@jhu.edu (a JHU-based address.)

* ''Examine'' the content of the email for ''spelling'' or ''grammatical'' errors. Many Phishing-type emails contain both.

* ''Hover over'', but '''do not click''', any links you might find in the content of the email before you verify legitimacy of the link. Does the link look legit? Is it a non-JHU link for a JHU-related purpose? Again, verify it's legitimacy before clicking the link.

* ''Look at'' who the email is being sent ''to''... is it to you only? are there other recipients as well? Keep that in mind as you consider whether the content of the email matches the audience.

* To be even more thorough, go as far as ''check'' the email headers, which is client-dependent to view, to make sure, indeed, the email came from a reliable source.

* You might receive an email that looks like it could possibly be phishing, but at the same time, looks legit as well... especially when it appears to be from JHU. We suggest you ''look up'' the sender's name/email on ''my.jh.edu'' to make sure it's a legit email address.... and as an extra step, you might consider calling or emailing that person directly at their @jhu.edu address to confirm the legitimacy of the email. It never hurts to check.

==Reporting Phishing or Spam Emails...==
:If you receive phishing/spoofing email , especially if it's requesting you to log in to the JHU login page (or to other pages that request you to login) or requests your cellphone number or asks for a gift card or wants to know your availability, please be wary of it, ''and if you think it's not legit'', '''do ''not'' click on any included links located in that phishing mail!'''

:{{red|'''Instead...'''}} (please read '''''all''''' the below options carefully and choose the appropriate reporting option.)

===...if the mail you received is specifically a Phishing email that {{red|''looks like''}} it came from an {{red|''@cs.jhu.edu'' email address}}===

:If you receive a Phishing email that '''looks like it ''came from'' an ''@cs.jhu.edu'' email address''', we want to know about that, ''regardless'' of whether you received the email at your ''own'' @cs.jhu.edu or @jhu.edu email address. So, in this instance, please forward the Phishing email (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

:{{red|'''However...'''}}

:If the Phishing email you received does '''''not''''' look like it came ''from'' an ''@cs.jhu.edu'' email address, then please see the below two options to determine who to report the Phishing email to.

===...if you receive Phishing/Spoofing email at your {{red|''@jhu.edu''}}, {{red|''@jh.edu''}}, {{red|''@jhmi.edu''}} or other {{red|''non''-@cs.jhu.edu}} (but still ''JHU''-related) email address===

:If you receive spam (including phishing, etc.) email at your ''@jhu.edu'' (or @jhmi.edu, @jh.edu, etc.) email address ''directly'' ('''''and is not from an @cs.jhu.edu email address''''', or if you don't forward your CS email to your @jhu email), you can visit [https://wseit.engineering.jhu.edu/get-help/reporting-spam-at-hopkins WSE IT's page on Phishing and Spam email] for info on reporting spam/phishing to JHU IT. As part of the process, you'll want to forward that email (including any mail headers, if possible, by '''forwarding''' it ''as an attachment''), to [mailto:spam@jhu.edu spam@jhu.edu] (and perhaps make the Subject Line say '''SPAM'''), so that JHU can examine it and take proper action. If you're not sure if the email is legitimate, mention that in your correspondence with JHU IT as well. If you haven't heard back from JHU in a reasonable amount of time, please [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support open a trouble ticket with JHU IT.]

:'''NOTE''': Phishing mail received at your ''non-CS'' email address and that did not originate from an ''@cs.jhu.edu'' address does '''not''' need to be reported to CS IT (i.e,. support@cs.jhu.edu)

===...if you receive Phishing/Spoofing email ''directly'' at your {{red|''@cs.jhu.edu''}} email address===

:If you receive the spam/phishing email ''directly'' (i.e., not forwarded from your @jhu.edu address) at your ''CS email address'', or... if you think the email originated from an @cs.jhu.edu email address, please forward it (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

==Filtering Spam Received At Your CS Email email address==

:Please see: [[:Category:Spam Filtering At CS|Spam Filtering At CS]]

==A JHU IT-Prepared Doc To Help Its Users Identify Phishing Emails==

:JHU has put together a pdf that provides helpful information for identifying phishing emails. It's geared to those using JHU's email system, but many of its tips apply to all that receive email.

:Please read: [[Media:Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf|Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf]]

==Do's & Don'ts Of Protecting Yourself From Phishing, Malware, & Ransomware-based Emails Scams==

:In an email to the JHU public, the JHU Chief Information Security Officer at the time compiled an excellent collection of Do's and Don'ts to protect yourself from phishing, malware, and ransomware-based email scams. Click the link below to read this email.

:[[Media:BeCautiousAndAvoidPhishingAttacks.pdf|Be Cautious and Avoid Phishing Attacks - Do's & Don'ts]]

==Training Course Opportunity To Help You Identify Phishing Emails==

:JHU offers an excellent online course for the end-user regarding electronic information security and data management that includes a section on ''identifying phishing emails''.

:To get info on the course, '''you need to be on the [[VPN_-_JHU | JHU VPN]]''' or directly on a JHU network, and then browse to:

:[https://lms14.learnshare.com/dashboard/dash.home.aspx?Z=Cvz7rlERBiINCk3kFkMDWtWkTAGCTs%2fZPxff8PHH9jpE3NtAwUrdMyfZVOCTBf2m Course: JHU Electronic Information Security and Data Management]

[[Category:Spam]]

If You Receive Spam

2026-07-28T20:40:30Z

Steve410: /* If You Receive Spam Messages At Your {{red|@jhu.edu, @jhmi.edu, or @jh.edu}} email address and want to report it */

Phishing and Spoofing-Masquerading Spam

2026-07-28T20:36:35Z

Steve410:

{{messagebox|
type=stop|
STOP! READ HERE FIRST: This page contains instructions for '''''Computer Science Department'' affiliates''' only|
2= 
If you are '''''not affiliated''''' with the ''Johns Hopkins University '''Computer Science Department''''', this is '''''not''''' the right resource for you. Instead, please see [https://wseit.engineering.jhu.edu/get-help/reporting-spam-at-hopkins WSE IT's page on Phishing and Spam email] for instructions on reporting spam to JHU IT. 
 
If you are a Computer Science affiliate, please read on...
}}

==Phishing==

:Phishing can generally be defined as ''non''-legitimate email you receive that tries to get you to provide the sender something personal. The sender is generally ''"fishing"'' for something from you, typically, one of the following...

*'''info''' (including personal info, login credentials, or alternate contact info, e.g. cell #)
* '''money''' (including gift cards)

:What are some elements that make up phishing email?

* It could be in the form of an ''html-based'' email with a ''login page'' embedded.

* It could be something as simple as someone emailing you requesting you to ''send them info'' directly.
**And sometimes, the sender might have first created an email address, like a gmail address, that looks ''similar'' to one you might already know... but not exactly the same.
**Or it might be a ''masqueraded'' sender address. See the Spoofing (Masquerading)/Spear Phishing section below.

* A phishing email might have a ''link'' to a ''login'' or ''info request'' page.

: The above are just some examples of characteristics of phishing emails.

: (Later in this page, we will provide you instructions for reporting phishing email to the appropriate groups.)

==Be Wary...==

:It is very important that you examine ''all'' incoming email to make sure it comes from a legitimate source.

:Your mail client should provide you a way to look at ''full mail or message headers'' so you can see if what you ''think'' is a legit address in the '''From:''' part of your message is actually the ''real'' address the sender is sending from.

:If you're unsure about an email, you should look up the person's email address off an official website (my.jh.edu, etc.) and use the looked-up address to contact the email originator to confirm the email request. Remember, these ''spammers might simply change even one character in their own email address'' from an email address you might already recognize.

:If your email has a ''link'' to a web page, the text for the link you see in your email may ''not'' be where the link actually takes you. '''Examine the link carefully.''' If you're at a computer, you might be able to hover your pointer over the link to see its true URL.

:Also, look for ''spelling'' or ''grammatical'' errors in an email. Sometimes, those could indicate that the email is not from a legitimate source.

==Spoofing (Masquerading)/Spear Phishing==

:'''Spoofing''' or '''Masquerading''' is when someone sends an email and it appears to come from someone else. It could be something as simple as someone changing the descriptive text part of the ''From'' line (where you put your full name) to whatever name they want... even a name you might be familiar with. Anyone can do it. So, no matter the descriptive ''From'' name... it's most important that you check the ''email address'' the sender is using. And in these cases, you could receive spoofed/masqueraded email in the form of a phishing email. Please see above for info on phishing email.

:'''Spear Phishing''' ''extends'' the masquerading, as spear phishing is a type of phishing spam where a spammer sends email that ''appears'' to be from someone you know/trust (via masquerading), but is actually from the spammer.

:: In the case of spear phishing, the spammer tries to get you to send them information (financial, etc.), as you might think you're actually sending it to the person you know/trust (and you're really not.)

::Spear Phishing is a ''very dangerous type of email,'' and it's easy to fall prey to it. It has become a common personal information-fishing tactic. And... it's also a very easy thing for a spammer to do.

::Spammers can make the '''''From:''''' address in your email look like '''''any''''' name or email address, like that of your trusted friend, family member, co-worker, etc. However, the actual e-mail was sent by the spammer. Examining the full mail headers for your email (different methods for each email client), can help you determine the actual sender's (spammer's) email address. (And it's also possible that the spammer's email address you see in the headers might not actually belong to the spammer, but rather another email address the spammer has stolen.)

:: If you receive email that looks like it comes from someone you know, but the '''''message content seems suspicious''''' in some way, '''examine''' the mail carefully, including the mail headers for the actual sender's email address, to be sure it's legitimate. If you receive email asking for ''personally identifiable information'', ''financial info'', ''login credentials'', etc., be wary, and make sure you are replying to the legitimate audience.

::''If you are not sure if the email is legit,'' contact the "sender" by an alternate means, e.g, by phone (a phone number you know is legit) or send a separate email to that individual (do not just click reply on the suspicious email) using an email address you know for that individual.

==Additional Tips To Identify Phishing==

:It is vitally important for all of us to be aware of all emails we receive to confirm their legitimacy... especially ones that are asking or phishing for sensitive info of any kind. Here is what you must regularly do...

* ''Examine'' the ''From'' email address. Be wary of official JHU emails that come from *''non*''-JHU email addresses.

*''Compare'' the name of the person sending the email with the email address. An email from our dept chair, Randal Burns, shouldn't come from georgesmith@gmail.com (and outside address) or even gsmith1@jhu.edu (a JHU-based address.)

* ''Examine'' the content of the email for ''spelling'' or ''grammatical'' errors. Many Phishing-type emails contain both.

* ''Hover over'', but '''do not click''', any links you might find in the content of the email before you verify legitimacy of the link. Does the link look legit? Is it a non-JHU link for a JHU-related purpose? Again, verify it's legitimacy before clicking the link.

* ''Look at'' who the email is being sent ''to''... is it to you only? are there other recipients as well? Keep that in mind as you consider whether the content of the email matches the audience.

* To be even more thorough, go as far as ''check'' the email headers, which is client-dependent to view, to make sure, indeed, the email came from a reliable source.

* You might receive an email that looks like it could possibly be phishing, but at the same time, looks legit as well... especially when it appears to be from JHU. We suggest you ''look up'' the sender's name/email on ''my.jh.edu'' to make sure it's a legit email address.... and as an extra step, you might consider calling or emailing that person directly at their @jhu.edu address to confirm the legitimacy of the email. It never hurts to check.

==Reporting Phishing or Spam Emails...==
:If you receive phishing/spoofing email , especially if it's requesting you to log in to the JHU login page (or to other pages that request you to login) or requests your cellphone number or asks for a gift card or wants to know your availability, please be wary of it, ''and if you think it's not legit'', '''do ''not'' click on any included links located in that phishing mail!'''

:{{red|'''Instead...'''}} (please read '''''all''''' the below options carefully and choose the appropriate reporting option.)

===...if the mail you received is specifically a Phishing email that {{red|''looks like''}} it came from an {{red|''@cs.jhu.edu'' email address}}===

:If you receive a Phishing email that '''looks like it ''came from'' an ''@cs.jhu.edu'' email address''', we want to know about that, ''regardless'' of whether you received the email at your ''own'' @cs.jhu.edu or @jhu.edu email address. So, in this instance, please forward the Phishing email (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

:{{red|'''However...'''}}

:If the Phishing email you received does '''''not''''' look like it came ''from'' an ''@cs.jhu.edu'' email address, then please see the below two options to determine who to report the Phishing email to.

===...if you receive Phishing/Spoofing email at your {{red|''@jhu.edu''}}, {{red|''@jh.edu''}}, {{red|''@jhmi.edu''}} or other {{red|''non''-@cs.jhu.edu}} (but still ''JHU''-related) email address===

:If you receive spam (including phishing, etc.) email at your ''@jhu.edu'' (or @jhmi.edu, @jh.edu, etc.) email address ''directly'' ('''''and is not from an @cs.jhu.edu email address''''', or if you don't forward your CS email to your @jhu email), you can visit  [https://johnshopkins.service-now.com/nav_to.do?uri=%2Fkb_view.do%3Fsysparm_article%3DKB0012905%26sysparm_rank%3D1%26sysparm_tsqueryId%3Dbd28183433825e54ccc4ec845d5c7bb0 JHU's How-to page for reporting spam] As part of the process, you'll want to forward that email (including any mail headers, if possible, by '''forwarding''' it ''as an attachment''), to [mailto:spam@jhu.edu spam@jhu.edu] (and perhaps make the Subject Line say '''SPAM'''), so that JHU can examine it and take proper action. If you're not sure if the email is legitimate, mention that in your correspondence with JHU IT as well. If you haven't heard back from JHU in a reasonable amount of time, please [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support open a trouble ticket with JHU IT.]

:'''NOTE''': Phishing mail received at your ''non-CS'' email address and that did not originate from an ''@cs.jhu.edu'' address does '''not''' need to be reported to CS IT (i.e,. support@cs.jhu.edu)

===...if you receive Phishing/Spoofing email ''directly'' at your {{red|''@cs.jhu.edu''}} email address===

:If you receive the spam/phishing email ''directly'' (i.e., not forwarded from your @jhu.edu address) at your ''CS email address'', or... if you think the email originated from an @cs.jhu.edu email address, please forward it (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

==Filtering Spam Received At Your CS Email email address==

:Please see: [[:Category:Spam Filtering At CS|Spam Filtering At CS]]

==A JHU IT-Prepared Doc To Help Its Users Identify Phishing Emails==

:JHU has put together a pdf that provides helpful information for identifying phishing emails. It's geared to those using JHU's email system, but many of its tips apply to all that receive email.

:Please read: [[Media:Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf|Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf]]

==Do's & Don'ts Of Protecting Yourself From Phishing, Malware, & Ransomware-based Emails Scams==

:In an email to the JHU public, the JHU Chief Information Security Officer at the time compiled an excellent collection of Do's and Don'ts to protect yourself from phishing, malware, and ransomware-based email scams. Click the link below to read this email.

:[[Media:BeCautiousAndAvoidPhishingAttacks.pdf|Be Cautious and Avoid Phishing Attacks - Do's & Don'ts]]

==Training Course Opportunity To Help You Identify Phishing Emails==

:JHU offers an excellent online course for the end-user regarding electronic information security and data management that includes a section on ''identifying phishing emails''.

:To get info on the course, '''you need to be on the [[VPN_-_JHU | JHU VPN]]''' or directly on a JHU network, and then browse to:

:[https://lms14.learnshare.com/dashboard/dash.home.aspx?Z=Cvz7rlERBiINCk3kFkMDWtWkTAGCTs%2fZPxff8PHH9jpE3NtAwUrdMyfZVOCTBf2m Course: JHU Electronic Information Security and Data Management]

[[Category:Spam]]

If You Receive Spam

2026-07-28T20:35:45Z

Steve410:

If You Receive Spam

2026-07-28T20:35:27Z

Steve410:

Category:Spam

2026-07-28T20:34:25Z

Steve410:

Category:Spam

2026-07-28T20:34:09Z

Steve410:

Category:Spam

2026-07-28T20:33:33Z

Steve410:

{{messagebox|
type=stop|
STOP! READ HERE FIRST: This category is for '''''Computer Science Department'' affiliates''' only|
2= 
If you are '''''not affiliated''''' with the ''Johns Hopkins University '''Computer Science Department''''', this is '''''not''''' the right resource for you. Instead, please see  <https://wseit.engineering.jhu.edu/get-help/reporting-spam-at-hopkins WSE IT's page on Phishing and Spam email] for instructions on reporting spam to JHU IT. 
 
If you '''''are''''' a Computer Science affiliate, choose one of the sub-categories or pages listed here.
}}

Using VNC To Access CS Linux Computers

2026-07-28T19:46:26Z

Steve410: /* IMPORTANT: When you are finished with your VNC connection... */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the ''590x'' part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==''IMPORTANT:'' When you are finished with your VNC connection...==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: <code>vncserver -kill :1</code> (for the :number, use the display number from the earlier steps. {{red|And make sure you have a space between the ''-kill'' and the '':port #''}})

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-28T19:44:52Z

Steve410: /* IMPORTANT: When you are finished with your VNC connection... */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the ''590x'' part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==''IMPORTANT:'' When you are finished with your VNC connection...==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps. {{red|And make sure you have a space between the ''-kill'' and the '':port #''}})

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Wireless Networking

2026-07-28T14:35:05Z

Steve410: /* {{red|WiFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}} */

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|WiFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by [https://support.cs.jhu.edu/wiki/Contacting_WSE_IT_Support WSE IT] that discusses the ins and outs of this WiFi transition, and how to make that transition for you smoother...

:[https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition Homewood Campus Wireless Transition ]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:34:35Z

Steve410: /* {{red|WiFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}} */

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|WiFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by [https://support.cs.jhu.edu/wiki/Contacting_WSE_IT_Support WSE IT] that will discuss the ins and outs of this WiFi transition, and how to make that transition for you smoother...

:[https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition Homewood Campus Wireless Transition ]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:33:08Z

Steve410: /* {{red|WifFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}} */

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|WiFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by [WSE IT |https://support.cs.jhu.edu/wiki/Contacting_WSE_IT_Support] that will discuss the ins and outs of this WiFi transition, and how to make that transition for you smoother...

:[Homewood Campus Wireless Transition |https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:32:37Z

Steve410: /* {{red|Wifi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}} */

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|WifFi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by [WSE IT https://support.cs.jhu.edu/wiki/Contacting_WSE_IT_Support] that will discuss the ins and outs of this Wifi transition, and how to make that transition for you smoother...

:[Homewood Campus Wireless Transition https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:31:17Z

Steve410: /* {{red|Wifi Upgrades at Homewood, Starting Late Summer, 2026, And How It Could Affect Your Access}} */

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|Wifi Upgrades at Homewood Starting Late Summer, 2026. How It Could Affect Your Access...}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by WSE that will discuss the ins and outs of this Wifi transition, and how to make that transition for you smoother...

:[Homewood Campus Wireless Transition https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:30:46Z

Steve410:

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

=={{red|Wifi Upgrades at Homewood, Starting Late Summer, 2026, And How It Could Affect Your Access}}==

Starting later Summer, 2026, JHU will be performing wireless Access Point (AP) upgrades. Please see the following page hosted by WSE that will discuss the ins and outs of this Wifi transition, and how to make that transition for you smoother...

:[Homewood Campus Wireless Transition https://wseit.engineering.jhu.edu/get-help/homewood-campus-wireless-transition]

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Wireless Networking

2026-07-28T14:25:12Z

Steve410:

==JHU-provided WiFi==

'''The CS department does ''not'' provide its own wireless capability.'''

We suggest connecting to [https://it.johnshopkins.edu/it-services/network-getting-connected/wireless JHU's '''"hopkins"''' wireless network] if you would like to wirelessly connect to JHU. (We recommend you '''do not''' connect to JHU's ''"JHGuestnet"'' access point, since it limits your ability to connect to sites within JHU. So, use ''"hopkins"'' instead.) Malone Hall has many "hopkins" access points throughout the building.

Johns Hopkins has set up the enterprise wireless network for staff, faculty, and student use in the Homewood campus buildings. You should be able to accomplish normal functions such as printing, backups, sharing data, file shares, email, instant messaging, etc... from your wirelessly capable device.

JHU has built out office and classroom areas for the proper coverage and capacity within the buildings on campus. This includes Malone Hall.

==What To Do If You Have Problems Accessing JHU WiFi==

'''NOTE: CS IT does ''not'' configure or troubleshoot systems not managed by CS IT. Therefore, CS IT does ''not'' configure those systems to operate on JHU WiFi.'''

If you have issues connecting to the Johns Hopkins Wireless network, please either:
* [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support Contact the JHU Help Desk] to open a problem ticket
::or
* Send an email to [mailto:WirelessTeam@jhu.edu '''wirelessteam@jhu.edu'''] and they can determine whether you have a radio infrastructure issue or device configuration issue.

When contacting JHU for WiFi issues, be sure to tell them where on campus you are experiencing the problem. They might also require specific information about your computer, including its wireless interface's MAC address.

{{red|test}}

==When You Absolutely Have To Run Your ''Own'' WiFi Access Point In Malone Hall==

('''NOTE:''' CS IT does '''''not''''' manage WiFi connections. If you need assistance with setting up your own WiFi, please read below, and if you have questions, please contact JHU's wireless team, as mentioned above. But, read below first, if you are attempting to set up your own WiFi...)

''The following info was provided by one of the network managers from Wireless Technologies for Johns Hopkins Enterprise. We have paraphrased and reformatted it for our wiki:''

The JHU Enterprise network meets common needs, but sometimes for the sake of innovation, department WiFi routers may be justified for projects. If doing this, please follow these guidelines:

* Please turn off the 5Ghz radio on your router and use only the 2.4Ghz.

* Turn down the power to the radio to 5 mw (or as low as possible.) Turning up the power to the radio to get a more-than-reliable signal will only cause problems for others.

* Use only ''non-interfering channels'' 1,6,11 in the unlicensed ISM 2.4GHz bandwidth. Be aware that you are in a "shared environment" and please coexist with your neighbors.

* '''Do not''' use '''''channels 2,3,4,5,7,8,9,or 10''''' in the 2.4 GHz frequency band. These channels overlap with the neighboring channels and cause enough co-channel interference to render neighboring channels unusable.

* Make sure you disable DNS and DHCP services and other enterprise services at the router.

* '''Do not''' use the SSID (network names) ''"hopkins"'' or ''"JHGuestnet"''. These are what JHU advertises for their wifi. You have the right to broadcast your radio in unlicensed frequency, but Johns Hopkins Enterprise IT has the right to defend its network and its SSIDs that they advertise.

* A user-run WiFi router may be turned off at the switch port if identified as causing issues.

* '''''If you are in doubt about setting up your own WiFi, then please email [mailto:wirelessteam@jhu.edu '''wirelessteam@jhu.edu''']'''''

[[Category:Networking]]

Software Available From JHU

2026-07-24T20:49:56Z

Steve410: /* Windows 10 Education Version OS Is Available To Students */

==JHU's Software Catalog Services==

JHU offers a variety of software to members of the JHU community for work and personal use. The available software includes productivity and antivirus, amongst others. There is a cost for some software, but there are no-cost software packages available from JHU as well.

Visit [https://johnshopkins.service-now.com/serviceportal?id=sc_category&catalog_id=f70f46fa0fec6300416246ace1050e2e JHU's software page] to explore what's available. (You'll need to authenticate with your JHED ID and password.)



==WSE's Alternative To Searching The JHU Software Catalog.==

The Whiting School of Engineering IT Group has indicated that finding software on JHU's site can be tricky. So, WSE has created a site to help find the software you're looking for:

[https://wseit.engineering.jhu.edu/software-downloads https://wseit.engineering.jhu.edu/software-downloads]

From there, you can navigate to: [http://software.wse.jhu.edu http://software.wse.jhu.edu] for an easy-to-use catalog system to locate software available from JHU. You can search by manufacturer or by title. You can also search for software available from JHU for home, research, and student use. If you need assistance with WSE's Software Downloads site, please contact WSE's IT support at [mailto:wsehelp@jhu.edu wsehelp@jhu.edu]



==If You Have Issues Obtaining Software From JHU==

Please contact the JHU Software Group at [mailto:software@jhu.edu software@jhu.edu]

[[Category:Obtaining Software For Your Own Or Research Lab Computer]]

Using VNC To Access CS Linux Computers

2026-07-24T20:48:22Z

Steve410: /* IMPORTANT: When you are finished with your VNC connection */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the ''590x'' part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==''IMPORTANT:'' When you are finished with your VNC connection...==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:48:09Z

Steve410: /* When you are finished with your VNC connection */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the ''590x'' part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==''IMPORTANT:'' When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:47:22Z

Steve410: /* Starting a Windows or Linux VNC Client */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the ''590x'' part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:47:03Z

Steve410: /* Starting a Windows or Linux VNC Client */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part when inputting the port number in this step..

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:45:35Z

Steve410: /* Tunneling Your VNC Session through SSH */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal ('''but also leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running'''.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:43:02Z

Steve410: /* When you are finished with your VNC connection */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''

* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)

* Close your VNC client on your local system.

* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:42:50Z

Steve410: /* Starting a Mac VNC Client */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.

* Press '''⌘ k'''

* A ''Connect to Server'' window pops up.

* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)

* A ''Screen Sharing'' window will open.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:42:33Z

Steve410: /* Starting a Windows or Linux VNC Client */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)

* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.

* Type in the password you gave when setting up the VNC server for ugradx

* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:42:13Z

Steve410: /* Tunneling Your VNC Session through SSH */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)

* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:41:28Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.

:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:41:15Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works.
:: Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)
::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:40:43Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

::'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works. Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

:::At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:40:20Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell

* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

**'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works. Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)

***At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:39:56Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell
* ssh ''joeuser''@''ugradx''.cs.jhu.edu

* run “vncserver”

**'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works. Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)
***At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)

* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.

* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section.

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Using VNC To Access CS Linux Computers

2026-07-24T20:39:10Z

Steve410: /* First Steps... Starting the VNC Service on the Remote Computer */

VNC ([https://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing]) is supported as a method for remotely accessing our [[:Category:Linux Clients|Linux Clients]]. Because VNC does not, by default, provide a securely encrypted network connection, you will need to tunnel your connections through SSH. Instructions for doing so are below.

Please keep in mind that our Linux clients are for everyone's use and graphical programs can use many system resources. Do not leave VNC sessions running unless you're actively using them. We reserve the right to terminate idle sessions in order to free up resources for others' use.

'''In the examples used below, we want to view the desktop of the remote system, ''ugradx'' by connecting as user ''joeuser''.'''

== First Steps... Starting the VNC Service on the Remote Computer ==

To start a VNC server on the remote Linux system from your own Windows, Mac,or Linux system:

*Open Windows Powershell, Mac Terminal or Linux shell
* ssh ''joeuser''@''ugradx''.cs.jhu.edu
* run “vncserver”
**'''NOTE:''' If this is the ''first time you're running vncserver'', the first thing it will do is prompt you to enter a new password that will be used in later steps when accessing from a vnc client. You will also be asked if this new password is for view-only. You may say "n" for "no". (Note that the password is needed because of the way VNC works. Anyone who can log in to the system can connect to ''any'' VNC session running on the system, regardless of who started that session. The password ensures that only you can use your sessions.)
* Look for the line indicating a new desktop... '''New ''ugradx'':1 (''joeuser'') desktop is ugradx:1''' (or something similar.)
* Notice what the number after the colon is. e.g. '''''ugradx'':1''' We'll call the number following the ''':''' the ''display number''. You might see a different number. That's ok. You'll need the display number you get for next step.
* '''''Add''''' the display number you noticed in the prior step to value of '''5900''' to create a new port number for vncserver to use in later steps. For example, using ''':1''' from the previous step, add that value of '''''1''''' to '''5900''' to get the new value of '''5901'''. This is a port number, and we'll need this during the upcoming "tunneling-through-ssh" section. At a later time, should you need to reset your vnc password (e.g., you forgot the password), ssh back into the system and run <code>vncpasswd</code> (Currently, vncpasswd will only allow up to 8 characters, unlike regular login passwords.)

== Tunneling Your VNC Session through SSH ==

You must tunnel your VNC session through SSH for remote access to our our CS Linux computers so that your session is secured. To connect to the remote linux system, you will have to set up an SSH TCP tunnel to the port the server is listening on. That port number is '''5900''' '''''plus the X display number,''''' so it will most often be port '''5901''', as in our earlier example.

The following steps to set up tunneling should work with Windows, Mac, and Linux clients.

On your '''local''' system:

* Open a new terminal (leaving the ''other'' terminal you ran earlier to start "vncserver" still open and running.)
* From the new terminal, run '''ssh -L 5901:localhost:5901 ''joeuser''@''ugradx''.cs.jhu.edu''' and log in as you normally would to ''ugradx''. (Remember, use the port number you came up with in the earlier steps.)

The tunnel is now set. Onto starting the vnc-type client on your local system...

== Starting the VNC client on your Local system==

 
'''''IMPORTANT:'' Leave those ''two'' ssh sessions from earlier running.'''

===Starting a Windows or Linux VNC Client===

* Open your Windows or Linux VNC client on your local system. (If you don't have a VNC client, try [http://www.tigervnc.com/ TigerVNC] and the following steps will assume you're using TigerVNC.)
* Connect to "localhost:1", where ":1" is the actual display number used by your VNC server. You might've used a different display number in earlier steps. And for this step, you do not need the 590x part.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

===Starting a Mac VNC Client===
* Point your mouse on the Mac desktop (not on a mac app or window), and click to make sure the desktop is activated.
* Press '''⌘ k'''
* A ''Connect to Server'' window pops up.
* In the empty field, type in the following: '''vnc://localhost:5901''' (or whichever ''port number'' you calculated from an earlier step.)
* A ''Screen Sharing'' window will open.
* Type in the password you gave when setting up the VNC server for ugradx
* You are now connected, with the remote ugradx desktop now displayed securely on your local desktop.

==When you are finished with your VNC connection==

* Choose either ssh terminal window for which you have a connection to ''ugradx''
* Run: “vncserver -kill :1” (for the :number, use the display number from the earlier steps.)
* Close your VNC client on your local system.
* Close your SSH terminals.

[[Category:Linux Clients]]
[[Category:Software]]
[[Category:Networking]]
[[Category:SSH]]

Requesting a cs.jhu.edu Hostname in DNS

2026-07-15T20:12:32Z

Steve410:

We can create cs.jhu.edu hostnames such as ''example.cs.jhu.edu'', with approval from a faculty member.

This service is '''only''' intended to reference network systems that are hosted on '''''non''-CS''' networks. If you need an IP address on a CS subnet, see [[Requesting a Static IP Address on the CS Network]]. If you need a CS-hosted virtual machine, see [[Requesting A Virtual Machine]].

This also only applies to hostnames that end in ''cs.jhu.edu''. If you need a different domain (e.g. ''jhu.edu'' or ''jhmi.edu''), you will need to [[Contacting JHU IT Support|contact Hopkins IT]] instead.

We can create three types of DNS records:

* '''A''' records point to IP addresses; this would apply if you have a non-CS IP address that you need the hostname to point to
* '''AAAA''' records are the same, but for IPv6 addresses
* '''CNAME''' records point to other hostnames; these are often used for third-party website hosting, e.g. GitHub Pages

== Process ==

# Fill out and submit a [https://support.cs.jhu.edu/forms/dns-request DNS record request]
# If you are not a CS-affiliated faculty member, we will contact the faculty sponsor you listed to get their approval
# We will let you know when the DNS entry is set up (or, less commonly, if there's a problem with the faculty sponsor's approval)

Requesting a cs.jhu.edu Hostname in DNS

2026-07-15T20:12:14Z

Steve410:

We can create cs.jhu.edu hostnames such as ''example.cs.jhu.edu'', with approval from a faculty member.

This service is only intended to reference network systems that are hosted on '''''non''-CS''' networks. If you need an IP address on a CS subnet, see [[Requesting a Static IP Address on the CS Network]]. If you need a CS-hosted virtual machine, see [[Requesting A Virtual Machine]].

This also only applies to hostnames that end in ''cs.jhu.edu''. If you need a different domain (e.g. ''jhu.edu'' or ''jhmi.edu''), you will need to [[Contacting JHU IT Support|contact Hopkins IT]] instead.

We can create three types of DNS records:

* '''A''' records point to IP addresses; this would apply if you have a non-CS IP address that you need the hostname to point to
* '''AAAA''' records are the same, but for IPv6 addresses
* '''CNAME''' records point to other hostnames; these are often used for third-party website hosting, e.g. GitHub Pages

== Process ==

# Fill out and submit a [https://support.cs.jhu.edu/forms/dns-request DNS record request]
# If you are not a CS-affiliated faculty member, we will contact the faculty sponsor you listed to get their approval
# We will let you know when the DNS entry is set up (or, less commonly, if there's a problem with the faculty sponsor's approval)

Requesting a Static IP Address on the CS Network

2026-07-06T21:06:42Z

Steve410: /* Requesting the Static IP Address */

Before continuing, please read [[Networking at CS - Overview]] to find out more about our network configurations before continuing. (We assume you've read that page before you continue to the next sections here.)

This page deals only with the process needed to obtain a '''''static IP address''''' on the CS networks. At this time, ''static IP addresses are only granted on the CS Grad/Research Nets''.

'''''NOTES:'''''

:* If you're connecting to the CS ''Ugrad'' net, follow the instructions at [[Connecting to the CS Ugrad Net]].

:* If you're connecting to the CS ''Grad'' nets but ''do not'' need a static IP address, you may follow the simpler instructions for dynamic IP addresses at [[Connecting to the CS Grad Nets]].

:* A static IP address requires approval from a member of the CS faculty. ''Please make sure you obtain approval before sending your request.'' (See below for info on requesting a static IP address.)

==Decisions, decisions...==

You will need to decide a couple of things about your future static IP address.

* First, you must decide whether it will be on the '''public''' or '''private''' grad net. The differences are detailed in our [[Networking at CS - Overview|Networking overview]], but the most significant one is that ''private IP addresses'' can only be contacted '''''from within the Hopkins network or VPN.''''' And, please keep in mind that ''public IP addresses'' are accessible from the Internet, '''''but you are now vulnerable to unauthorized access attempts.''''' Again, please review the [[Networking at CS - Overview|Networking overview]].

* Second, you must decide how you will configure your system to use its new IP address, whether you will use '''DHCP''' to automatically receive your network configuration ''or'' whether you will '''manually''' enter all of the information yourself. We recommend using DHCP whenever possible because it reduces the amount of work you have to do and means that you'll automatically receive any network configuration changes as soon as we make them. (Your home Internet connection probably uses DHCP for its network configuration.)

== Requesting the Static IP Address ==

* Fill out the [https://support.cs.jhu.edu/forms/ip-address-application CS Network IP Address Application].
::To apply for a static IP address, you '''must''' provide your device's MAC (or NIC) address.

* We will contact the CS faculty member you list on the form to verify we can provide you a static IP address.

* Once approved, we will email you with IP address information.

* You may then use the information at [[Using a Static IP Address on the CS Grad Nets]] to set your computer up with its new IP address.

[[Category:Networking]]

Requesting a Static IP Address on the CS Network

2026-07-06T21:04:34Z

Steve410: /* Requesting the Static IP Address */

Before continuing, please read [[Networking at CS - Overview]] to find out more about our network configurations before continuing. (We assume you've read that page before you continue to the next sections here.)

This page deals only with the process needed to obtain a '''''static IP address''''' on the CS networks. At this time, ''static IP addresses are only granted on the CS Grad/Research Nets''.

'''''NOTES:'''''

:* If you're connecting to the CS ''Ugrad'' net, follow the instructions at [[Connecting to the CS Ugrad Net]].

:* If you're connecting to the CS ''Grad'' nets but ''do not'' need a static IP address, you may follow the simpler instructions for dynamic IP addresses at [[Connecting to the CS Grad Nets]].

:* A static IP address requires approval from a member of the CS faculty. ''Please make sure you obtain approval before sending your request.'' (See below for info on requesting a static IP address.)

==Decisions, decisions...==

You will need to decide a couple of things about your future static IP address.

* First, you must decide whether it will be on the '''public''' or '''private''' grad net. The differences are detailed in our [[Networking at CS - Overview|Networking overview]], but the most significant one is that ''private IP addresses'' can only be contacted '''''from within the Hopkins network or VPN.''''' And, please keep in mind that ''public IP addresses'' are accessible from the Internet, '''''but you are now vulnerable to unauthorized access attempts.''''' Again, please review the [[Networking at CS - Overview|Networking overview]].

* Second, you must decide how you will configure your system to use its new IP address, whether you will use '''DHCP''' to automatically receive your network configuration ''or'' whether you will '''manually''' enter all of the information yourself. We recommend using DHCP whenever possible because it reduces the amount of work you have to do and means that you'll automatically receive any network configuration changes as soon as we make them. (Your home Internet connection probably uses DHCP for its network configuration.)

== Requesting the Static IP Address ==

* Fill out the [https://support.cs.jhu.edu/forms/ip-address-application CS Network IP Address Application].
::To apply for a static IP address, you '''must''' provide your device's mac address.

* We will contact the CS faculty member you list on the form to verify we can provide you a static IP address.

* Once approved, we will email you with IP address information.

* You may then use the information at [[Using a Static IP Address on the CS Grad Nets]] to set your computer up with its new IP address.

[[Category:Networking]]

Networking at CS - Overview

2026-07-06T21:03:27Z

Steve410:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses static IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses static or dynamic IP addresses that are ''only accessible from within the Hopkins network (and Hopkins VPN)''.

::'''CS Undergrad Net''' (128.220.224.x) - Uses IP addresses that are ''accessible from the Internet''

:The Public and Private Grad/Research Nets are only ''physically'' accessible via network jacks in Malone Hall in CS work areas, except for the CS Undergrad Labs (Malone Hall room 122). The CS Undergrad Net is only ''physically'' accessible via network jacks in the CS Undergrad Lab. (Of course, you can access the Grad/Research Nets and the Ugrad Net systems remotely from other systems.)

:Not all network jacks are active. If you need to use a network jack but are not getting any network connection at all from it, please {{mailto|support|email us}} to ask for it to be activated.

 

==Network Jacks (Wallports) In Malone Hall==

:Network jacks may be located be under floor panels via access doors on the floor or they might be located on the wall, depending upon where you're located. Each network jack is identified with a floor number and jack number. (It is very important that any correspondence with CS IT Support or JHU Networking about a network jack include the full jack number.)

:(For those grad students working on the third floor of Malone, you might see that your floor panel access door is located under a slightly raised cabinet where the floor access door might be difficult to reach. For your convenience, there are network cables already coming out of those specific floor panels, and each of those cables is labeled with the port number.)

:Each active network jack in your Malone ''office'' will go to exactly one of those two Grad/Research networks (Public ''or'' Private Grad Net), so care will be needed to connect your computers into appropriate jacks. Again, if a jack is not currently active, you can {{mailto|support|email us}} to have it activated.

:Any given network jack can be changed from one network to the other (i.e., ''public to private'' or ''private to public'') with relatively little difficulty with an emailed request to [mailto:support@cs.jhu.edu CS Support]. We will pass on your request to JHU Networking. JHU Networking will be administering the network configurations; here is their current plan:

:* '''Even-numbered jacks''', by default, are connected to the '''''Public''''' CS Grad network, 128.220.35.x
:* '''Odd-numbered jacks''', by default, are be connected to the '''''Private''''' CS Grad network, 10.161.159.x

:'''Note 1:''' All network jacks in the CS Undergrad Lab are part of the CS Undergrad Net (128.220.224.x)

:'''Note 2:''' If you have a system that will reside in the G29 Malone ''server room'' instead, please contact CS Support, and we will help arrange your system's connections to the appropriate network, as there are no wallports in G-29.

 

== ''Public'' CS Grad/Research Network Details ==

:The '''"Public" CS Grad/Research Net''' uses static IP addresses that are directly accessible from the Internet. It is useful for servers that need to be widely accessible or for systems that people need to connect to without going through the Hopkins VPN. (For example, if you need to ssh into your work machine from out on the Internet, your work machine needs a public IP address.)

:Systems on the Public Grad Net can freely communicate with systems elsewhere on the Hopkins network, including systems on the Private CS Grad Net.

:In order to set up a system on the Public Grad Net, you will need to follow the instructions at [[Requesting a Static IP Address on the CS Network]] and indicate in your request that the IP address will be public. There is '''no''' ''dynamic IP address service'' available on the Public network. You will also need to provide your device's MAC address.

===Public IP Security Considerations===

:Please keep in mind that a system with a Public IP is exposed to the Internet. That means that '''''your system is open and vulnerable to access attempts from the outside.''''' If you're the only one who will access your system from the outside, please consider a Private IP instead, and use the VPN to put you into the JHU network so that you can access your system. If you have several outside people needing access to your system, then, yes, a Public IP is probably needed.

:And, because systems on the Public Grad Net are exposed to the Internet, they are expected to be managed in a way that preserves their security and the security of the Hopkins network. The JHU Network Security Team (part of the [http://www.it.jhu.edu/ IT@JH] group, ''not'' CS) may periodically perform security scans of systems on the Public Grad Net. If they determine that there are security problems with a system, they may disable all Internet access for that system until the problems are resolved.

===Opening Ports on the JHU Firewall===

:Some systems with a CS '''public''' IP might might want to be accessible through JHU's perimeter firewall. (CS does not maintain a departmental firewall) To have a port opened on the JHU firewall, please see: [https://support.cs.jhu.edu/wiki/Requesting_Open_Ports_on_the_JHU_Firewall Requesting Open Ports on the JHU Firewall]

 

== ''Private'' CS Grad/Research Network Details==

:The '''"Private" CS Grad/Research Net''' uses IP addresses that can only be directly accessed from either the Hopkins network or the Hopkins VPN. It is useful for systems that do not need to be accessed from the Internet, like desktop computers or printers. The private addressing used on this network helps keep the systems a little more secure, since no one on the Internet can contact them directly.

:You can connect your system to the Private Grad Net by following the instructions at [[Connecting to the CS Grad Nets]]. By default, you will receive a ''dynamic IP address''. If you need a ''static IP address'', follow the instructions at [[Requesting a Static IP Address on the CS Network]], making sure to specify that you want a ''private static IP address''.

 

==''CS Undergrad Network'' Details==

:The '''CS Undergrad Network''' is only available via wall and tabletop network jacks in Malone Hall Room 122 (the CS Collaboration Room). To connect to the CS Undergrad Net, follow the instructions at [[Connecting to the CS Ugrad Net]]. Your computer will receive a dynamic IP address. There are no static IP addresses granted for the CS Ugrad Net.

 

== Requesting a Static IP Address ==

:If you need to request a ''static IP address'', please follow the instructions at [[Requesting a Static IP Address on the CS Network]].

 

== DNS Servers to use when on the CS Network ==

:Primary DNS: '''10.200.1.1'''

:Secondary DNS: '''10.200.2.2'''

:DHCP-provided CS IPs will automatically receive the above DNS servers.

 

== General Configuration Notes ==

===Public Network (128.220.35.x, even-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''128.220.35.1'''

===Private Network (10.161.159.x, odd-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''10.161.159.1'''

 

== Security Note ==

:All computers that connect to the CS Grad/Research or Undergrad net should be at their latest security levels and should be configured to prevent viruses, etc. For antivirus software, please see the [http://it.jhu.edu/antivirus JHU Antivirus webpage].

[[Category:Networking]]

Requesting a Static IP Address on the CS Network

2026-07-06T21:00:32Z

Steve410: /* Requesting the Static IP Address */

Before continuing, please read [[Networking at CS - Overview]] to find out more about our network configurations before continuing. (We assume you've read that page before you continue to the next sections here.)

This page deals only with the process needed to obtain a '''''static IP address''''' on the CS networks. At this time, ''static IP addresses are only granted on the CS Grad/Research Nets''.

'''''NOTES:'''''

:* If you're connecting to the CS ''Ugrad'' net, follow the instructions at [[Connecting to the CS Ugrad Net]].

:* If you're connecting to the CS ''Grad'' nets but ''do not'' need a static IP address, you may follow the simpler instructions for dynamic IP addresses at [[Connecting to the CS Grad Nets]].

:* A static IP address requires approval from a member of the CS faculty. ''Please make sure you obtain approval before sending your request.'' (See below for info on requesting a static IP address.)

==Decisions, decisions...==

You will need to decide a couple of things about your future static IP address.

* First, you must decide whether it will be on the '''public''' or '''private''' grad net. The differences are detailed in our [[Networking at CS - Overview|Networking overview]], but the most significant one is that ''private IP addresses'' can only be contacted '''''from within the Hopkins network or VPN.''''' And, please keep in mind that ''public IP addresses'' are accessible from the Internet, '''''but you are now vulnerable to unauthorized access attempts.''''' Again, please review the [[Networking at CS - Overview|Networking overview]].

* Second, you must decide how you will configure your system to use its new IP address, whether you will use '''DHCP''' to automatically receive your network configuration ''or'' whether you will '''manually''' enter all of the information yourself. We recommend using DHCP whenever possible because it reduces the amount of work you have to do and means that you'll automatically receive any network configuration changes as soon as we make them. (Your home Internet connection probably uses DHCP for its network configuration.)

== Requesting the Static IP Address ==

* Fill out the [https://support.cs.jhu.edu/forms/ip-address-application CS Network IP Address Application].
** To apply for a static IP address, you '''must''' provide your device's mac address.

* We will contact the CS faculty member you list on the form to verify we can provide you a static IP address.

* Once approved, we will email you with IP address information.

* You may then use the information at [[Using a Static IP Address on the CS Grad Nets]] to set your computer up with its new IP address.

[[Category:Networking]]

Available Printers

2026-07-02T17:06:05Z

Steve410:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) ||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| ''HP'' copier (replaced the old ''Canon'' Copier''')
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' HP Copier Drivers (do ''not'' use the old Canon Drivers) for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 (3rd floor Kitchen Area) ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring pri, as of 5/28/25''nters. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]''{{red|'''NEW'''}}

Available Printers

2026-07-02T17:04:42Z

Steve410:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) ||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| ''HP'' copier (replaced the old ''Canon'' Copier''')
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 (3rd floor Kitchen Area) ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring pri, as of 5/28/25''nters. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]''{{red|'''NEW'''}}

Available Printers

2026-07-02T17:03:29Z

Steve410:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) ||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| ''HP'' copier, replaced the old ''Canon'' Copier''')
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 (3rd floor Kitchen Area) ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring pri, as of 5/28/25''nters. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]''{{red|'''NEW'''}}

Available Printers

2026-07-02T17:02:20Z

Steve410:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) ||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| ''HP'' copier, replaced the old ''Canon'' Copier''')
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 printer in the 3rd floor Kitchen Area) ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring pri, as of 5/28/25''nters. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]''{{red|'''NEW'''}}

Available Printers

2026-07-02T17:01:42Z

Steve410:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) ||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| ''HP'' copier, replaced the old ''Canon'' Copier''')
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring printers. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]''{{red|'''NEW'''}}

Notices

2026-06-11T19:52:10Z

Steve410: /* {{red|CS COMPUTING LAB AVAILABILITY}} */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==




:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) are now '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 10 through Wednesday, August 12. And the computers in that room were moved from there and are now available remote-only since June 10. On Thursday, August 13, MH-122 becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we transferred the computers from MH-122 and made them remote access-only.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab is closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) has '''''closed permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we have closed G61 (as it's being repurposed.) G61 is no longer a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that has been relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we do have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 has now become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 have being retired. (Note: Ugrad1 through Ugrad12 are currently remote-only, as another group is using MH-122 for the summer.)

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) were shut down June 1.

:* Four of the masters Linux computers (masters1 thru masters4) have been relocated to MH 316.

:* The current G61 printer has also been moved into MH 316.

:* The dept has transferred J-Card access for current CS Masters students from MH G-61 to MH 316. If there are issues, we will let you know. And if you are a CS Masters student and you have issues gaining access to MH 316, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-06-11T19:51:37Z

Steve410: /* {{red|CS COMPUTING LAB AVAILABILITY}} */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==




:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) are now '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 10 through Wednesday, August 12. And the computers in that room were moved from there and are now available remote-only since June 10. On Thursday, August 13, MH-122 becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we transferred the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab is closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) has '''''closed permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we have closed G61 (as it's being repurposed.) G61 is no longer a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that has been relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we do have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 has now become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 have being retired. (Note: Ugrad1 through Ugrad12 are currently remote-only, as another group is using MH-122 for the summer.)

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) were shut down June 1.

:* Four of the masters Linux computers (masters1 thru masters4) have been relocated to MH 316.

:* The current G61 printer has also been moved into MH 316.

:* The dept has transferred J-Card access for current CS Masters students from MH G-61 to MH 316. If there are issues, we will let you know. And if you are a CS Masters student and you have issues gaining access to MH 316, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-06-11T19:50:23Z

Steve410: /* {{red|CS COMPUTING LAB AVAILABILITY}} */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==




:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) are now '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 10 through Wednesday, August 12. And the computers in that room will be moved from there to remote-only on June 10. On Thursday, August 13, the room becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room on sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we transferred the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab is closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) has '''''closed permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we have closed G61 (as it's being repurposed.) G61 is no longer a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that has been relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we do have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 has now become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 have being retired. (Note: Ugrad1 through Ugrad12 are currently remote-only, as another group is using MH-122 for the summer.)

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) were shut down June 1.

:* Four of the masters Linux computers (masters1 thru masters4) have been relocated to MH 316.

:* The current G61 printer has also been moved into MH 316.

:* The dept has transferred J-Card access for current CS Masters students from MH G-61 to MH 316. If there are issues, we will let you know. And if you are a CS Masters student and you have issues gaining access to MH 316, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-06-11T19:43:59Z

Steve410: /* UNPLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==




:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) will be '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 10 through Wednesday, August 12. And the computers in that room will be moved from there to remote-only on June 10. On Thursday, August 13, the room becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room on sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we will be transferring the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab is closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access '''but''' '''''closing permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we will be closing G61 (as it's being repurposed.) G61 will be no longer be a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that is being relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we will plan to have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 will become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 are being retired.

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) will be shut down the morning of June 1.

:* Four of the masters Linux computers (masters1 thru masters4) have been moved into MH 316.

:* The current G61 printer has also been moved into MH 316.

:* The dept will be working on a plan to transfer J-Card access from MH G61 to MH 316. If there are issues, we will let you know.

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-06-11T19:42:13Z

Steve410: /* PLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===



{{outage
|services=masters10
|time=Friday, May 29
|summary=masters10 is only available remotely for the moment. Please use a different lab computer if you need to use one in person.
}}
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==




:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) will be '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 10 through Wednesday, August 12. And the computers in that room will be moved from there to remote-only on June 10. On Thursday, August 13, the room becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room on sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we will be transferring the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab is closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access '''but''' '''''closing permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we will be closing G61 (as it's being repurposed.) G61 will be no longer be a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that is being relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we will plan to have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 will become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 are being retired.

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) will be shut down the morning of June 1.

:* Four of the masters Linux computers (masters1 thru masters4) have been moved into MH 316.

:* The current G61 printer has also been moved into MH 316.

:* The dept will be working on a plan to transfer J-Card access from MH G61 to MH 316. If there are issues, we will let you know.

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Matlab

2026-06-02T15:38:14Z

Steve410: /* Running MATLAB in the CS Computing Labs */

==Running MATLAB in the CS Computing Labs==

'''[https://www.mathworks.com/products/matlab.html MATLAB]''' is available on the '''Linux''' machines in both the MH 122 Ugrad Lab/Collaboration Room and the MH 316 Masters Lab. MATLAB is also available on the dept's compute servers (gradx, gradz, ugradx, ugradz.)

While seated at one of the Linux machines in the CS Labs (or ssh'd into one of those systems or the compute servers), open a terminal (shell) and run <code>matlab &</code>

== MATLAB Personal Licenses ==

Students have been inquiring regarding licenses for MATLAB.

:{{red|'''NOTE:''' The CS Dept's IT group '''''does not''''' provide personal licenses for MATLAB.}}

The Whiting School of Engineering (WSE) now provides licenses that can be used on JHU-owned ''or'' personal machines. Please see: [https://software.wse.jhu.edu/siteauth/apps/software.cgi?selection=bySpecificTitle&name=Matlab https://software.wse.jhu.edu/siteauth/apps/software.cgi?selection=bySpecificTitle&name=Matlab] '''NOTE: You must be on the JHU network or be connected via the JHU VPN to access that page.''' and you might be prompted to log in with your JHED ID to access that page.

If you have questions regarding obtaining personal MATLAB licenses, please contact WSE's IT at [mailto:wsehelp@jhu.edu wsehelp@jhu.edu] or JHU's software group at [mailto:software@jhu.edu software@jhu.edu]



[[Category:Software]]
[[Category:Obtaining Software For Your Own Or Research Lab Computer]]
[[Category:Software Available On The CS Linux Clients]]