Networking

This page has information, fixes, hints and tips about using networks on our school campuses. [|CDO] was previously (as of this writing, Summer 2008) a site that used Novell Netware network operating system (version 6.5 - similar to Novell's Linux-based networking stack.) The school network servers has regrettably moved to the closed, proprietary dark side of Microsoft with the kludge that is Active Directory. I won't be covering too much about Microsoft networking problems (probably require a site of its own!). I'll keep these entries about issues we had with Novell in the hopes that the info helps others.

Novell "Client" issues

 * This issue snags lots of folks. The call to say they've logged on to their Windows 2000/XP-based PC and they repeatedly get the Novell logon request screen when they try to access their server space (via the desktop shortcut I've placed or Network Places/Neighborhood) or try to print to a network laser printer. What's going on?!? This scenario happens almost exclusively when the user has checked the **Workstation Only** box on the logon screen. "So what?", you might ask. Workstation only means the user has chosen not to access //network services// (printers, servers, applications residing on a server), only to access the local hard drive, devices and print to the local, direct-connect printer. When the user then requests a network service, the logon //Client// will then keep asking for authentication (and who are you?) -- hitting **Cancel** only stops the request for the moment. Easy fix: close any applications and files that are open, choose **Logoff**, go back to the Client screen, //uncheck the Workstation Only box//, and logon. End of story!
 * CDO has settings for student logons that make the student accounts **volatile**. We had problems with computer lab hard drives filling up and not allowing students to logon. Here's the story:
 * This means that when they logon, Novell passes their logon info (username, password) to the Windows networking software which passes this on to the Windows operating system (Windows 2000, XP).
 * The OS then creates a **profile** for that student user in the **Documents and Settings** folder. The profile is based on the Windows **Default User** account settings (My Documents hive, desktop wallpaper, bookmarks, favorites, default printer, etc.)
 * If the student saves his/her document(s) to local My Documents folder on the hard drive and then logs off/shuts down/restarts, the account's volatile (remember that?) settings go into effect, removing any locally saved settings, files, profile info for that student user.
 * If the student didn't save his/her work to their network drive (labeled as the **K:\** drive), then the file saved in the local My Documents is gone, in the //bit-bucket//.
 * The moral of the story: students must be given instruction on how to save to their server storage space. This isn't something they will know without our help.
 * Another situation that has been very problematic for teachers. The user (a teacher or staff member in this case) uses a laptop with an installed **Novell Client** outside the Amphitheater network: at home, a hotel on school travel, a conference, etc. Great! The problem occurs when they try to logon with the Novell Client: they must check the **Workstation Only** box on the Client screen to access their Windows system. Not an issue at all IF they have used the laptop before and logged on to the school network successfully (Workstation Only box NOT checked.) This situation is the inverse of the above situation:
 * Teacher/staff accounts are set to retain the user profile after a logoff/restart/shutdown.
 * The user profile is not created until the users successfully logs on to the school/site network with the Novell Client software and the Workstation Only box is NOT checked. Windows will then create the profile on the hard drive in the Documents and Settings folder.
 * The user can verify that they will be able to logon outside of school by unplugging the Ethernet cable, restarting the laptop, and clicking the Workstation Only box on the Client logon screen. They need to logon without the normal network context information appended to their user name (i.e., .TEACHERS.) and their regular logon password.
 * This should be done before they leave their school/site to make sure they will be able to logon to their profile.