CS IT Support Wiki - User contributions [en]

Gmail as a CS Mail Client

2026-09-30T16:24:40Z

Pip:

Occasionally, people in the department want to have email from their [[:Category:Mail|CS email account]] appear in their Gmail account.

''We do not recommend doing this'', and we cannot offer support for people who choose to do it anyway. Every approach involves tradeoffs that can be mitigated by using a mobile or desktop mail client or [[Webmail|our webmail]].

Especially if you are a member of the CS faculty, we strongly recommend that you conduct all CS-related business using either your CS email address or your JHU email address. Using a non-CS, non-JHU email address makes it much easier for malicious actors to attempt to impersonate you over email with your colleagues and students. (For example, if you've been in the department for some time, you've probably received an email from a random Gmail account fraudulently claiming to be Randal Burns and asking you to buy gift cards for him. The attacker can fake Randal's name on the email, but they cannot fake a cs.jhu.edu email address.)

Nevertheless, below are some resources we've found for people who want to do this despite the above advice.

== Gmail as an IMAP Client ==

'''Note''': The principal drawback of this approach is that your CS account password will be stored on Google's servers. This increases the risk of your account being compromised.

Google has a support article “[https://support.google.com/mail/answer/21289 Add another email account on your computer]”. You can follow its instructions to have Gmail fetch mail from your CS account, using the appropriate CS [[:Category:Receiving Email|mail client instructions]]. As with any mail client, we recommend using IMAP, not POP, to retrieve your email.

You should also follow Gmail's instructions for [https://support.google.com/mail/answer/22370 sending emails from a different address] and information from our [[:Category:Sending Email|mail sending instructions]] so that emails relating to CS can go out with your CS email address attached. If you do this, make sure your email is going through the CS mail server, after a login with your CS account. If you don't do that, other mail servers will reject your email as fraudulent.

== Forwarding Your Email to Gmail ==

Although it is possible to forward your CS mail to Gmail using our [[Forwarding Mail|mail forwarding instructions]], '''you should not do this'''. Mail servers use a number of mechanisms to verify the authenticity of email, and simple mail forwarding often causes the forwarded messages to fail that validation. If you simply forward your CS email to Gmail, you will lose an indeterminate number of emails sent to you by non-CS people.

[[Category:Mail]]

Notices

2026-09-17T20:08:27Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2026-09-17T13:52:45Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2026-09-17T13:32:36Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2026-09-17T13:31:57Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2026-09-16T18:37:15Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Mailman at CS

2026-09-14T13:22:35Z

Pip: /* Things You Might Want to Change */

==INTRO==

:Most user-controlled mailing lists in the CS Department are now run on our [https://wiki.list.org Mailman] system. (Older CS mailing lists are [http://www.greatcircle.com/majordomo/ Majordomo]-based.)

'''NOTE: Although the CS IT Support Team can create the actual mailing list, we do not manage the content of user-requested mailing lists. That is managed by the user or their designee.'''

==Subscribing to a CS Mailman Mailing Lists ==

: CS Mailman mailing lists visibility are either public or private.

:* '''Public List:''' The public can see what lists are available and manage their subscriptions to those lists at:

::: https://lists.cs.jhu.edu/mailman

:* '''Private List:''' List does not display on the public list of CS Mailman lists.
:** For a Mailman private list, subscribers will have to know what the list's name is. The list's name is in the list's email address, so if one sends email to and receives email from "''listname@cs.jhu.edu''", the list's name would be "''listname''".
:** Subscribers to private Mailman mailing lists can manage their subscription information for such a list at:

::::<tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/listinfo/''listname''</tt>

===Getting Help With Your Mailman list Subscription===

* If a subscriber needs to contact the owner of a CS Mailman list, they can email the list owner at: <tt>''listname''-owner@cs.jhu.edu</tt>

* General documentation on subscribing to Mailman lists can be found at: The [http://www.gnu.org/software/mailman/users.html GNU Mailman User Documentation]

The rest of this page is mostly concerned with information for list owners; people who run a CS-hosted mailing list.

== Requesting A CS-Hosted Mailing List To Be Created ==

*'''Currently, you must be a CS faculty or staff member (or CS student that has approval from the student's instructor) to request a CS mailing list.'''

* Please fill out our [https://support.cs.jhu.edu/forms/mailing-list-request mailing list request form].
** We will let you know when your new mailing list is ready.
** We will have some default settings in place for you. You'll be able to configure/customize your list settings after you receive the list.

== Administering (Configuring/Customizing) Your New CS Mailman Mailing List ==

:General Mailman List Administration Documentation can be found online at: [http://www.gnu.org/software/mailman/mailman-admin/index.html http://www.gnu.org/software/mailman/mailman-admin/index.html]

:However, we're also including some basic list admin information below that is geared to the CS-based Mailman mailing lists.

::'''NOTE:''' If a list administrator needs additional assistance with managing their CS Mailman mailing lists, please email CS IT Support at: [mailto:support@cs.jhu.edu support@cs.jhu.edu].

:For purposes of illustration, all of the examples here will use a list named "''listname''".

:After we have created your new mailing list, you will receive an email with your list administration password and links to the webpages for managing your mailing list. In general, a list named "''listname''" can be managed from the webpages at:

:: <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>

: You should go there now and make sure it's configured the way you will want it.

=== How Your List is Configured by Default ===

:For the most part, the default settings for your list should be reasonable. Specific settings you might want to change are mentioned below.

:Broadly speaking, new lists are configured in the following ways by default:

:* They're set up as discussion lists, which means that anyone who is subscribed to the list may post to the list and have their post sent to all of the other subscribers. ''Only'' list subscribers can send to the list; non-subscribers will have any attempted posts held until a moderator can review them.
:* Lists are largely private by default. They're not advertised publicly (on the [https://lists.cs.jhu.edu/mailman/listinfo "list of lists" page]); their archives are only available to list subscribers; and the subscriber list is only available to list moderators.
:* Moderator approval is required before anyone can subscribe to the list. Most lists will want to change this setting, but it at least prevents people from using the list until the owner is ready.

=== Things You Should Change ===

:On the "General Options" page, which is the first page you'll see when you go to <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>, there are a few items you should definitely change:

:* '''owner''' - This is your email address and the email addresses of anyone else who will have complete control over the list (if you're sharing list administrative duties).
:* '''moderator''' - If you will have list moderators, put their email addresses here. A moderator has less access than a list owner. Moderators can approve postings to the list, clear out spam, and do other housekeeping tasks but cannot reconfigure the list's settings.
:* '''description''' - A short (one-line) description of what your mailing list is for.
:* '''info''' - A longer description of what your mailing list is for.

=== Things You Might Want to Change ===

:Also in the General Options section are these settings, which will probably be okay if you leave them as they are, but which you might want to change to personalize your mailing list:

:* '''subject_prefix''' - The text that the mailing list will add to the beginning of the Subject: line for any email sent to the list. We highly recommend that if you have a value here you put it in [square brackets].
:* '''welcome_msg''' - This works a bit like the ''info'' field described above, but contains a bit of information that will be sent to any new subscriber to your mailing list. If you want to send welcome messages, you'll also have to set '''send_welcome_msg''' to "Yes".

:On the "Privacy Options > Subscription rules" page, you can control how public your mailing list will be. The most notable settings are:

:* '''advertised''' - If you set this to "Yes", your mailing list will appear on the list of CS-based lists at https://lists.cs.jhu.edu/mailman.
:* '''subscribe_policy''' - The default setting, "Require approval", will require you (or a designated list admin or moderator) to approve each subscription request. This maximizes list privacy, but is more work than most lists require. Setting it to "Confirm" allows anyone to subscribe if they want to.

:On the "Archiving Options" page, you can control whether Mailman keeps a history of all the emails sent to your list. (Note that nothing can prevent list subscribers from keeping their own archives if they so choose.) The default setting for '''archive_private''', "private", will only allow list subscribers to see the archives. If you change that to "public", anyone on the Internet will be able to see them. If you simply set the '''archive''' option to "No", no history will be kept.

=== Special Settings for Announcement Lists ===

Many lists we host are announcement lists; many people subscribe to these lists, but only a few people have permission to send emails to the list. This is how you set up your mailing list to work similarly:

On the "Privacy options > Sender filters" page (which you get by clicking "Privacy options" in the top menu then clicking "Sender filters"), set the following options:

* '''default_member_moderation''' - Set to "Yes".
* '''member_moderation_notice''' - This is the message that people who are subscribed but not allowed to post will receive if they try to post anyway. We suggest something along the lines of, "This mailing list is only for announcements; you cannot send email to it."
* '''accept_these_nonmembers''' - This is a list of email addresses of people who are allowed to post to the list without being subscribed to it. This would be used for someone who would send messages but who would not necessarily need to receive a copy of every email sent to the list. ('''Note''': This ''only'' works for people who are ''not'' subscribed to the list. For people who are list members, you need to follow the instructions below.)

To allow a list subscriber to send to the list, go to the "Membership Management > Membership List" page, find the entry for the person you want to allow (either by finding them in the table or by putting their email address into the search field and clicking "Search"), uncheck their box in the "mod" column, and click the "Submit Your Changes" button.

===If You Receive a ''"1 <your list> moderator request(s) waiting"'' Message===

Should you receive a message that indicates you have one (or more) "moderator requests waiting", that typically means you are the owner of a Mailman mailing list, and a message arrived that you have to moderate. Specifically, this message means that someone tried to send an email to the list, but the sender wasn't on the list of approved senders. When that happens, the list is configured to hold onto the message and let the list owners/moderators know about it. Then, as the list owner (or one of the list owners), you can follow the link provided and decide what to do about the message.


== About Mailman Passwords ==

===Administrative Password===

: By default, your list has one ''administrative password''. Anyone who knows that password can log in and change anything about your list configuration. This means that the way you give someone access to your list is simply to tell them the password. If you need to remove administrative access for someone, you will have to go to the administrative interface at <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>, go to the "Passwords" page, change the administrator password, and then share the new password with anyone else who still needs to have administrative access.

===Moderator Password===

: If you want, you can set a ''moderator password''. Anyone with the moderator password will be able to manage the process of getting emails to or keeping them from the list: they can approve or discard held messages and they can block people from posting to the list. They cannot change much else about the configuration of the list.

===Administrative Interface Password Requests===

: When the ''administrative interface'' asks for a password, either the administrative password or the moderator password can be used. If the moderator password is used, only the moderator functions will be active.

== Spam Management ==

:It is a fact of life that eventually someone will try to send spam to your mailing list. Unfortunately, it's also likely that you will eventually have someone who should be allowed to post to the list try to send an email from an email address that the list doesn't recognize. There is no way for Mailman to discriminate between these two scenarios; all it knows is that it got email for a list from someone who isn't affiliated with that list. There are a number of list options available to help you, the list admin, deal with these sorts of situations.

:By default, if the mailing list gets an email from someone who isn't subscribed to the list then it will hold on to the email until a list admin or moderator comes along and decides what to do with the email. List admins and moderators will get daily emails with lists of held messages and links to the "pending moderator requests" page:

::<tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admindb/''listname''</tt>

:That page makes it pretty easy to deal with spam. You can easily skim through the list of held emails, click to approve any that should be let through, and then click one button to delete the rest.

:On the "General Options" page, the '''admin_immed_notify''' setting can be changed to "Yes", which will send you an email every time a message is held for review. You can reply to that email with instructions for Mailman. This setting is good for people who like using email to manage their list, want fast turnaround for held messages, and don't mind the additional emails.

:On the "Privacy options > Sender filters" page, the '''generic_nonmember_action''' setting controls what to do when the list receives an email from an non-subscribed address. The default setting, "Hold", is ''strongly recommended'' so that you can help out people who should be able to send to the list but were blocked for some reason. If, however, you're getting a lot of spam and can live with the future management difficulties, you can set it to "Discard". (The other two settings are ''really'' not recommended for most lists. "Accept" will end up sending a lot of spam to the mailing list, and "Reject" will bother the people that the spammers are pretending to be.)

[[Category:Mailing Lists]]

Mailman at CS

2026-09-11T17:57:13Z

Pip: Mailman's web interface is on a separate server now

==INTRO==

:Most user-controlled mailing lists in the CS Department are now run on our [https://wiki.list.org Mailman] system. (Older CS mailing lists are [http://www.greatcircle.com/majordomo/ Majordomo]-based.)

'''NOTE: Although the CS IT Support Team can create the actual mailing list, we do not manage the content of user-requested mailing lists. That is managed by the user or their designee.'''

==Subscribing to a CS Mailman Mailing Lists ==

: CS Mailman mailing lists visibility are either public or private.

:* '''Public List:''' The public can see what lists are available and manage their subscriptions to those lists at:

::: https://lists.cs.jhu.edu/mailman

:* '''Private List:''' List does not display on the public list of CS Mailman lists.
:** For a Mailman private list, subscribers will have to know what the list's name is. The list's name is in the list's email address, so if one sends email to and receives email from "''listname@cs.jhu.edu''", the list's name would be "''listname''".
:** Subscribers to private Mailman mailing lists can manage their subscription information for such a list at:

::::<tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/listinfo/''listname''</tt>

===Getting Help With Your Mailman list Subscription===

* If a subscriber needs to contact the owner of a CS Mailman list, they can email the list owner at: <tt>''listname''-owner@cs.jhu.edu</tt>

* General documentation on subscribing to Mailman lists can be found at: The [http://www.gnu.org/software/mailman/users.html GNU Mailman User Documentation]

The rest of this page is mostly concerned with information for list owners; people who run a CS-hosted mailing list.

== Requesting A CS-Hosted Mailing List To Be Created ==

*'''Currently, you must be a CS faculty or staff member (or CS student that has approval from the student's instructor) to request a CS mailing list.'''

* Please fill out our [https://support.cs.jhu.edu/forms/mailing-list-request mailing list request form].
** We will let you know when your new mailing list is ready.
** We will have some default settings in place for you. You'll be able to configure/customize your list settings after you receive the list.

== Administering (Configuring/Customizing) Your New CS Mailman Mailing List ==

:General Mailman List Administration Documentation can be found online at: [http://www.gnu.org/software/mailman/mailman-admin/index.html http://www.gnu.org/software/mailman/mailman-admin/index.html]

:However, we're also including some basic list admin information below that is geared to the CS-based Mailman mailing lists.

::'''NOTE:''' If a list administrator needs additional assistance with managing their CS Mailman mailing lists, please email CS IT Support at: [mailto:support@cs.jhu.edu support@cs.jhu.edu].

:For purposes of illustration, all of the examples here will use a list named "''listname''".

:After we have created your new mailing list, you will receive an email with your list administration password and links to the webpages for managing your mailing list. In general, a list named "''listname''" can be managed from the webpages at:

:: <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>

: You should go there now and make sure it's configured the way you will want it.

=== How Your List is Configured by Default ===

:For the most part, the default settings for your list should be reasonable. Specific settings you might want to change are mentioned below.

:Broadly speaking, new lists are configured in the following ways by default:

:* They're set up as discussion lists, which means that anyone who is subscribed to the list may post to the list and have their post sent to all of the other subscribers. ''Only'' list subscribers can send to the list; non-subscribers will have any attempted posts held until a moderator can review them.
:* Lists are largely private by default. They're not advertised publicly (on the [https://lists.cs.jhu.edu/mailman/listinfo "list of lists" page]); their archives are only available to list subscribers; and the subscriber list is only available to list moderators.
:* Moderator approval is required before anyone can subscribe to the list. Most lists will want to change this setting, but it at least prevents people from using the list until the owner is ready.

=== Things You Should Change ===

:On the "General Options" page, which is the first page you'll see when you go to <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>, there are a few items you should definitely change:

:* '''owner''' - This is your email address and the email addresses of anyone else who will have complete control over the list (if you're sharing list administrative duties).
:* '''moderator''' - If you will have list moderators, put their email addresses here. A moderator has less access than a list owner. Moderators can approve postings to the list, clear out spam, and do other housekeeping tasks but cannot reconfigure the list's settings.
:* '''description''' - A short (one-line) description of what your mailing list is for.
:* '''info''' - A longer description of what your mailing list is for.

=== Things You Might Want to Change ===

:Also in the General Options section are these settings, which will probably be okay if you leave them as they are, but which you might want to change to personalize your mailing list:

:* '''subject_prefix''' - The text that the mailing list will add to the beginning of the Subject: line for any email sent to the list. We highly recommend that if you have a value here you put it in [square brackets].
:* '''welcome_msg''' - This works a bit like the ''info'' field described above, but contains a bit of information that will be sent to any new subscriber to your mailing list. If you want to send welcome messages, you'll also have to set '''send_welcome_msg''' to "Yes".

:On the "Privacy Options > Subscription rules" page, you can control how public your mailing list will be. The most notable settings are:

:* '''advertised''' - If you set this to "Yes", your mailing list will appear on the list of CS-based lists at https://lists.cs.jhu.edu/mailman.
:* '''subscribe_policy''' - The default setting, "Require approval", will require you (or a designated list admin or moderator) to approve each subscription request. This maximizes list privacy, but is more work than most lists require. Setting it to "Confirm" allows anyone to subscribe if they want to.

:On the "Archiving Options" page, you can control whether Mailman keeps a history of all the emails sent to your list. (Note that nothing can prevent list subscribers from keeping their own archives if they so choose.) The default setting for '''archive_private''', "private", will only allow list subscribers to see the archives. If you change that to "public", anyone on the Internet will be able to see them.

=== Special Settings for Announcement Lists ===

Many lists we host are announcement lists; many people subscribe to these lists, but only a few people have permission to send emails to the list. This is how you set up your mailing list to work similarly:

On the "Privacy options > Sender filters" page (which you get by clicking "Privacy options" in the top menu then clicking "Sender filters"), set the following options:

* '''default_member_moderation''' - Set to "Yes".
* '''member_moderation_notice''' - This is the message that people who are subscribed but not allowed to post will receive if they try to post anyway. We suggest something along the lines of, "This mailing list is only for announcements; you cannot send email to it."
* '''accept_these_nonmembers''' - This is a list of email addresses of people who are allowed to post to the list without being subscribed to it. This would be used for someone who would send messages but who would not necessarily need to receive a copy of every email sent to the list. ('''Note''': This ''only'' works for people who are ''not'' subscribed to the list. For people who are list members, you need to follow the instructions below.)

To allow a list subscriber to send to the list, go to the "Membership Management > Membership List" page, find the entry for the person you want to allow (either by finding them in the table or by putting their email address into the search field and clicking "Search"), uncheck their box in the "mod" column, and click the "Submit Your Changes" button.

===If You Receive a ''"1 <your list> moderator request(s) waiting"'' Message===

Should you receive a message that indicates you have one (or more) "moderator requests waiting", that typically means you are the owner of a Mailman mailing list, and a message arrived that you have to moderate. Specifically, this message means that someone tried to send an email to the list, but the sender wasn't on the list of approved senders. When that happens, the list is configured to hold onto the message and let the list owners/moderators know about it. Then, as the list owner (or one of the list owners), you can follow the link provided and decide what to do about the message.


== About Mailman Passwords ==

===Administrative Password===

: By default, your list has one ''administrative password''. Anyone who knows that password can log in and change anything about your list configuration. This means that the way you give someone access to your list is simply to tell them the password. If you need to remove administrative access for someone, you will have to go to the administrative interface at <tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admin/''listname''</tt>, go to the "Passwords" page, change the administrator password, and then share the new password with anyone else who still needs to have administrative access.

===Moderator Password===

: If you want, you can set a ''moderator password''. Anyone with the moderator password will be able to manage the process of getting emails to or keeping them from the list: they can approve or discard held messages and they can block people from posting to the list. They cannot change much else about the configuration of the list.

===Administrative Interface Password Requests===

: When the ''administrative interface'' asks for a password, either the administrative password or the moderator password can be used. If the moderator password is used, only the moderator functions will be active.

== Spam Management ==

:It is a fact of life that eventually someone will try to send spam to your mailing list. Unfortunately, it's also likely that you will eventually have someone who should be allowed to post to the list try to send an email from an email address that the list doesn't recognize. There is no way for Mailman to discriminate between these two scenarios; all it knows is that it got email for a list from someone who isn't affiliated with that list. There are a number of list options available to help you, the list admin, deal with these sorts of situations.

:By default, if the mailing list gets an email from someone who isn't subscribed to the list then it will hold on to the email until a list admin or moderator comes along and decides what to do with the email. List admins and moderators will get daily emails with lists of held messages and links to the "pending moderator requests" page:

::<tt><nowiki>https://lists.cs.jhu.edu</nowiki>/mailman/admindb/''listname''</tt>

:That page makes it pretty easy to deal with spam. You can easily skim through the list of held emails, click to approve any that should be let through, and then click one button to delete the rest.

:On the "General Options" page, the '''admin_immed_notify''' setting can be changed to "Yes", which will send you an email every time a message is held for review. You can reply to that email with instructions for Mailman. This setting is good for people who like using email to manage their list, want fast turnaround for held messages, and don't mind the additional emails.

:On the "Privacy options > Sender filters" page, the '''generic_nonmember_action''' setting controls what to do when the list receives an email from an non-subscribed address. The default setting, "Hold", is ''strongly recommended'' so that you can help out people who should be able to send to the list but were blocked for some reason. If, however, you're getting a lot of spam and can live with the future management difficulties, you can set it to "Discard". (The other two settings are ''really'' not recommended for most lists. "Accept" will end up sending a lot of spam to the mailing list, and "Reject" will bother the people that the spammers are pretending to be.)

[[Category:Mailing Lists]]

Trouble Logging In Using VS Code With Remote SSH Plugin

2026-09-01T20:01:35Z

Pip: Redirected page to Visual Studio Code#If you have problems with Remote SSH

#REDIRECT: [[Visual Studio Code#If you have problems with Remote SSH]]

[[Category:Troubleshooting]]
[[Category:SSH]]
[[Category:Software]]

Visual Studio Code

2026-09-01T20:00:57Z

Pip:

'''VS Code ''' is a common desktop coding environment. We support the use of the VS Code Remote SSH plugin to connect to our [[:Category:Linux Clients|Linux clients]], but we recommend a few specific settings.

== Recommended VS Code Settings for the CS Linux Clients ==

First, ''use the latest release of VS Code''. Older versions may have issues that have been addressed in newer releases.

Second, open your settings and make sure the following are set:

* Remote.SSH: '''Use Flock''' should be ''checked''
* Remote.SSH: '''Remote Server Listen On Socket''' should be ''checked''

== If you have problems with Remote SSH ==

''First'', make sure the two above settings are set. If "Use Flock" is not checked, VS Code may have problems including problems with only setting itself up partially. If "Remote Server Listen On Socket" is not checked, you might have problems with the Remote SSH plugin's dynamic port forwarding.

''Second'', make sure you can use your computer's native [[Connecting to CS Systems with SSH|SSH]] client (''not'' VS Code) to connect to our system. If your non–VS Code SSH client doesn't work either, you can contact {{mailto|support}} with the output of your SSH client for assistance.

''Third'' (if your system's SSH client works, but VS Code's Remote SSH plugin does not), try resetting the server-side VS Code configuration:

<ol>
<li> Exit all of your VS Code sessions. (Close all your VS Code windows.) </li>
<li> Delete the <code>.vscode-server</code> directory in your grad or ugrad home directory. You can do that by SSHing to the Linux client you used with VS Code and running:
: <kbd>rm -fr ~/.vscode-server</kbd>
: If the directory doesn't exist, that's okay.
: If you get an error message similar to "device or resource is busy", run the command <kbd>pkill -u $(id -u) -f vscode</kbd> then run the <code>rm</code> command above again.</li>
<li> Try connecting to the CS Grad or Ugrad system again.</li>
</ol>

''Finally'', you can contact {{mailto|support}} for further assistance. Please include the following information:

* The system you're connecting from
* The system you're trying to connect to
* Whether you've tried using SSH without VS Code to connect to our system
* A copy or screenshot of the SSH output in VS Code

[[Category:SSH]]
[[Category:Software]]

Visual Studio Code

2026-09-01T19:58:45Z

Pip: Created page with "'''VS Code ''' is a common desktop coding environment. We support the use of the VS Code Remote SSH plugin to connect to our Linux clients, but we..."

'''VS Code ''' is a common desktop coding environment. We support the use of the VS Code Remote SSH plugin to connect to our [[:Category:Linux Clients|Linux clients]], but we recommend a few specific settings.

== Recommended VS Code Settings for the CS Linux Clients ==

First, ''use the latest release of VS Code''. Older versions may have issues that have been addressed in newer releases.

Second, open your settings and make sure the following are set:

* Remote.SSH: '''Use Flock''' should be ''checked''
* Remote.SSH: '''Remote Server Listen On Socket''' should be ''checked''

== If you have problems with Remote SSH ==

''First'', make sure the two above settings are set. If "Use Flock" is not checked, VS Code may have problems including problems with only setting itself up partially. If "Remote Server Listen On Socket" is not checked, you might have problems with the Remote SSH plugin's dynamic port forwarding.

''Second'', make sure you can use your computer's native [[Connecting to CS Systems with SSH|SSH]] client (''not'' VS Code) to connect to our system. If your non–VS Code SSH client doesn't work either, you can contact {{mailto|support}} with the output of your SSH client for assistance.

''Third'' (if your system's SSH client works, but VS Code's Remote SSH plugin does not), try resetting the server-side VS Code configuration:

<ol>
<li> Exit all of your VS Code sessions. (Close all your VS Code windows.) </li>
<li> Delete the <code>.vscode-server</code> directory in your grad or ugrad home directory. You can do that by SSHing to the Linux client you used with VS Code and running:
: <kbd>rm -fr ~/.vscode-server</kbd>
: If the directory doesn't exist, that's okay.</li>
<li> Try connecting to the CS Grad or Ugrad system again.</li>
</ol>

''Finally'', you can contact {{mailto|support}} for further assistance. Please include the following information:

* The system you're connecting from
* The system you're trying to connect to
* Whether you've tried using SSH without VS Code to connect to our system
* A copy or screenshot of the SSH output in VS Code

[[Category:SSH]]
[[Category:Software]]

VSCode

2026-09-01T19:39:05Z

Pip: Redirected page to Visual Studio Code

#REDIRECT: [[Visual Studio Code]]

VS Code

2026-09-01T19:38:48Z

Pip: Redirected page to Visual Studio Code

#REDIRECT: [[Visual Studio Code]]

Notices

2026-08-31T13:35:17Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2026-08-28T22:17:50Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Notices

2026-08-28T20:00:28Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Notices

2026-08-27T16:34:21Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Notices

2026-08-26T19:54:52Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Resource Limits on the Linux Clients

2026-08-26T19:52:10Z

Pip: /* Memory Usage */

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''16 GiB'''. This limit applies only to the non-lab systems like ugradv, ugradx, and ugradz. The lab systems (ugrad1 through ugrad12) have no imposed limit, so it's possible for a buggy program to use up all of a system's RAM. If one lab computer is unresponsive, you can simply use a different one until we're able to fix the problem. (But, email [mailto:support@cs.jhu.edu support@cs.jhu.edu] to let us know you experienced an issue, and include the system name as well.)

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 16 GiB of RAM will hit the limit, but so will running eight programs that each use 2 GiB of RAM.

The limit also applies to memory reservations, whether or not they're actively being used. This means if you <code>mmap</code> a file, the entire file size will count towards this limit, even though blocks from the file are only paged into RAM on demand.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same account is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]

Resource Limits on the Linux Clients

2026-08-26T19:51:59Z

Pip: /* Memory Usage */

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''16 GiB'''. This limit applies only to the non-lab systems like ugradv, ugradx, and ugradz. The lab systems (ugrad1 through ugrad24) have no imposed limit, so it's possible for a buggy program to use up all of a system's RAM. If one lab computer is unresponsive, you can simply use a different one until we're able to fix the problem. (But, email [mailto:support@cs.jhu.edu support@cs.jhu.edu] to let us know you experienced an issue, and include the system name as well.)

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 16 GiB of RAM will hit the limit, but so will running eight programs that each use 2 GiB of RAM.

The limit also applies to memory reservations, whether or not they're actively being used. This means if you <code>mmap</code> a file, the entire file size will count towards this limit, even though blocks from the file are only paged into RAM on demand.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same account is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]

Linux Clients on the CS Undergrad Net

2026-08-26T19:51:23Z

Pip:

The following is a list of Linux machines available for students, faculty, researchers, or staff. These Linux machines can be accessed remotely via [[Connecting to CS Systems with SSH|<code>ssh</code>]], <code>scp</code> or [[VNC]].

If you're working remotely, although you are welcome to log into '''''any''''' of our Linux clients, it's recommended that you use ''ugradv.cs.jhu.edu'' and ''ugradx.cs.jhu.edu'', as those can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so ''anything you can do on one of them can be done on all of the others'', too.

===NOTES===

:* All Ugrad Net systems end with '''''.cs.jhu.edu''''' as in, '''''ugrad1.cs.jhu.edu'''''

:* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Ugrad Net machines ''are different than'' those on the [[Linux Clients on the CS Grad/Research Net|Grad]] systems.

:* Ugrad Net linux clients have [[Disk Quotas|disk quotas]] on the Ugrad home directories.

:* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* '''These Linux clients are primarily used for ''educational (coursework)'' purposes.''' Therefore, since you are sharing these systems (CPU, memory, etc.) with other users, please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

 

==Available Ugrad Linux Systems==

* '''ugrad1''' through '''ugrad12'''
** Standard ''Fedora 44'' Linux clients
** Located in [[:Category:Labs|the CS Undergraduate Lab (Malone 122)]]
** Each client has 8 cores (one 4-core i7 CPU with hyperthreading) and 16 GiB RAM.
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (already installed) for coursework.
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''

* '''ugradv''' and '''ugradx'''
** ''Fedora 44'' Linux-based compute servers
** 32 cores (one 16-core Xeon 6511P CPU with hyperthreading), 256 GiB RAM
** Two NVIDIA L4 Tensor Core GPUs
** ''Only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers''

* '''ugradz'''
** ''Fedora 44'' Linux-based compute server.
** 32 CPU cores, 48 GiB RAM.
** ''Only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers''
** Only accessible from the Hopkins network or VPN; not accessible directly from the Internet.

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

Linux Clients on the CS Grad/Research Net

2026-08-26T19:47:21Z

Pip:

The following is a list of Linux machines available for ''grad'' students, faculty, researchers, or staff on the ''Grad/Research Net''. These Linux machines can be accessed remotely via <code>ssh</code>, <code>scp</code>, or [[VNC]].

If you're working remotely, although you are welcome to log into any of our Linux clients, it's recommended that you use either ''gradv.cs.jhu.edu'' or ''gradx.cs.jhu.edu''; those systems can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so anything you can do on one of them can be done on all of the others, too.

===NOTES===

* All Grad/Research Net systems end with '''''.cs.jhu.edu''''' as in, '''''masters1.cs.jhu.edu'''''

* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Grad Net machines ''are different than'' those on the [[Linux Clients on the CS Undergrad Net|Ugrad]] systems.

* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

* You are ''sharing these systems (CPU, memory, etc.) with other users,'' so please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

* '''These Linux clients are primarily used for ''educational (coursework)'' purposes and for ''light research'' that does not impair CPU/memory/disk resources for others.''' Therefore, since you are sharing these systems (CPU, memory, disk space etc.) with other users, please make sure that you do not overload the processors on these systems nor store large files or large amounts of files on these systems. When your are completed running your processes, please make sure you stop those processes.
 

==Available Grad/Research Systems==

* '''masters1''' through '''masters4'''
**''Fedora 44'' Linux clients
** Malone Hall 316 (the CS Masters/MSSI Lab)
** Each client has 8 cores (one quad-core Xeon E3-1240 CPU with hyperthreading) and 16 GiB RAM
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (both already installed) for coursework
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradv''' and '''gradx'''
** ''Fedora 44'' Linux-based compute servers
** 24 cores (one 12-core Xeon 6505P CPU with hyperthreading), 128 GiB RAM
** An NVIDIA L4 Tensor Core GPU
** ''Only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradz'''
** ''Fedora 44'' Linux-based compute server
** 32 CPU cores, 48 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

Linux Clients on the CS Grad/Research Net

2026-08-26T19:46:11Z

Pip:

The following is a list of Linux machines available for ''grad'' students, faculty, researchers, or staff on the ''Grad/Research Net''. These Linux machines can be accessed remotely via <code>ssh</code>, <code>scp</code>, or [[VNC]].

If you're working remotely, although you are welcome to log into any of our Linux clients, it's recommended that you use ''gradx.cs.jhu.edu'', as it can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so anything you can do on one of them can be done on all of the others, too.

===NOTES===

* All Grad/Research Net systems end with '''''.cs.jhu.edu''''' as in, '''''masters1.cs.jhu.edu'''''

* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Grad Net machines ''are different than'' those on the [[Linux Clients on the CS Undergrad Net|Ugrad]] systems.

* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

* You are ''sharing these systems (CPU, memory, etc.) with other users,'' so please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

* '''These Linux clients are primarily used for ''educational (coursework)'' purposes and for ''light research'' that does not impair CPU/memory/disk resources for others.''' Therefore, since you are sharing these systems (CPU, memory, disk space etc.) with other users, please make sure that you do not overload the processors on these systems nor store large files or large amounts of files on these systems. When your are completed running your processes, please make sure you stop those processes.
 

==Available Grad/Research Systems==

* '''masters1''' through '''masters4'''
**''Fedora 44'' Linux clients
** Malone Hall 316 (the CS Masters/MSSI Lab)
** Each client has 8 cores (one quad-core Xeon E3-1240 CPU with hyperthreading) and 16 GiB RAM
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (both already installed) for coursework
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradv''' and '''gradx'''
** ''Fedora 44'' Linux-based compute servers
** 24 cores (one 12-core Xeon 6505P CPU with hyperthreading), 128 GiB RAM
** An NVIDIA L4 Tensor Core GPU
** ''Only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradz'''
** ''Fedora 44'' Linux-based compute server
** 32 CPU cores, 48 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

Matlab

2026-08-26T19:42:28Z

Pip:

==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 (gradv, gradx, gradz, ugradv, 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]]

GPUs In The CS Linux Clients

2026-08-26T19:41:47Z

Pip:

The majority of the CS [[:Category:Linux Clients|Linux clients]] contain '''Nvidia GPUs''' with support for [[CUDA On The CS Linux Clients|'''CUDA''']] and OpenCL.

These systems include:

* ''masters1'' through ''masters4'' (Masters' Lab; Quadro K620 GPUs)

* ''ugrad1'' through ''ugrad12'' (Ugrad Lab; GeForce GTX 645 GPUs)

* ''gradv'', ''gradx'', ''ugradv'', and ''ugradx'' (Remote-access compute systems; L4 Tensor Core GPUs)

''However'', our alternate compute server Linux clients, ''gradz'' and ''ugradz'' (that are only remotely available through ssh or scp) '''''do not''''' have CUDA-capable GPUs in them. You'll notice that CUDA software ''is'' available on those machines merely because we share the same configuration amongst all our Linux client systems, whether they have the same hardware or not.

==Details About Our GPUs==

To see specific details about our GPU, log into any of our labs' Linux computers referenced above and run:

:'''nvidia-smi'''

==How To Use The GPUs==

We do not have specific info on the "how-tos" of using our GPUs, because... how you use our GPUs will very much depend on which library or framework you're using and what you want to do with them. Generally, CS courses that make use of the GPUs will cover how to make use of them in the course materials.

We recommend that you consult documentation for the specific GPU library you want to use. For example if you plan to use CUDA with our GPUs (and we believe several CS students do), you can check CUDA's own documentation. Another common framework is PyTorch (which itself uses CUDA, but also provides a lot of other functionality). Our systems also support OpenCL, in case you want to write code that is portable across more GPU architectures than just the Nvidia GPUs we have. And your instructor might be able to assist you as well.

[[Category:Linux Clients]]

Notices

2026-08-26T18:27:27Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Requesting a Static IP Address on the CS Network

2026-08-25T17:37:30Z

Pip: /* Now We Can Continue... */

==First... Read Our Networking Overview Document==
Before continuing with the rest of this page, please 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.)

==Now We Can Continue...==

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'' net''s'' 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]].

:* If you need a cs.jhu.edu hostname but ''not'' an IP address on one of the CS subnets, follow the instructions at [[Requesting a cs.jhu.edu Hostname in DNS]].

:* A static IP address requires approval from a member of the [https://www.cs.jhu.edu/faculty 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 cs.jhu.edu Hostname in DNS

2026-08-25T17:35:15Z

Pip:

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)

[[Category:Networking]]

Notices

2026-08-25T16:20:55Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Notices

2026-08-24T17:52:02Z

Pip: /* Linux Clients Not Accessible During Upgrades */

Notices

2026-08-24T17:50:21Z

Pip:

Python on the CS Webservers

2026-08-12T20:06:09Z

Pip: /* Python Versions */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2026, the Linux clients use Python 3.14 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

If you need a package that is not supported on our web servers' default Python version, you can use the versioned Python executable to set up the virtual environment. For example, if you had a package that needed Python 3.11 or later, you could run <kbd>python3.11 -m venv <var>/path/to/venv/directory</var></kbd>. If you run a Python program in such a venv, it will use the version of Python you used to set up the venv, even if the program starts with {{code|#!/usr/bin/env python3}} or {{code|#!/usr/bin/env python}}.

See the previous section for which versions of Python are available on both our web servers and our Linux clients.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Python on the CS Webservers

2026-08-12T20:05:58Z

Pip: /* Python Versions */ Web servers don't have Python 3.13.

Forwarding Mail

2026-07-16T17:35:01Z

Pip: /* Setting Up Forwarding For Your CS Address */

==INTRO==

:When you receive a CS Linux account, you're also receiving an email address in the form of '''''yourusername''@cs.jhu.edu'''

:You might choose to automatically forward any email you receive at this CS address to some other preferred address (for example, to your @jhu.edu address or to an address outside of JHU.) And currently (subject to change) we do allow you to configure your CS email to automatically forward, however...

==Consider ''Not'' Forwarding Your CS Email To ''Outside'' of JHU==

:Both JHU and WSE IT have highly recommended you '''do not''' automatically forward your JHU-based email to '''''outside''' of JHU''. Please refer to [https://wseit.engineering.jhu.edu/redir-email/ WSE's article on redirecting email].

:However, for some of you, this might not be feasible. At this time, CS email can be forwarded to both other JHU-based addresses '''''or''''' to sites outside of JHU.

==Setting Up Forwarding For Your CS Address==

* If you're a CS ''grad student, professor, researcher, postdoc or staff member,'' log into one of our [[Linux Clients on the CS Grad/Research Net]] and cd to your home directory.

:: or

* If you're a CS ''ugrad student,'' log into one of our [[Linux Clients on the CS Undergrad Net]] and cd to your home directory.

:: then...

* In the top level of your home directory, create a '''<code>.forward</code>''' file (don't forget the "'''.'''" ) using an editor.

* Put your preferred email account address as the only line in the <code>.forward</code> file.

* Save changes.

:Now, incoming mail to your CS address should be forwarded to your preferred address.

== Things to be Aware of ==

:We have noticed that Gmail sometimes ignores email messages that have been forwarded back to the account that sent them. Most of the time this isn't usually a problem, but if you're forwarding to a Gmail account and you want to test the forwarding, you should ''not'' use the same Gmail account to send your test email. Test it with an email from another source, or have a friend send you an email.

==When Your CS Account Is Removed...==

:'''IMPORTANT!''' When your affiliation with the CS department is complete and your CS account is removed (See: [[CS Account Removal]]), '''''any email forwarding that you have configured will be removed.'''''

:'''''CS is no longer forwarding emails''''' for those no longer currently affiliated with the CS department.

[[category:Mail]]

Requesting a cs.jhu.edu Hostname in DNS

2026-07-08T14:49:26Z

Pip: Created page with "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 ho..."

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)

Lab And Other Website Hosting

2026-06-03T14:04:17Z

Pip: /* File Storage Method */

==INTRO==

In addition to hosting [[Creating a Webpage|personal webpages]] accessed as <code><nowiki>http://www.cs.jhu.edu</nowiki>/~<var>account</var></code>, we can also host entire websites, with custom URLs (e.g. <code><nowiki>http://</nowiki><var>your-lab-name</var>.cs.jhu.edu</code>).

:'''''This service is only available to CS Faculty.'''''

To request a hosted website, you must decide on a ''website name'' and ''file storage method'' for the website files. Both choices are ''described below''. Then you need to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with a complete description of your request.

If you choose the [[#Dedicated Website Account|Dedicated Website Account file storage method]] ''described below'', you'll also need to ''print out'', ''fill out'', and ''sign'' a [https://support.cs.jhu.edu/forms/vhost-form.pdf Computer Science Department ''Website'' Account Form].  You can then scan and email it to [mailto:support@cs.jhu.edu support@cs.jhu.edu]

{{red|'''NOTE:''' CS IT does '''not''' create or edit webpage content for users. You are responsible for your own website design and troubleshooting.}}

== Website Name Options ==

This choice governs what URLs people use for accessing your website. There are four options available.

=== www.cs.jhu.edu Subdirectory ===

:Your website name can exist as part of the <code>www.cs.jhu.edu</code> website, e.g. <code>www.cs.jhu.edu/<var>your-lab</var></code>.

=== CS Domain Name ===

:Your website name can exist under the <code>cs.jhu.edu</code> domain, e.g. <code><var>your-lab</var>.cs.jhu.edu</code>.

:If you request this option, we will set it up for you when we set up your website. We will set up '''SSL''' access (i.e.'''''https://'''''-style URLs) as well.

=== JHU Domain Name ===

:You can also set up a website name within the <code>jhu.edu</code> domain, e.g. <code><var>your-lab</var>.jhu.edu</code>.

:We ''cannot'' set this up for you automatically. If you want this option, we'll put you in contact with the appropriate people who manage the <code>jhu.edu</code> domain; you'll have to request the name from them. Once the hostname is set up for you, we'll set up '''SSL''' access (i.e., '''''https://'''-style URLs) as part of the website.

=== Other Domain Name ===

:Finally, you can use any second-level domain you want to register, e.g. <code><var>your-lab</var>.org</code>.

:If you chose this option, you will be entirely responsible for making and maintaining the domain registration. If you want '''SSL''' ('''''https://''''' URLs), we'll provide you an appropriate Certificate Signing Request, but you will have to obtain the certificate and then send it to us.

== File Storage Method ==

There are ''two'' options for how the website's files will be stored on our systems. Both require CS Linux accounts.

=== Personal Account ===

:The simplest approach is to simply store the website's files under your ''personal'' CS account. In this case, you create a directory to hold the files (e.g. <code>~/<var>my-lab-website</var></code>) and just [mailto:support@cs.jhu.edu email support] to tell us what directory you want to use.

:This approach works best '''if you are the ''only'' person''' who will be managing the files for the website.

:Note that with this approach, if your account is removed (see [[CS Account Removal]] for the policies related to that process), the website will be removed at the same time.

=== Dedicated Website Account ===

:Alternately, we can create a special account dedicated to your website. It will have its own home directory for the website's files. You and anyone else who manages the files will be given access to the account's home directory. A CS Grad Net account is required for access; if you or the other people need an account, please see our [[Obtaining CS Computer Accounts]] page.

:For this option, you will need to fill out and sign a [https://support.cs.jhu.edu/forms/vhost-form.pdf website account form].

:This approach is best when '''more than one person needs to be able to manage the website's files''', or when the person managing those files will change over time.

:The website will remain for as long there is someone affiliated with the department who is responsible for the website's maintenance.

[[Category:Webpages and Webservices]]

Available Printers

2026-06-02T16:08:07Z

Pip:

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) '''''{{red|NEW!}}'''''||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.''|| {{red|('''''NEW'' ''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 (''{{red|'''NEW'''}} 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]]

Obtaining CS Computer Accounts

2026-06-02T16:07:30Z

Pip:

:{{red|CS IT will handle many computer account issues now '''remotely''', via email (never send passwords through email, though!) or Zoom. So, please make sure you have [https://support.cs.jhu.edu/wiki/Zoom Zoom] installed on your computer or mobile device. And, plan to have your J-Card in-hand. (If no J-Card, you'll at least need a picture ID.) If you have any questions, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] }}



A CS Linux account provides:

:* A Linux shell and disk space for ''course work'' and ''light research''.

:* A CS-based [[:Category:Mail | email address]].

:* Directory space to [[:Category:Webpages_and_Webservices | host a webpage]].

'''''NOTES:'''''
* A CS Linux account ''is not'' related to a JHED account. (JHED accounts are part of JHU's own accounts system.)

* The [[Linux_Clients_on_the_CS_Grad/Research_Net | CS ''Grad Net'' Linux client computers]] and [[Linux_Clients_on_the_CS_Undergrad_Net | ''Ugrad Net'' Linux client computers]] are similar in terms of the software/applications installed, ''but they use '''separate''' user accounts. ''

* All CS accounts '''must''' be pre-approved by a CS faculty member from this [https://www.cs.jhu.edu/faculty CS Faculty member list] '''''unless'''''...
** a student is a direct CS student (i.e., a CS PhD, CS Masters, or CS Undergrad student)
** a student is taking a CS course taught by a [https://www.cs.jhu.edu/faculty CS Faculty member] and is on a course list provided to CS IT Support directly by the faculty member or by CS Academic Advising.
** the account applicant has some other CS affiliation and will therefore need approval by CS Dept administration.

 
Below, you'll see the process to obtain a CS ''Linux'' account for access to the [[:Category:Computers_Available_on_the_CS_Network|Computers Available on the CS Network]].

==Obtaining The CS Account Form==

You can download a copy of the [https://www.cs.jhu.edu/formfiles/newacctform.pdf CS Linux/Windows Account Form] from our [[Forms]] page.

Once you've downloaded it, come back to this page for further instructions.

 

==Filling Out The CS Account Form==




Please print and fill out the form '''''COMPLETELY''''', and '''sign both sides of the form'''. ''Please be legible.''

(Some of you might edit the PDF directly, but you still need to sign both sides of the form before submitting the form.)

You then need to obtain any [[#Signatures|authorized signatures]]. {{red|(Please see our updates to obtaining signatures in that section below.)}}

Additionally, make sure you list your [http://www.it.johnshopkins.edu/services/email JHU-assigned e-mail address] on the account form. Many of our CS mailing lists use that address.

There is a section there for ''Permanent (non-JHU/non-CS) Email Address''. Please fill that in. Note: If you will not be accessing your CS email directly, we encourage you then to [https://support.cs.jhu.edu/wiki/Forwarding_Mail forward] your CS email to an address you do check frequently (whichever is your preferred email address... it could be your permanent email address or your @jhu.edu email address) so that you do not miss any emails that may be sent to your @cs.jhu.edu email address. 

Under “Local Address”, please list your local resident street address while attending (or working at) JHU. 

 

===Indicating Your JHU Affiliation Type===

The CS Account form requires you to choose your JHU affiliation.

===== Grad Student, Faculty/Instructor, Staff, Researchers, or Postdoc CS Computer Accounts =====
:On the CS Linux/Windows Account Form, if you're a ''CS Grad student'' or ''CS Faculty/Instructor'', ''Staff'', ''Researcher'' or ''Postdoc'', please make sure you've checked off that you want a '''Linux Grad''' account, which will supply you with your CS e-mail address and an account to access the [[Linux Clients on the CS Grad/Research Net|Grad/Research Net Linux]] computers that are supported by CS IT (including the Linux computers in the Master's Lab).

:If you are teaching or TA'ing a CS Undergrad Course, and, as a result, also '''''require''''' a CS Ugrad account for yourself, you can check off '''Ugrad Linux'''. But, if you do end up needing a Ugrad account, please realize that your CS Grad/Research Net account is your primary account (email, webpage, etc.) And, the Undergrad Net machines are subject to [[Disk Quotas|disk quotas]].

:''CS Grad students'' (PhD and Masters) should also indicate their expected graduation year on the form next to their student affiliation.

:''CS Staff members:'' In addition to checking off the Linux box you should also check off the ''Windows'' box at the top.

:'''''If you already have a''''' '''Grad/Research''' Linux account, and then ''later'' '''''require''''' a '''Ugrad''' Linux account (TA'ing a Ugrad course, for instance), please fill out the form again indicating which other accounts you need,  You'll fill in your current username after the '''''"Already have a CS acct..."''''' line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.")

:'''''If you already have a''''' '''Ugrad''' Linux account, and then later, become part of the CS Graduate program (Masters or PhD) and are applying for a Grad Linux account (which is probably why you're reading this section now), please fill out the form again indicating which other accounts you need, You'll fill in your current username after the "Already have a CS acct..." line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.") However, if you do get a CS Grad/Research Net Linux account, your CS Ugrad Net e-mail will no longer be in service (although, you will have access to your old e-mail). You would now have CS Grad/Research Net mail. If you're receiving a Grad account, you should move your Ugrad files over to your new Grad account and let us know, so that we can remove your Ugrad account.

===== CS Undergrad/CS Minor Student Accounts =====
:If you are a ''CS Undergraduate student'' or ''CS Minor student'', you will need a CS Undergrad Account to access the [[Linux Clients on the CS Undergrad Net|Undergrad Net Linux]] computers.


: CS Undergrad/Minor students should also indicate their expected graduation year on the form next to their student affiliation.

:'''''If you already have a''''' '''Ugrad''' Linux account, and then later, become part of the CS Graduate program and would need a '''Grad''' Linux account, please fill out the form again indicating which other accounts you need,  You'll fill in your current username after the '''''"Already have a CS acct..."''''' line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.") However, if you do get a ''CS '''Grad/Research''' Net'' Linux account, your ''CS '''Ugrad''' Net'' ''e-mail'' will no longer be in service (although, you will have access to your old e-mail). You would now have ''CS Grad/Research Net'' mail. If you're receiving a Grad account, you should move your Ugrad files over to your new Grad account and let us know, so that we can remove your Ugrad account.

:Note: CS Linux  machines have [[Disk Quotas|disk quotas]]. Please remove files you no longer need on your account after you are finished with them.

===== Class/Course Accounts =====
:If you are provided a ''class account by your instructor, or if you apply for one yourself'', please note that class accounts are up for removal after the semester is complete.

:'''''If you already only have a''''' '''CS class account''', but have entered into the CS Undergrad program, you are eligible to obtain a '''CS Ugrad''' Linux account, To do so, fill out the CS Account Form again from scratch, but this time, follow the section above for CS Undergrad/Minor students.. (But, do indicate somewhere along the top that you had been using a class account and what that account is.)

:Note: CS Linux  machines have [[Disk Quotas|disk quotas]]. Please remove files you no longer need on your account after you are finished with them.

===== Concurrent Students =====

:If you start as a ''CS Concurrent Student'' (grad/ugrad at the same time) or if you were already a CS Ugrad student with a CS Ugrad account and become a Grad student, please make arrangements with CS IT Support to obtain a ''CS Grad/Research Net'' Linux account, if you'd like. However, if you do get a ''CS '''Grad/Research''' Net'' Linux account, your ''CS '''Ugrad''' Net'' ''e-mail'' will no longer be in service (although, you will have access to your old e-mail). You would now have ''CS Grad/Research Net'' mail. Your CS Ugrad account, however, will remain while you have a Grad account, until you graduate.

===== Other =====

:If you're not sure you fit into one of the listed categories on the form, ''for example "research scientist"'', please choose "Other" and specify your position within JHU, and a reason you need the account, if applicable. You will still need to get an [[#Signatures| authorized signature]] on your form.
 

=== Choosing your CS Account Username ===

:{{red|'''NOTE:''' We do '''not''' change CS usernames/accounts once created.}}

:'''''CS Faculty, Instructors, Staff, Post Docs, Researchers, and some others:''''' You can generally request your own username. You should request up to three possible usernames, and we will use what we can, depending upon what's available. However, we highly recommend you choose to make your CS account username the same as your JHED ID.

:'''''CS Ugrad, Masters, and PhD Students:''''' A CS username will be assigned to you, based upon your current JHED ID.

:'''''Non-CS students taking a CS Course:''''' We will assign you a special course-based username for your CS course account. ''That course account will only be valid the semester the course is taught and will be removed upon course completion.''

:'''''Others:''''' When in doubt, your can choose to request us to use your JHED ID username as your CS username too.
 

== Signatures ==

We require '''at least two''' and up to '''three''' signatures on each account form.
*You will sign the '''front''' of the form ''and'' read and sign the '''back''' of the form.
*Several of you will also need to obtain an '''authorized signature''' as appropriate (and as described on the form.) {{red| But, read below for changes in this policy.}}

{{red|'''UPDATE:''' In recent years, we had made some changes regarding signatures, and those changes are still in place... Instead of you having to obtain the authorized signatures on the form, in several cases (for example, students), we will take care of that for you. Please see below for details. '''''(So, all you need to do is fill out the form, make sure you sign both sides, ''read the section below about any signatures needed'', obtain any required signatures, per below, and then [[#Submitting The Account Form| submit the form to us]].)''''' }}

* ''CS Grad (Masters & PhD) students:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots. 

* ''CS Undergrads/CS Minors:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots.  

* ''CE (Computer Engineering) students:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots.

* ''Non-CS student taking a CS class:'' Until further notice, you do '''not''' need your CS professor (CS Faculty/CS Instructor) to sign the form. '''Your account will last for the semester.'''  {{red| '''NOTE:''' }} Under the Non-CS Student section, if you're taking a CS course and you list your Course name and #, in that same section, '''please also list your CS professor's name''' as well. This will speed up processing.

* ''New CS faculty/instructors/staff:'' Please get '''Laura Henneman''' or the '''CS Dept. Chair''' to sign your account form. 

* ''Postdocs, visiting faculty, or research scientists, etc.:'' Please have a '''CS Faculty Member''' (or possibly, '''Laura Henneman''') sign the form. 

* ''Students from other depts that are not associated with CS who are requesting a CS account on our system:'' You must have a [https://www.cs.jhu.edu/faculty ''CS Faculty''] member sign the account form. That CS Faculty member is sponsoring your account. If you're an undergrad student, you would have access to our ''CS Ugrad Network'' systems. If you're a grad student, you would have access to our ''CS Grad Network'' systems. {{red|We will attempt to obtain this approval for you, however, you need to indicate somewhere on the form '''which''' [https://www.cs.jhu.edu/faculty CS faculty] member will sponsor your account. You do may need an authorized signature, as long as we are able to obtain any approvals for your account. Just make sure '''you''' sign the front ''and'' back in the appropriate spots for your account. If you choose to gather the authorized faculty signature yourself by sending your filled-out/signed form to the faculty member to sign, then please have that faculty member scan and email the completed form to [mailto:support@cs.jhu.edu support@cs.jhu.edu]), that will speed up processing.}}

If you have any issues regarding signatures, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] to discuss alternatives.



 

==Submitting The Account Form==




*First, make sure you ''signed'' '''both''' sides of the form. Also, if you need to, obtain any [[#Signatures|authorized signatures]]



* Please '''scan both sides ''into a single'' pdf.''' Then, attach the pdf to an email and send that to [mailto:support@cs.jhu.edu support@cs.jhu.edu]
:::{{red|'''''IMPORTANT NOTE 1:''''' When you email the account form to us, please have the '''''Subject Line''''' include '''''your name''''' and the words '''''"CS Account Form"''''}}
:::{{red|'''''IMPORTANT Note 2:''''' When you send your filled-out and signed account form to support@cs.jhu.edu, if possible, '''''please send it from a JHU-based email address''''', to make sure it will get to our team. Obviously, if you don't have a JHU-based email address, that's ok too... just send from an email address you have. But, again, we prefer it coming from a JHU-based email address to ensure its delivery to us.}}

::'''NOTE:''' If you don't have a scanner, you can always use an app like [https://www.camscanner.com CamScanner] on Android and iPhone or [https://support.apple.com/en-us/HT210336 Notes app] on iPhone. As a last resort, you can ''neatly'' take a photo of both sides of the form.





== Processing your CS Account Form And Receiving Your CS Account==



'''''Please allow at least 2-3 business days for your account to be created, as we have to obtain the authorized approval.'''''

* After your account is created, you will be contacted ''via e-mail'' at one of the e-mail addresses you listed on the form (so, check all of them) by [mailto:steve@cs.jhu.edu Steve DeBlasio]. He will send you instructions for pick-up of the account information, which will now be done remotely.
::{{red|'''BE AWARE: If you are expecting e-mail from the CS IT Support team, and if you use [http://www.gmail.com Gmail], make sure you check your Gmail Junk folder. Gmail likes to file some e-mails from CS into Gmail Junk folders.''' }}

* {{red|For remote account pick-up, as mentioned above, Steve DeBlasio will provide you instructions. He will meet with you over [https://support.cs.jhu.edu/wiki/Zoom Zoom] Please make sure you have Zoom installed on your computer or mobile device. And, you will need to have your J-Card (or other picture ID if you do not have a J-Card) in-hand, as he will need to see it when you meet with Steve via Zoom.}}



==''Do Not'' Share Your CS Password!==
:Please don't share your CS account password with anyone. No one else ever needs to know your account password, not even CS IT Support. If you're requesting information about an account, you can just give the account name; that's enough for authorized people to look up information about the account. Sharing the password with other people is potentially a security risk.

:Even if you think the person you're contacting is trustworthy, since they should never need your password, it's good practice to never send it (not even via email or text.) That makes it impossible to accidentally send it to the wrong person, among other things.

==And finally...==

If you have any problems filling out the account forms or have not received notice that your account is ready in a reasonable amount of time (at least 2 ''business days'' after submitting the form), please email [mailto:support@cs.jhu.edu support@cs.jhu.edu].

[[Category:Accounts]]

Screenlocking Policy in the CS Ugrad Labs and Masters Lab

2026-06-02T16:06:00Z

Pip:

To all CS Grad or Ugrad students who use either the MH-122 CS Ugrad Lab/Collaboration Room or the 316 CS Masters Lab Lab Linux or Windows computers:

* If you need to leave one of the Linux or Windows computers in those labs ''for more than one hour'', you need to '''log out''' of it '''''instead of screenlocking''''' it, to allow others to use the machine.

* An hour should give you plenty of time to use the restroom or pick up lunch, etc. Do not screenlock the computer if you have to go to a class that is more than an hour long. Please logout instead.

* If we see that your machine is screenlocked (or if it is brought to our attention), and it has been more than an hour, ''we will have the option to unlock it and log you out'' (without notice), so that others can gain access to the computer.

* If there is a specific program that you '''must''' run directly at the desktop (instead of ssh'ing in, etc.), and you need to absolutely lock the screen for more than an hour for this purpose, you should contact us ([mailto:support@cs.jhu.edu support@cs.jhu.edu]) ahead of time to make arrangements.

We are hoping not to have to impose an automatic unlock-and-logout software system on these machines, so, please help out your fellow students by only screenlocking your machine if you'll be away for less than an hour.

[[Category:Labs]]

Resetting a CS Lab Printer That Hangs

2026-06-02T16:05:41Z

Pip:

CS Labs MH 122 and MH 316 each house an HP LaserJet 4350 printer.

Per the [https://support.cs.jhu.edu/wiki/Available_Printers available printers list]...

:MH-122's printer is called '''mh122prt'''

::and

:MH 316's printer is called '''mh316prt'''

If you notice either of these printers are hung up ''(not related to a printer jam)'', it could be an incompatible document or a document that triggers an '''error 49.4C02''' or something similar might have occurred.

Generally, to unhang these printers, try the following steps:

* Power off the printer with the power switch on the right side of the printer.

* Wait 1 minute. (Helps the internal memory clear out.)

* Power the printer back on and wait until the screen shows ''Ready''

:'''IMPORTANT NOTE:''' Try not to turn off a printer while it is in the middle of printing. Perhaps hit the menu button and find a "Cancel Print"-type of option. Otherwise, the printer might jam.

If the printer still doesn't work, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with a full description of the problem (including which CS Lab room # the printer resides in.)

[[Category:Printing]]

Computing Rules and Policies for CS IT Services and Computing Labs

2026-06-02T16:04:46Z

Pip:

==CS I.T.’s Computing Services and Computing Labs: Computing Rules and Policies==

The following applies to the [[:Category:Labs | CS Grad & Undergrad Computing Labs]] (MH 122 and MH 316) and their computers. However, where appropriate, these rules and policies also apply to the general computing services provided by CS I.T. The computing labs are here to meet computing needs of students taking Computer Science courses that have specific resource needs not offered by the rest of the university computers and labs. We accomplish this goal by providing the tools needed to meet their academic goals in a positive educational environment.

'''NOTE: THE CS UGRAD & GRAD LABS (Malone 122 & MH 316) ARE UNDER SURVEILLANCE FOR YOUR SAFETY, AS WELL AS FOR THE PROTECTION OF THE LAB EQUIPMENT.'''

==RULES OF USE FOR THE CS GRAD/UGRAD LABS, THEIR RELATED COMPUTERS, & GENERAL CS IT Services==

# Masks are now '''''optional''''' for all those using our labs. (updated Aug, 2022)
#''Eating'' is '''no longer allowed''' in the lab.
# Absolutely no commercial software is to be installed on any of the CS Grad/Ugrad Lab-related computers, except by the CS IT Support Staff.
# Any user-installed free/shareware must be installed within user’s own home directory and removed when done.
# Tampering with current setups/configurations of the CS Grad or Ugrad Lab-related computers and furniture is prohibited and will not be tolerated.
# People doing work for Computer Science courses will have priority over anyone else using the CS Grad or Ugrad Lab machines.
# No foreign hardware (with the exception of USB thumb drives) is to be used with the CS Grad or Ugrad Lab machines or wall ports without the permission of the CS IT Support Staff.
# No networked games (except for those required for class assignments on game software-writing) are to be played on any of the CS Grad or Ugrad lab computers. We define networked games as any real-time, graphics-based game played between two or more computers.
# Admission to the CS Grad and Undergrad Labs is granted only to those persons who have legitimate Computer Science Department needs. These persons will have J-Card access.
# Students will not allow any non-authorized persons into the CS Grad/Undergrad Labs. Only those who have Computer Science-authorized J-Card access will be allowed into these labs. All CS users should swipe their J-Card for entry to the CS Labs.
# No bicycles allowed in the Computer Science Masters Lab or Undergrad Labs for any reason. Use the bicycle racks outside the building.
# Users will clean up after themselves in the CS Computing Labs.
# No propping the CS Undergrad Lab doors open unless authorized to do so by the CS office or CS IT staff.
# The CS Ugrad Lab (Malone 122) is primarily for Undergrad students and for Grad/Masters course work as required. However, Grad/Masters students should utilize the Masters Lab (Malone 316) instead, whenever possible, and only use the Ugrad Lab computers as required. (Ugrad computers have home directory [[Disk Quotas | disk quotas]]. Grad/Masters computers do not.)
# Users will not give out their passwords, nor will they allow others to use their personal accounts.
# Course-specific Linux accounts issued to students will be deleted upon the completion of the course. This rule applies to Teaching Assistant accounts as well. If you need a personal Linux account, please apply for one. Details on the CS IT Support Wiki in the [https://support.cs.jhu.edu/wiki/Category:Accounts Accounts] category.
# Users will adhere at all times to any and all policies with regard to [[Disk Quotas | disk quotas]]. Users of the ''Ugrad Net'' Linux computers are limited to '''10 gb''' of home directory disk space. Exceptions will be made on a case-by-case basis by e-mailing [mailto:support.cs.jhu.edu support@cs.jhu.edu]
# Any action which violates local, state, and/or federal laws and/or which violates JHU's Computing Ethics Policy is strictly prohibited.
# Lock or logoff all machines before leaving the CS Grad or Ugrad Labs or any CS IT-managed system.
# Locking any computing lab system for more than one hour (without prior authorization from CS IT Support) or leaving any machine that you are logged into unattended (and unlocked) by you is not permitted! You may be logged off regardless of what you are working on, and your account may be disabled. This is for both security purposes and to allow others to use the lab machines. See [[Screenlocking_Policy_in_the_CS_Ugrad_Lab_and_Masters'_Office|Screenlocking Policy in the CS Ugrad Labs and Masters Lab]] for more details

'''FAILURE TO COMPLY WITH THE ABOVE RULES MAY RESULT IN DENIAL OF ACCESS TO THE DEPARTMENTAL COMPUTING RESOURCES.'''

'''CASES INVOLVING VIOLATION OF APPLICABLE LAWS OR UNIVERSITY POLICIES MAY BE PROSECUTED TO THE FULLEST EXTENT OF THE LAW. 

[[Category:Labs]]

Networking at CS - Overview

2026-06-02T16:04:00Z

Pip:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses 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 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.

===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]]

Connecting to the CS Ugrad Net

2026-06-02T16:02:53Z

Pip:

Since CS does not maintain [https://support.cs.jhu.edu/wiki/Wireless_Networking wireless connections], if you will not be connecting to JHU's '''''hopkins''''' or '''''eduroam''''' wireless system, then, you will need to use a Cat 5 or Cat 6 cable for your network connection to connect to the ''CS Undergrad Net''.

'''DHCP''' service with dynamic IP addresses on the CS Ugrad Net is available from:

:* the table-mounted and wall-based network jacks within the Malone 122 Undergraduate computer lab

'''NOTE:''' ''Static IP'' addresses are '''not''' available on the CS Ugrad Net.

 

==Obtaining a ''DHCP'' IP Address on the CS Undergrad Net==

#Set your computer to use '''DHCP'''
#Plug your computer into a tabletop or wall-based network jack in ''MH 122''
#Depending on your operating system, you may have to reboot your computer at this point
#You should now have a dynamically-assigned IP address on the CS Undergrad Net

:'''NOTE:''' Sometime in the future, we will be using a different method for providing a dynamically-assigned IP, but for now, the procedure above works.



[[Category:Networking]]

Available Printers

2026-06-02T15:41:50Z

Pip:

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) '''''{{red|NEW!}}'''''||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.''|| {{red|('''''NEW'' ''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 (''{{red|'''NEW'''}} 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]]

Notices

2026-05-29T19:26:07Z

Pip: /* 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 ===



{{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 ===


:'''WHAT''': JHU's Chilled water outage could potentially affect our CS IT Services.

:'''WHEN:''' Friday, 5/29, 10pm thru Saturday, 5/30, 2am.

:'''DETAILS:'''

::JHU Facilities just announced to us that they will be performing another chilled water outage Friday, (5/29, from 10pm until Saturday, 5/30, at 2 am. (4 hours.)

::When this happens, our CS server room loses cooling ability, and that can adversely affect our server hardware. Without cooling, we may need to resort to shutting down a variety of our servers (and their services) to protect them from overheating.

::If you notice any of our CS IT services (login, mail, web, MySQL, etc..) become unavailable Friday evening into Saturday, it might be due to the cooling outage.



______,


 

== {{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 will be 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) will be moved into MH 316, and we hope to have them running that day, but they could be delayed.

:* The current G61 printer will also be moved into MH 316 on June 1 or shortly thereafter.

:* 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-05-22T16:55:12Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

== {{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=several lab machines
|time=Friday, May 22
|summary=Several lab machines did not return to operation after a power outage. Those systems include ugrad3, ugrad7, and masters10. Please use other Linux clients until those have their issues addressed.
}}
 

=== 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 will be 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) will be moved into MH 316, and we hope to have them running that day, but they could be delayed.

:* The current G61 printer will also be moved into MH 316 on June 1 or shortly thereafter.

:* 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]]

Networking at CS - Overview

2026-05-01T19:22:04Z

Pip:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses 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 122 and the Ugrad Lab side of MH G61). 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 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.

===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). (Note that our other Ugrad Lab room, the Ugrad Lab side of Malone Hall G61, houses additional Ugrad Lab systems, but we are not currently supporting users plugging into the network in that 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]]

Notices

2026-04-16T23:11:52Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2026-02-18T16:42:38Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2026-02-18T16:30:10Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */