Accounts: Temporary Accts
We will not permanently register a machine for someone who will only be here a short while. In these cases, a guest NOMAD account is provided to the individual. This allows non-NCSU personnel to access the NCSU Wireless network. As most laptops are now equipped with wireless cards, this covers most scenarios.
We have a form being created for this. For now, we request that an email be sent to firstname.lastname@example.org by the visitor's sponsor.
As a follow up to the guest NOMAD access: Within all classrooms and conference rooms we recommend the usage of a WIRED Nomad Wall port. It is possible to configure a wall port to act as a part of the NOMAD wireless network. As such, any laptop that plugs into this wall port will receive an IP from the NOMAD network, and require that someone login b/f network access is granted. Combined with guest NOMAD accounts provided by the college or department, this grants guests the ability to use wired network access in specific locations without the need to register their machine. It provides increased security for the University as we record the accesses of these guest NOMAD userids, remove the possibility of guests using any wall port they see, and as guest accounts are limited in their time frame (usually limited to a couple days or less upon creation) we can restrict the length of their access to the NCSU network.
Making Guests Permanent -- NoPay NCSU Accounts
NCSU has the ability (once again this is at the departmental/unit level) to create Unity accounts for individuals that are associated with the University, but are neither students nor on payroll. These are referred to as NoPay accounts. It’s a slight complicated procedure, but basically, someone in the department vouches for an outsider to have access. Example: Tom Conte has some researchers at Intel that he works with. They require access to some of his systems/websites. Tom comes to me and requests that we extend a NoPay account to them. Assuming I agree (some basic usage/access questions are always asked), the outsider fills out a form we have for the purpose of collecting the HR information that is required. UnityID accounts are now COMPLETELY tied to the NCSU HR system -- one is not created without the person being entered into our HR systems.
FYI - This is not a good thing as it has increased the time to get a UnityID from 24hrs to 2 weeks, but that’s the way it is.
Don't currently have a Unity or EOS Realm ID? Need one? Need an extention? Request a NoPay Account.
Wireless AP that are not on the NOMAD network
While NC State does allow Non-NOMAD wireless on campus (http://www.ncsu.edu/it/rulesregs/wireless/implementation-rules.html), it does place this at the discretion of the academic unit (ie, college or department).
Frankly, this is not something we want to encourage. Outside of specific wireless research projects, all wireless at NC State should be on the NOMAD network. We'd end up with countless overlapping networks that just confuse both the IT people (who inevitably end up having to fix it) and the students who *see* the network. Add the fact that most people have no clue what they're doing, especially when it comes to SECURING a wireless network (which by the way, generally doesn't happen)... Cheap wireless APs also have a tendency to get hacked...
Should the private wireless network in ANY WAY affect a nearby/overlapping NOMAD network, it will be removed by central IT.
Accounts are available for workshop attendees and sponsors who need access to University resources during seminars and meetings. There are different policies and procedures for obtaining a temporary account depending on which college the workshop is associated with.
PAMS Procedure for Workshop Accounts: