Getting Help

Getting Help

1. If you have issues with Computer Science Resources
  • For Academic/Class-related questions, see Academic Contacts
  • For Computing/IT-related issues
    • Can’t log in? Solve Virtually
      • Connect to https://weblogin.cs.rutgers.edu and log in using your NetID and your University password. This is the same password you use for your Canvas or ScarletMail account. 
      • If you forgot your university password, you can change it at https://netid.rutgers.edu.
      • Hint: Your NetID is the one that looks like a car license plate. Example, for John D. Smith, could be jds12
      • Your first login to our iLab or Research machine is special. It automatically activates your account and creates your home directory on our Linux machine. There is an instruction you need to follow on this first login. Please follow that instruction. 
      • Do not use VSCode for your first login.
      • VSCode saves your password. If you changed your password, you need to change the saved password. Multiple attempts in the background by VSCode with the wrong password will result in a lockout. Once locked, you will need to wait at least 30 minutes.
      • Always log in with your NetID/University password unless you are an existing user who uses CS Password with 2FA. CS Password users can manage their Computer Science passwords on a dedicated site. 
      • If the machine is not responding, check the status of CS machines or Networking.
      • Send an email to help@cs.rutgers.edu to create a support ticket. We will try to get back to you within two business days.
      • Follow @RutgersLCSR’s X.com account.
    • Can’t log in? Solve in-Person
      • For programming, class-related questions, or non-technical questions, visit the iLab Assistant at Hill 252 (Coding and Social Lounge, previously, The CAVE).
      • Visit the LCSR Operator at CoRE 235, call 848-445-2443, or  
      • Visit the LCSR Technical Staff at CoRE on the 2nd floor for any technical questions. The CoRE building is on the Busch campus.
2. If you have issues with Non-CS computing resources
3. If you have issues with Facilities or Building
  • Needs to get Keys or Keycard access to Computer Science Offices or Rooms, or be locked out? email keycards@cs.rutgers.edu  or see LCSR Technical Staff at CoRE, 2nd floor,
  • Problems with Rutgers’s physical building and facilities (e.g., heating, cooling, lights, plumbing, etc.)? Please submit a maintenance request to University Facilities and/or let us know by emailing help@cs.rutgers.edu to create a support ticket, and our staff will contact the University Facilities people for you.

For Graduating Students, see Access to Rutgers technology resources for graduating students.

For other help, see Helpdesk.

About the CS Support System

LCSR has been using the University Help System since Feb.  10, 2026

We are using email to submit a problem. An incident ticket will be generated, and the incident number will be sent back to the user via email. Additional messages from the system may appear as the incident state changes.

How do I report a problem?
  • Send an email to help@cs.rutgers.edu detailing your specific problem.
  • Contact our Operator at ext. 5-2443 (848-445-2443 for external callers) or LCSR Technical Staff at CoRE on the 2nd floor for issues that might require a more immediate response. See the Operations page for coverage.
What happens when I submit a problem?

You should get a new Incident message with the Incident number from the system.

Why didn’t I get a response?

The incoming messages are passed through a spam filter. If the filter flags the message as spam, it will be dropped before it reaches the system. This is an attempt to prevent spam from creating extraneous tickets. If you don’t get a response, try resending the message or calling Operations.

What is the response time?

Most people get a response within a day, often within hours. We will respond to you within 24-48 business hours. If you don’t get any response, please call the Operator at ext. 5-2443 (848-445-2443 for external callers), as something else could be wrong.