| New requests for access to the local network for
personally owned laptops, either wireless or wired, are no longer being
accepted. If you want network access for such a system in a research laboratory
or student office, you need to talk to your faculty advisor about arranging
installation of wireless access points for the osuwireless system. This form should be
used by the faculty advisor to request installation of the access point(s)
needed to cover the area(s) in question. If you previously had departmental network access from your own laptop, and it's not working due to a system upgrade (e.g. motherboard swap, system replacement, etc.), please use the traditional mechanism to request continued access, and we will try to accommodate you. It should be noted that, ultimately, all access to the departmental network for personally owned systems will be terminated at some point, and the preferred mechanism for acquiring Internet access is by leveraging osuwireless. |
NOTE: If you are not familiar with local network policies in general, please review them now. ALL USERS are expected to abide by them. Ignorance of policy is not an excuse to violate it. (In other words, the phrase "...But I didn't know..." is not acceptable reasoning.) Maintaining your system according to acceptable use policies is your responsibility.
In the context of this presentation, "personally-owned" means purchased with personal (not OSU) funds by (or for) the applicant. In the case of computers purchased for the applicant, if (outside) company property, the applicant needs administrative access, and a company support account is also permitted; otherwise, the applicant and/or adult members of his/her immediate family need to be the only administrative users.
It is not possible for management to fully support personal computers (as opposed to those owned by CBE, MSE, and/or OSU) attached to the network, due to the resources and security certification required. While we recognize that faculty and staff might have a need for more than one device type (e.g. a desktop and a laptop), for these classes of users, we must limit access to no more than one device type per person, provided the systems are OSU property.
AS A COURTESY, we can provide for limited support of researcher/student portable (e.g. "laptop" or "notebook") computers and Personal Digital Assistants (PDAs) attached to the local network. Note that no one is required to use their own computer for academic/research purposes, so the ramifications of choosing to do so are the sole responsibility of the user. ECR6 Management is NOT RESPONSIBLE for any negative impact caused by the delay or denial of local network access for personally-owned systems. Support for such systems is limited to providing a (dynamic) Internet address while connected to the local network.
When necessary, initial configuration will be by ECR6 Management. When the laptop computer (or PDA) is returned to the user, it is the user's responsibility to make sure the system is kept secure by applying any vendor-supplied security patches (e.g. Windows "critical updates") and anti-virus software upgrades as soon as they are available.
Personally-owned desktop computers (as opposed to laptop/notebook computers) cannot be supported on the local network, due to lack of resources. For details, contact
The following lists the requirements of any personally-owned laptop to be considered for local network access. Violation of any of these policies (or those referenced from material linked from this page) will lead to termination of network access unless/until the problem is resolved.
Upon return of your laptop (after configuration for local network access), you MUST ensure that all accounts are password protected.
Only one (class of) personally-owned system (laptop and/or PDA) is permitted per student/researcher. For example, you could have both a laptop and a PDA registered for local network access, but two laptops or two PDAs would not be allowed.
J. Smith (Mobile)
Click on the "Update Samba (SMB) Server Properties" button to complete the configuration of your system.
J. Smith (Mobile)
The aforementioned changes will require you to restart your PC.
For Windows-compatible file sharing, Linux uses SAMBA. This subsystem is
controlled primarily with the smb.conf file. (Use "man 5 smb.conf"
to determine where your variant of Linux stores this file.) The following
options need attention:
netbios name = smith-423
server string = J. Smith (Mobile)
For modern Windows systems, the MAC address can be determined with the "IPCONFIG /ALL" command issued from a "Command Prompt" window. (See Start>All Programs>Accessories menu.) Note that if your system has more than one NIC (e.g. Ethernet and WiFi), you need to be sure you provide the correct MAC address, as each NIC has a different one. The MAC address under Windows is presented as the "Physical Address."
If you're using an Apple Macintosh system and a modern version of Mac OS X, the MAC address will be available by clicking on the Ethernet tab after accessing the Network preferences pane and choosing "Built-in Ethernet" from the Show menu. It will be presented as the "Ethernet ID."
If you're using some other kind of NOS (Network Operating System), we will try to work with you to determine how to configure it. If this process proves to be too time-intensive, though, you may have to go without local network access.
This page speaks mainly to users who desire wired network access. For wireless access, please review the material presented here, which should be considered as an addendum to these policies. (Requests for departmental wireless access still need to use the mechanism presented, above.)
After you submit your E-mail request, you will receive a message indicating your message has been received. You will later receive a subsequent message when your request is ready to be processed (known as "vetting"). Because this access is provided as a courtesy, no priority is given to such requests. As such, the interval of time between your initial request and when it's processed can be considerable, so you should not make any plans which depend on your ability to connect your laptop to the local network. We are unable to estimate when time will be available to honor a request, so please don't ask us to. We will endeavour to meet any outstanding laptop access request within 90 days, but we can make no guarantees. Requests must be complete and accurate to reflect your ability to follow our directions for ensuring compliance with policy; inaccurate or incomplete requests will be denied.