u/darkjedi521

It's move in time! Also known as the time of year where everyone gets overwhelmed all at once.

TL;DR: Call x7777 for phone, network, laptop, login issues, software problems and x2000 for HVAC, plumbing, leaks, and other building problems. Problem solvers do not watch reddit for problem reports especially when their queues are full of issues submitted through the standard channels.

In an effort to avoid a few dozen network questions/complaints threads, here's a summary of common network issues.

0.) Don't be afraid to call, email, or visit the Help Desk. It is hard to fix problems no one knows about. x7777 or https://ITSSC.rpi.edu will reach them if you can't visit in person. If its a facilities problem (power, plumbing, leaks, but not Ethernet, phone, or CATV), x2000 or https://info.rpi.edu/facilities-management/fixx

0-a.) You may need to follow up. In the start of semester madness, things can get overlooked by accident. Keep the ticket # from the initial contact. You can actually log in to .CIO's and FIXX's systems and check your status.

0-b.) Your RPI email will be used for all official email communication. Ignore its existence at your own risk.

1.) Wireless is shared bandwidth among all clients on an access point. Although the access points should be able to handle the traffic, they may have issues with the occasional spike. Try a wired connection if experiencing overall slow speeds to see if that resolves the problem. Make a note of the time, your physical location, the physical/MAC address of your wireless adapter, and let the helpdesk know. They can be reached at x7777 or https://itssc.rpi.edu The network techs can't investigate problems they don't know about.

2.) Wireless can have faster raw speed than wired, but because of its shared medium, its latency can vary. If a fixed latency is important, try a wired connection or convince your neighbors to use a wired connection. The access point may be capable of 600 Mbits, but assume a minimum of 2 Wifi clients per student.

3.) Running your own access point is prohibited. Relevant Policy. Due to the shared nature of wireless spectrum, the more radio sources competing for the same channel, the worse the signal is for everyone. RF coordination is a challenge even with relatively clear spectrum.

4.) It is possible to put gaming consoles and such on the WiFi. There's a special network that you have to register the device for. It will only work on the residential side of campus and not in the academic buildings. Info. If this doesn't work, submit a request for a manual override here: Netreg

5.) 3rd party DNS servers are prohibited. Traffic to external DNS providers is blocked. This includes the root servers. If you can't access anything, triple check you're set to obtain your name server information automatically. Policy

6.) You can run servers on campus and receive a static IP for the wired network in your room. Server and IP info

7.) No matter how nicely you ask, you won't get a bypass code for duo. That being said, you can get help if your authentication device breaks

8.) When requesting software, it takes some time for all the ACLs to update (typically you get an email with instructions once they are set). If you get denied, wait an hour, reboot (to clear Window's ACL cache) and try again. If that fails, put in a trouble ticket.

8-a.) There is a lot of info out there for running Windows software via bootcamp on Mac. That info only applies to Apple's Intel era (2006 - 2020). Current Macs use an ARM derived CPU. It is possible to run virtual Windows for ARM using commercial solutions you can buy, and then use Windows for ARM's built in Intel emulation to run your required PC software, but performance and compatiblity may vary greatly.

9.) .CIO generally operates on a "Don't make me pay attention to what you're doing" basis and are generally willing to work with you on legitimate needs.

I think this covers the common start of academic year questions/complaints.