Network, Network Access and Communications
General Network Services
Office computers used by faculty and staff, as well as public, lab
and shared computers, are connected to the University network by a
100-Mbps Ethernet connection. Firewalls and Intrusion Detection Systems
are in place throughout the University network to provide enhanced
security features and to ensure safety for all network clients. All external connectivity is handled by several dedicated 1-Gbps connections to the Internet and Internet2 via the Merit Network. Oakland University is an Internet2 participant.
Wireless Network Connectivity
Oakland University offers 802.11b/g Wireless Networking throughout all
major buildings on campus, with access to popular programs and protocols
used for Internet browsing. Communications sent over the wireless
networks are unencrypted. You can access the wireless network by joining
the network GrizzNet from your mobile computer. GrizzNet is the primary identifier (SSID) of community wireless network services.
Other wireless networks that may appear:
- GrizzNet-N - Enhanced network speeds for clients that support 802.11n protocol.
- voice - This is a prototype network for UTS testing and is not available to the community at this time.
- OUGolf - This is a guest access network for patrons of the Golf and Learning Center.
Network Access for Visitors and Guests
What is Network Access?
Network Access is the ability to use the wired and wireless networks provided by Oakland University. Network Access includes the ability to use a browser (i.e., Internet Explorer, Safari, Firefox, Chrome, etc.) to browse web sites or otherwise access the Internet.
Who can obtain Network Access?
Students, Faculty, and Staff of Oakland University may use Network Access by registering their device at https://netreg.oakland.edu and logging in with their assigned NetID and password. Employees (Faculty and Staff) are provided Network Access in order to successfully complete their work at Oakland University. Students are provided Network Access as a service with costs covered by tuition.
Who are Visitors and Guests?
Visitors are those people who visit the campus for short periods of time and their identity is not authenticated.
Guests visit for defined periods of time and the identity of a guest is authenticated by showing and recording a picture ID or through event registration.
Can Visitors obtain Network Access, particularly wireless Network Access?
No, at this time Oakland University does not offer Visitors Network Access due to costs and regulatory compliance issues.
Can Guests obtain Network Access, particularly wireless Network Access?
Short-term Guests participating in an event in the Oakland Center or Meadow Brook Hall, or visiting Kresge Library, may obtain Network Access. For events in the Oakland Center or Meadow Brook Hall, plans for Network Access should be arranged at the time the event is planned. Event attendees should check with the event organizer about network access. Event attendees are responsible for compliance with the Digital Millennium Copyright Act and university policies and should note that network access activities are tracked and subject to legal action, such as subpoena.
Short-term Guests using Kresge Library may arrange for access at the Circulation Desk.
Long-term Guests are those who need Network Access for longer than one day. Long-term Guests must be sponsored by a department. The form NetID - Guest Account Request Form must be completed and submitted for long-term Guest Network Access. Access must be sponsored by a department. Oakland University does not sell or lease access.
Guests are responsible for compliance with the Digital Millennium Copyright Act and university policies and should note that network access activities are tracked and subject to legal action, such as subpoena.
Can a university department arrange Guest or Visitor network access for an event in a different location (other than the Oakland Center, Meadow Brook Hal and Kresge Library)?
In some locations and with advance planning, temporary network access can be arranged for an official university event. The sponsoring department should contact the Helpdesk (email email@example.com) with event planning details as early as possible before the date. UTS will analyze the request and provide a response about possibilities and costs.
Why doesn’t Oakland University provide free and open wireless network access like local restaurants?
As a University, Oakland must comply with federal regulations that do not apply to restaurants. To keep the cost of network operation as low as possible, Oakland University has implemented the lowest cost options for regulatory compliance. Additionally, student tuition covers the costs of providing wireless access points and bandwidth necessary to provide Network Access. To keep the cost of education as low as possible, we must restrict access to those who pay for it – our students – or those employed by the university who need access to do their jobs.
Network Policies and Security
- Network connectivity is governed by official Policy #850 - Network Policy.
- Network access and use are governed by Policy #890 Use of University Information Technology Resources.
- Access and use may be limited, restricted, or suspended in situations where there is an abnormally excessive usage of resources, suspicious or illegal activity, or during an investigation as approved under guidelines in Policy #890 and approved by the Office of Legal Affairs.
- All non-wireless computers must connect directly to a network jack on
the wall. Unless prior written consent has been granted, no desktop
hubs, switches, or routers are permitted. Unapproved devices will be
removed by UTS.
- Servers operating on the University network must be approved and either operated by University Technology Services or be covered by an appropriate Service Level Agreement (SLA).
To review all information technology and networking related university policies and guidelines, please review the Policies and Guidelines site.
Network Registration System - NETREG
All computers connecting to the Oakland University network must be registered to an Oakland constituent before network access will be granted. All registration data must be accurate, and periodic re-registration will take place annually to ensure that all records are current. Any computer which remains powered off or disconnected from the University network for more than 180 days is automatically de-registered.
University Technology Services provides several resources to you to make sure that the registration data regarding your computer is correct. You can use these resources from your computer when it is connected to the University network.
Contractors performing authorized work, as well as vendors soliciting responses for Request for Proposals (RFPs)
must abide by the Telecommunication (Data, Video and Voice) Standards
when submitting proposals or performing changes to the network infrastructure.
The following items should also be taken into account when designing systems that connect to the Oakland University network.
• All device-to-device network communications must use IPv4 over Ethernet. Legacy protocols such as IPX/SPX and NetBEUI are prohibited.
• All network-connected devices should be IPv6-capable. If not, the vendor should have an IPv6 roadmap and/or migration strategy.
• All device-to-device network communications must allow for connectivity between subnets. Direct layer 2 connectivity between devices cannot be guaranteed and must not be required by this system.
• All network-connected devices must support standards-compliant DHCP including periodic lease renewal prior to expiration.
• All network-connected devices must present only a single MAC address to its directly-connected switch. All network-connected devices must never act as bridges or attempt to participate in spanning tree. Filtering transit BPDUs is prohibited.
• All required network communications must be documented and diagramed, including: source/destination device, IP protocols, and UDP/TCP port numbers.
• If IPsec is used to secure device-to-device communications, NAT-Traversal/Transparency must be supported.
• All network-connected devices must only send (and be able to receive) IP packets that are less than or equal to 1500 bytes in size including the IP header.
• Primary remote vendor support must be conducted via the university-provided VPN. Remote support provided via dial-in modem may be provided as a secondary method.
• All new cabling installed for this system must be performed under the supervision of UTS and follow existing university standards.
• If name resolution is required, all network-connected devices must use DNS. WINS must not be required for name resolution.
• "Universal Plug and Play" (UPnP) must not be required for system functionality.
• All network-connected devices should support 802.1x .