0% found this document useful (0 votes)
149 views51 pages

The Berkley College: Practical File of Novel Netware (Practical Software Lab - XII)

This document provides an overview and step-by-step instructions for installing Windows Server 2003 on a computer. It discusses checking system requirements, partitioning the hard disk, formatting the partition in NTFS format, and starting the installation process from the CD. The setup program copies files, initializes the configuration, and loads device drivers before restarting the computer to complete the graphical installation.

Uploaded by

P.s. Dhiman
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
149 views51 pages

The Berkley College: Practical File of Novel Netware (Practical Software Lab - XII)

This document provides an overview and step-by-step instructions for installing Windows Server 2003 on a computer. It discusses checking system requirements, partitioning the hard disk, formatting the partition in NTFS format, and starting the installation process from the CD. The setup program copies files, initializes the configuration, and loads device drivers before restarting the computer to complete the graphical installation.

Uploaded by

P.s. Dhiman
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 51

The Berkley College

Practical file of Novel Netware (Practical Software Lab XII)

Submitted to: Mr.Abhishek

Submitted by: Uni. Roll no

Over View of Networking and Novell:


HOW DOES A NETWORK OPERATE? To understand how a network operates, you must know about the principal components of a network: the file server, the workstations, and the software that runs on each----NetWare and operating systems like DOS, OS/2, VMS, UNIX, and the Macintosh operating system. Beyond these basic components, a NetWare network can incorporate mainframe computers, backup devices, modem pools, and different types of servers (such as file servers, print servers, or archive servers). The Network Workstations and DOS Workstations are the personal computers on which network users do their work. Workstations are used much like non-networked personal computers. The only difference is that they can access files from more than just the local drives. Each workstation processes its own files and uses its own copy of DOS. The Network File Server and NetWare The file server is a personal computer that uses the NetWare operating system to control the network. The file server coordinates all of the workstations and regulates the way they share network resources. It regulates who can access which files, who can make changes to data, and who can use the printer first. All network files are stored on a hard disk in or attached to the file server, instead of on diskettes or hard disks in individual workstations. WHAT IS A NETWARE NETWORK? A NetWare network is a group of computers (such as PCs or Macintoshes) that are linked together so they can communicate and share resources. Network users, each working on a different personal computer, can communicate with each other via the network. They can also share network resources (hard disks on the file server, data, applications, and printers) and use any service the network provides (for example, access to a mainframe system). The NetWare Workstation Workstations use two pieces of software to communicate with the file server, the shell and a protocol. The shell must be loaded into each workstation before that workstation can function on the network. The NetWare shell, either NETX or VLM (depending on whether you are using IPX or ODI), directs workstation requests to DOS or NetWare. When a workstation makes a request (asks to do a task), the shell decides if it is a workstation task (to be directed to DOS) or a network task (to be directed to NetWare). If the request is a workstation task (such as using the DOS DIR command to list the files in a local directory), DOS should handle the request. If the request is a network task (such as printing a job on a network printer), NetWare should handle the request. The shell sends the request to the appropriate operating system, somewhat like a railroad track switcher sends trains to the proper destination. The workstation shell uses another file(s), IPX (or the ODI components: LSL, the MLID and ,IPXODI) to send network messages to the file server. This IPX protocol is the language the workstation uses to communicate with the file server.

How are files stored on a Network?


All network information is stored on the file server's hard disk. The system for storing that information is called the "directory structure." The NetWare directory structure is organized into: 1. File servers, which contain one or more...

2. 3. 4.

Volumes, which can span several hard disks, divided into... Directories, which can contain other directories (subdirectories) and... Files.

A directory structure can be compared to a filing cabinet system. The file server corresponds to the filing cabinet. The volumes correspond to the filing cabinet drawers. Each file server has at least one volume, the SYS: volume, which is created when the server is installed. In NetWare v3.12, however, one volume can span several hard disks. The directories correspond to the hanging folders within the filing cabinet drawers. You can create and delete directories to suit your organizational needs, much as you insert hanging folders into, and remove them from, a filing cabinet. Directories can contain other directories, which are sometimes referred to as subdirectories. These directories within a directory then correspond to the manila folders inside the hanging folders. They divide directories into smaller units, just as manila folders divide hanging folders into smaller units. And finally, directories contain actual files, just as manila folders contain individual documents. A file might be a letter or a list of addresses. When you save information in a file, you give the file a unique name so you can retrieve it later.

Who can use the network?


Before being able to work on the network, a person must be designated as a network user. Network users can be assigned four levels of responsibility on the network. 1. Regular network users 2. Operators (file server console, print queue, & print server operators) 3. Managers (workgroup managers, user account managers) 4. Network supervisors Regular network users are the people who work on the network. They can run applications and work with files according to the rights assigned to them. Operators are regular network users who have been assigned additional privileges. For example, a file server console operator is a network user who is given specific rights to use the FCONSOLE utility. Managers are users who have been given responsibility for creating and/or managing other users. Workgroup managers can create and manage users; user account managers can manage, but not create, users. Managers function as supervisors over a particular group, but they do not have supervisor equivalence. Network supervisors are responsible for the smooth operation of the whole network. Network supervisors maintain the system, restructuring and updating it as needed. Supervisors may also teach regular network users how to use the network.

How is the information protected?


All information on a NetWare network is stored in a central location--the file server's hard disk. However, all users should not be able to access all information (such as payroll files). In addition, users should not always be able to access the same data at the same time; otherwise, they may overwrite each other's work. To prevent problems like these, NetWare provides an extensive security system to protect the data on the network. NetWare security consists of a combination of the following: Login security Login security includes creating usernames and passwords and imposing station, time, and account restrictions on users.

Trustee rights (privileges) assigned to users Trustee rights control which directories and files a user can access and what the user is

allowed to do with those files and directories, such as creating, reading, erasing, or writing to them.

Attributes assigned to directories and files Directory and file attributes determine whether that directory or file can be deleted, copied, viewed, or written to. In addition, they also mark a file as shareable or nonshareable.

Installation of Windows 2003 NT Server Computer and processor PC with a 133-MHz processor required; 550-MHz or faster processor recommended; support for up to four processors on one server Memory 128 MB of RAM required; 256 MB or more recommended; 4 GB maximum Hard disk 1.2 GB for network install; 2.9 GB for CD install Drive CD-ROM or DVD-ROM drive Display VGA or hardware that supports console redirection required; Super VGA supporting 800 x 600 or higher-resolution monitor recommended Plan your installation When you run the Windows Server 2003 Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of Windows Server 2003 more efficient by helping you to avoid potential problems during installation. when planning for your Windows Server 2003 installation Check System Requirements Check Hardware and Software Compatibility Determine Disk Partitioning Options Choose the Appropriate File System: FAT, FAT32, NTFS Decide on a Workgroup or Domain Installation Complete a Pre-Installation Checklist After you made sure you can go on, start the installation process. Beginning the installation process You can install Windows Server 2003 in several methods all are valid and good, it all depends upon your needs and your limitations. In this tutorial we are installing directly from a CD by booting your computer with the CD. Start the computer from the CD.

You can press F6 if you need to install additional SCSI adapters or other mass-storage devices.

Setup will load all the needed files and drivers.

Windows server 2003 welcome screen and available options press enter

Read and accept the licensing agreement and press F8 if you accept it.

Select or create the partition on which you will install Windows Server 2003.Now you need to click C to create new partition

Enter the partition size and press enter

After creating the partition you need to select where you want to install windows server 2003 press enter

Now you need to format your new partition with NTFS select the option as below and press enter

Drive Format is in progress

After format setup will start copying files is in progress

Setup Initializes your windows configuration

The computer will restart now and the installation process will start in graphical mode.

It will then begin to load device drivers based upon what it finds on your computer. You dont need to do anything at this stage.

Click Customize to change regional settings, if necessary. Current System Locale Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, United Kingdom. Current Keyboard Layout Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard. If you dont need to make any changes just press Next.

Enter the name and Organization click next

Enter your product key click next

Select the license mode you want to use click next

Enter the computer name and administrator password click next

Select the correct date and time for your computer click next

Installing network in progress

Now you need to set the network settings here select custom settings click next

Select Internet Protocol (TCP/IP) click on properties

Select use the following ip address radio button and enter you ip address details click ok

After configuring IP address you need to click next

In the Workgroup or Domain window enter the name of your workgroup or domain. A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration. A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name. If youre a stand-alone computer, or if you dont know what to enter, or if you dont have the sufficient rights to join a domain leave the default entry selected and press Next.

Next the setup process will finish copying files and configuring the setup. You do not need to do anything.

After finishing installation process your system will reboot and you can see logon screen

After logging in you should see similar to the following screen for Windows server 2003 R2 editions now you need to insert CD2 to install extra components click ok

Thats it you have completed windows server 2003 R2 installation. . Managing Resources and Users

Users, Printers, Groups


Leaf objects represent network resources. They cannot have other objects below them. For now, we'll review the four main types of leaf objects: Server, User, Volume, and Alias. Typeless vs. Typeful Names Until now, we have used typeless names for NDS objects. However, NDS can also use typeful names. You do not have to use typeful names. NDS automatically converts typeless names into typeful names. Here is an example of a typeless name, which uses only object names: .admin.CompNetSupp.OurCo Here is the same name in typeful format, where the object type is prefixed before each object name: .CN=admin.OU=CompNetSupp.O=OurCo

Object Type Abbreviations These are the abbreviations for types of objects used in a typeful name format. CN stands for common name. This abbreviation C O OU CN Fits this type of object Country Organization Organizational Units All leaf objects

Client for Novell and Windows


Earlier, you learned how Novell Client software enables workstations to communicate with the network and to submit user names and passwords during the login procedure.

Windows Client Windows 95/98 comes with Microsoft Clients for NetWare, which you can use to connect to a NetWare server. However, this client software is not NDS aware, so a workstation running it does not take full advantage of NetWare 5 services. Novell recommends that you use the Novell Client for Windows 95/98. This workstation client takes full advantage of all NetWare 5 functionality.

After placing the CD in the drive, WINSETUP.EXE should launch automatically. If not, use Windows Explorer to find the file and launch it, and after installation launches, your first step is to select a language option.

Then select a client version. In this example, we are installing the client for Windows 95/98. Then select the option for installing the Novell Client. Novell requires you to accept the terms of their license agreement before installing

Typical or Custom The Typical installation uses default settings that most users need, while the Custom option lets you select exactly what is installed. For illustration purposes, we will use the Custom option. Select a Protocol Select a protocol option based on the protocols used by your network. The protocol and any other necessary drivers will be installed. Select IP and IPX.

NDS or Bindery You must select either the NDS or Bindery connection option. Clients that log in to a NetWare 4 or 5 server will need NDS. Clients that log in to a NetWare 3 server will connect to the bindery

Custom Options Custom options allow you to add additional functionality to the client. For example, to use network printing, certain NDPS software must be installed on the workstation. Also, if you want to download applications to the workstation or perform other management tasks remotely, you must install Novell Workstation Manager. These custom options can be installed later. However, planning the needs of the workstations and installing the options now can make your work easier.

After the client software is installed, you're prompted to reboot the workstation. It must be rebooted for the client to become active. Rebooting immediately enables you to check that the client is functioning correctly. But you might want to wait to reboot if you have additional work to perform on that workstation.

Two key changes occur because of the client installation. First, the Novell log in dialog box appears when the client boots the computer. Second, Novell's icon is added to the system tray. Windows 95/98 users can also launch the login dialog box from the Novell icon, the Start menu, or LOGINW95.EXE in the Novell\Client32 directory.

Client Configurations
You can control some of the workstation's network related activities by configuring the client. These configurations will affect every person who uses the workstation to access the network. If your users share stations or frequently use different stations, you might want to minimize the configurations you set. However, if one person uses the same computer every day, setting client configurations can make the login procedure quicker. To access client configurations, use the Control Panel. From the Start menu, point to Settings, and click Control Panel. With the Control Panel open, double-click the Network icon to open the Network dialog box. Select the Novell NetWare Client and click Properties.

Client Tab The Novell NetWare Client Properties dialog box offers quite an assortment of configuration options. Client tab to set default login information. The information you enter has to match information specified for the User object in NDS. For example, you might use the Name context box to set the context a user needs in order to log in. This context is the NDS location of the User object.

Contextless login relieves users of the need to enter their login context. Without it, users must enter the NDS context of their User object when logging in. Contextless login requires the login server to run Cataloging Services, and it uses more server capacity than traditional login.

Protocol Preferences. Beginning with clients for NetWare 5, Novell defaults to a preference for IP. So if you install both IP and IPX on a workstation, the station will attempt to use IP first when sending and receiving packets. Use this tab to change the protocol preference, if you wish.

Advanced Settings The Advanced Settings tab gives you access to several parameters. For example, you can use Cancel Desktop Login to prevent users from using their workstations when not logged into the network. By default, this parameter is set to Off. Select any parameter from the list, and select an option from the Settings list.

To log in, a user enters her username and password, which were created when her account was created. She then clicks OK to log in (assuming her network uses contextless login, or her context has already been set). A user might also need to set Advanced options Advanced options allow users to specify login information. If contextless login isn't in effect, users typically need to enter Tree and Context information the first time they log in. It is then stored for future logins. Logging in from a different machine than usual may require changing this information. For example, if admin's User object is not in the Sales.OurCo NDS container, he will need to change context. Users can enter their context or use the browse button beside the box to locate it. After the settings are entered, click OK to log in The version of NetWare Administrator that you use depends on the operating system of your Windows workstation. Versions of the application are located in subdirectories on the SYS volume in the Public directory. The examples in this course always use NWADMN32.EXE, unless noted otherwise. Workstation OS Windows 95 Windows 98 (or Windows 95 if the workstation is running a 32-bit version of Novell Client for Windows 95/98) Windows NT Application Version NWADMN95.EXE NWADMN32.EXE NWADMNNT.EXE Location SYS\Public\Win95 SYS\Public\Win32 SYS\Public\WinNT

You can use Windows Explorer, Network Neighborhood, My Computer, or the DOS prompt to launch NetWare Administrator. Here, we could double-click NWADMN32.EXE to launch the application.

Follow these steps to create a User object with NetWare Administrator: In the tree, select the container where you want to create the object. In this example we'll create a User object in the CompNetSupp container From the Object menu, choose Create. In the Class of new object list, choose User and then click OK In the Create User dialog box, enter the Login name, also called a common name, for the user. This name is also the name of the User object. Make sure that the Login name follows the naming standards established for your network. You must enter a Login name In the Last name box, enter the user's complete last name. You must enter a value in this box. You do not have to use the remaining options on this dialog box. You'll learn about templates and defining additional properties later in this unit. Therefore, we'll briefly review the Create Home Directory and Create another User option.

Home Directory
The Create Home Directory option enables you to create a network file system directory where the user can store files. Use the browse button to select the volume or directory where the new directory will be located. In the Home Directory box, enter a name for the directory. Usually this name should be the login name. After you have entered the required information and selected any additional options, click Create to create the new User object

The User object is created and appears in the NDS tree.

You manage NDS objects by manipulating the objects' property values. In this example, you learn to manage User objects. However, managing all NDS objects follows this same basic procedure. To view and change property values, select an object. From the Object menu, choose Details to open the object's properties dialog box. You can manage several User object properties. Properties are grouped on pages, and you access these pages by clicking the buttons along the right side of the dialog box. You'll learn the details of managing these properties in other courses of this series. Now, let's review the Identification page properties.

The Last name box contains the name you entered when you created the User object. All of the other information on this page is optional. You should enter a name in either the Given name or Full name boxes. A user's full name might not fit into your Login name naming convention. For instance, you might have User objects named CLongen1 and CLongen2. In the Full name box, you can specify that CLongen1 represents Clarisa Longenberger.

Earlier, when you created a User object, you saw the option to use a Template object. You use a template to do two things: Create User objects that share the same properties

Update the property values of all users created from that Template object Select the container where the object will be used. Select the container where the object will be used. In the Class of new object list, select Template In the dialog box, enter a name for the template. You must enter a name for a Template object In the Template object's properties dialog box, enter any values you wish all of the User objects to share. Here we entered department information. After entering values, click OK to create the object. The template is now ready to use.

Login Security Features


Login security has four features: Account restrictions Password restrictions

Intruder Detection Authentication

On the Login Restrictions page, you can select three options. The Account disabled option prevents a user from logging in. You can set this option temporarily and reactivate the account later. The Account expiration date option allows you to disable an account on a preset date and time. The Limit concurrent connections option determines how many logins a user can have at one time. For example, if this limit is two, then a user can log into the network from one workstation and then login from a second workstation. You can also limit the hours during which a user can login. On the Login Time Restrictions page, you can limit the hours during which a user can login. Select the hours that a user cannot login and click Reset. The restricted hours appear in gray.

On the Network Address Restriction page, enter network addresses of workstations from which the user can log into the network. Click Add to enter an address. In the protocol options group, select the protocol used by that address. The Account Balance page enables you to regulate how much the user uses one or more network resources. For example, you can limit a user to being logged in only 100 hours during a month. In order to use this feature, Accounting must be set up on every server in your network, and each server must have the bindery setup. On each server, you select the services for which there will be a charge and the charge rate. For example, you might charge one point for one hour of login time. By default, the user is allowed unlimited credit You use the Password Restrictions page to specify how the password option functions and to set passwords. If you want, you can prevent users from setting their passwords. You do not have to require passwords with user accounts. However, to secure your network, you should use them. Passwords must be at least five characters up to a maximum of 128 characters. The Intruder Detection feature detects and records information about failed login attempts due to incorrect passwords. This feature also can lock an account after a set number of attempts.

ConsoleOne
ConsoleOne is a Java-based utility that you can use to create these NDS objects: User Group Organization Organizational Unit

ConsoleOne can be run on either the server or any workstation that has the Novell Client software and Java Runtime Environment (JRE) installed. The JRE is automatically installed with the NetWare operating system. This course shows you how to use ConsoleOne from a Windows 98 workstation. To create a User object with ConsoleOne, start in Windows Explorer and navigate to the SYS volume's Public\mgmt\ directory. Double-click Console1.exe.

In the tree pane of ConsoleOne, select the container where you want to create the User object. In this case we'll be placing the new User object in the CompNetSupp container. Open the File menu and choose User from the New submenu. In the New User dialog box, enter a login name and last name, then click Create In the Create Authentication Secrets dialog box, if the Tree and Context boxes are empty, enter the information for where the User object will be created in the NDS tree. This information appears automatically if you selected the container object (i.e., context for the User object) in Step 2. Enter a password and click OK. The User object appears in the display pane

UIMPORT is a command-line utility that enables the administrator to create multiple User objects by using an ASCII text file and a control file. In situations where a large number of user accounts need to be brought into NDS from a different platform, UIMPORT enables the creation to be automated.

Consider this example. When employees are hired, a personnel department creates a record for each employee in a database. The record contains information about the employee's name, the department where he works, and his employee ID numbers. At the end of each week, the personnel department exports the information for the employees hired that week to an ASCII text file, which is sent to you, the network administrator. Then, you use that file to create User objects and set up accounts. ASCII Text Files To use UIMPORT, you need two ASCII text files: A comma-delimited text file that has the user data. This file is named with a .DAT extension. A control file that is named with a .CTL extension. UIMPORT uses information in the control file to know where to create the User objects and how to organize and read the field values in the data file. Here's an example of a UIMPORT control file named control.ctl. There are many Import control parameters. This example shows only three that you must use Name context specifies the container in which the users will be created. The Separator specifies the character used in the data file to separate field values. In this case we're using commadelimited files. The Import Mode field uses four possible values: B for updating property values of existing User objects or creating new User objects C only for creating User objects U only for updating property values of existing User objects R for removing or deleting User objects listed in the data file from NDS Fields represent properties of User objects. For a complete list of the fields you can use, check the UIMPORT help. Just like when you create User objects with NetWare Administrator, you must use the Name and Last Name fields. The Name field represents the username assigned to the User object. F:\public> UIMPORT [path:\]controlfile [path:\]datafile

Logging Into Your Novell Account

from Windows 95/98


To login to your Novell account, all you need to know your username and password - nothing more. Your Novell username is usually the same as your First Initial and Last Name. Another example is usernames with the first 5 letters of their last name + the first letter of their first name + the last 2 digits of their SSN. The initial password is the student's SSN without any dashes or spaces. For example, Jane J. Smith has a SSN of 123-45-6799, so her username is smithj99 and her initial password is 123456799. Step 1. If the PC is turned off, turn it on and go to step 2. If the PC is on and waiting at the "Novell Login" screen, go to step 2. If the PC is already on and the Windows 95 status bar is displayed, click on the "Start" button and click on "Shut Down...". The "Shut Down Windows" dialog box will appear. Click on "Restart the computer?" and click on "Yes". Step 2. When the PC has finished its process it will stop at the "Novell Login" dialog box. The screen will prompt you for your Username and Password. Step 3. Type your username in the "Username" field and press [Tab]. Type your password in the "Password" field and press [Enter]. Step 4. If this is the first time you have logged into your Novell account, or your password is older than 180 days, the "Confirm..." screen will notify you that your password has expired and ask you if you want to change your password. Click on "Yes". If you do not get this "Confirm..." screen, go to step 7. Step 5. The Novell "Change Password" dialog box will prompt you for a new Novell password. You must use a password that is at least 5 characters long. Note: Academic Computing recommends that when selecting a password you do not use any word that can be found in a dictionary or familiar names and dates. The best type of password is a cryptic combination of letters, numbers, and/or symbols. Step 6. Type your new password in the "Enter new password:" field and press [Tab]. Retype your new password in the "Retype new password:" field for verification, and press [Enter]. If you enter an invalid password the screen will prompt you for the information again. Step 7. A "Change Windows Password" dialog box may appear and prompt you for and new Windows password. If it does, press [Enter] or click on "OK". If the dialog box does not clear, press [Esc] or click on "Cancel" to clear it. Step 8. When both the Novell system and Windows have authenticated your username and password, your Novell login script will run. The login script will automatically configure the PC environment for you. When it is complete, it will close. Congratulations! You have successfully logged into the Novell Network. IMPORTANT - Please remember to logout of your Novell account before you leave the PC. If you do not, the next person that uses the PC will have access to your account and your files.

From a Windows NT Workstation


These instructions will take you through the process of logging into your personal Novell account from a Windows NT Workstation in the General Access Computer Labs.

Step 1. If the PC is turned off, turn it on and go to step 2. If the PC is on and waiting at the "Begin Login" screen, go to step 2. If the PC is already on and the Windows NT status bar is displayed, click on the "Start" button and click on "Shut Down...". The "Shut Down Windows" dialog box will appear. Click on "Close all programs and log on as a different user?" and click on "Yes". Step 2. When the PC has finished its process it will stop at the "Begin Login" window. The screen will prompt you to press [Ctrl-Alt-Del] (all at the same time) to begin the login process. Step 3. When you press [Ctrl-Alt-Del], the "Novell Login" window will open and prompt you for your Username and Password. Type your Username in the "Username" field and press [Tab]. Type your password in the "Password" field and press [Enter] or click on OK.

Step 4. The "Windows NT/2000 Workstation" window will open and prompt you for another name and password. Do not enter or change any information in this dialog box, simply press [Enter] or click on OK.

Step 5. If this is the first time you have logged into your Novell account, or your password is older than 180 days, the "Confirm..." screen will notify you that your password has expired and ask you if you want to change your password. Click on "Yes". If you do not get this "Confirm..." screen, go to step 7. Step 6. The "Change Password" dialog box will prompt you for a new Novell password. Type your new password in the "Enter new password:" field and press [Tab]. Retype your new password in the "Retype new password:" field for verification, and press [Enter] or click on OK. If you enter an invalid password the screen will prompt you for the information again. Note: Passwords must be at least 5 characters long. Academic Computing recommends that when selecting a password you do not use any word that can be found in a dictionary or familiar names and dates. The best type of password is a cryptic combination of letters, numbers, and/or symbols. When you have successfully changed your password the login process will continue. Step 7. When both the Novell system and Windows have authenticated your Username and password, the Novell login script will run and the Windows NT desktop will open. Congratulations! You have successfully logged into the Novell Network on a Windows NT Workstation. IMPORTANT - Please remember to logout of your Novell account before you leave the PC. If you do not, the next person that uses the PC will have access to your account and your files.

Control Panel Novel Netware

List of Control Panel applets


The applets listed below are components of the Microsoft Windows control panel, which allows users to define a range of settings for their computer, monitor the status of devices such as printers and modems, and set up new hardware, programs and network connections. Each applet is stored individually as a separate file (usually a .cpl file), folder or DLL, the locations of which are stored in the registry under the following keys:

HKLM\SOFTWARE\Microsoft\Windows\Current Version\Control Panel\Cpls


This contains the string format locations of all .cpl files on the hard drive used within the control panel.

HKLM\SOFTWARE\Microsoft\Windows\Current
Version\Explorer\ControlPanel\Namespace This contains the location of the CLSID variables for all the panels not included as cpl files. These are commonly folders or shell applets, though Windows Vista allows physical programs themselves to be registered as well. The CLSID then allows items such as the icon, infobox and category to be set and gives the location of the file to be used. The control panel then uses these lists to locate the applets and load them into the control panel program (control.exe) when started by the user. In addition to using the control panel, a user can also invoke the applets manually via the command processor. For instance, the syntax "Control.exe inetcpl.cpl" or "control.exe /name Microsoft. InternetOptions" will run the internet properties applet in Windows XP or Vista respectively.

Standard applets
Accessibility Options (Access.cpl) Allows users to configure the accessibility of their PC. It comprises various settings primarily aimed at users with disabilities or hardware problems.

The behavior of the keyboard can be modified, this is aimed at people who have difficulty pressing key-combinations, or pressing a key just once. (StickyKeys, FilterKeys and ToggleKeys) Behavior of sounds can be modified. (SoundSentry and ShowSounds) High contrast mode can be activated. The keyboard cursor can be customized.

The mouse pointer can be controlled using the keyboard. (MouseKeys)

Note that in the next generation of Windows, the Ease of Access control panel superseded the simple access.cpl control panel in previous versions. Add New Hardware (hdwwiz.cpl) Launches a wizard which allows users to add new hardware devices to the system. This can be done by selecting from a list of devices or by specifying the location of the driver installation files. Add or Remove Programs (appwiz.cpl) (Renamed Programs and Features in Windows Vista and later) The Add/Remove Programs dialog allows the user to manipulate software installed on the system in a number of ways; Allows users to uninstall and change existing software packages, as well as indicating how much space individual programs take and how frequently they are used.

Allows users to manually install software from a CD-ROM or Floppy Disk, and install add-ons from Windows Update. Allows users to change which Windows components are installed, via the Windows setup Wizard, which includes Internet Explorer,Windows Media Player and Windows Messenger Finally, it allows users to specify the default applications for certain tasks, via the 'set program access and defaults' wizard, such as internet browsers, media players and email programs and whether

access to these programs is available Administrative Tools (control admintools) Contains tools for system administration, including security, performance and service configuration. These are links to various configurations of the Microsoft Management Console such as the local services list and the Event Viewer. Automatic Updates (wuaucpl.cpl) This is used to specify how the Automatic Updates client (wuauclt.exe) should download updates from the Microsoft Update Website, by default this is set to download and install daily, however this can be changed to a more suitable frequency. This also allows the user to specify whether to ask permission before downloading and/or installing updates or to simply switch off Automatic Updates all together. Date and Time (timedate.cpl) Allows user to change the date and time stored in the machines BIOS, change the time zone and specify whether to synchronize the date and time with an Internet Time Server and which server to use. Display (control desktop) (desk.cpl)

Allows the user to change the display characteristics of their computer;

Allows users to change the desktop background (wallpaper) to a picture of their choice and specifies how it should be shown. Allows the user to change or disable the screensaver, and specify how long it takes to activate and whether to ask for a password on resume Allows the user to specify the color styles of all elements within the system, primarily whether to use the Windows XP / Vista styles (blue by default in XP) or to use the classic Windows 98 / Mestyles, this also allows the user to change the My Computer and Recycle Bin icons.

Allows the user to change the screen resolution and colour quality, and provides trouble shooting advice for displays. Folder Options (control folders)

This item allows for configuration of how folders and files are presented in Windows Explorer. More specifically it allows the user to specify general settings like whether folders open in a new window or the existing window and whether the common tasks pane is shown, as well as more advanced tasks such as whether windows should hide critical system files and whether to show file extensions. It is also used to modify file type associations in Windows; i.e., which program opens which type of file and other settings like actions for each file type and the file extension. Fonts (control fonts) Displays all fonts installed on the computer. Users can remove fonts, install new fonts or search for fonts using font characteristics. Note that "explorer \Windows\Fonts" has the same effect. Internet Options (inetcpl.cpl) Allows the user to change the way the computer manages internet connections and browser settings for Internet Explorer, it has several tags specifying different attributes;

General - This specifies the homepage and color schemes and allows the user to delete internet usage history. Security & Privacy - These specify whether the computer should allow websites to undertake certain processes and download cookies, this panel also gives access to the inbuilt pop-up blocker

(Windows XP SP2 and later) and the phishing controls (Internet Explorer 7).

Content - Allows the parental controls and auto-complete to be configured and also specifies how to deal with certificates. Connections, Programs and Advanced - These give access to other aspects of internet settings such

as the default modem connection and email client, proxy settings and other advanced configurations. Game Controllers (joy.cpl) Allows you to add, display, troubleshoot, and use advanced settings on joysticks and game controllers Keyboard (control keyboard) Lets the user change and test keyboard settings, including cursor blink rate and key repeat rate. Mail (mlcfg32.cpl) (mlcfg.cpl) Mail allows for configuration of the mail client in Windows, usually Microsoft Outlook. Microsoft Outlook Express cannot be configured with this item; it is configured through its own interface. mlcfg.cpl is used for 64 bit office applications first available with the Office 2010 release. Mouse (control mouse) (main.cpl) Mouse allows the configuration of pointer options, such as the double click and scroll speed, and includes visibility options such as whether to use pointer trails and whether the pointer should disappear when typing. This also allows the user to specify the pointer appearance for each task, such as resize and busy. Network Connections (control netconnections) (ncpa.cpl)

Displays and allows the user to edit or create network connections such as Local Area Networks (LAN) and internet connections. It also offers troubleshooting functions in case the computer has to be reconnected to the network. Phone and Modem Options (telephon.cpl) Manages telephone and modem connections. Power Options (powercfg.cpl) Includes options to manage energy consumption such as;

Specify how long it takes to switch off the display and hard drives and how long it takes for the system to enter standby, if at all. To decide what to do when the computer's on/off button is pressed, such as whether to shut down or to enter standby. Whether to allow Hibernation (some systems become unstable when restarting). Allows the user to configure UPS (if available). Printers and Faxes (control printers)

Displays all the printers and faxes currently installed on the computer, and has two main uses;

Firstly, it shows the all the jobs queued for each printer, the file size and status of each job and which user they belong to, it also allows each job to be paused, canceled or moved up or down the list. Secondly, it allows the user to set the printing or faxing preferences, such as paper size and quality via the manufacturers own preferences pane and also specifies how to share the printer across

a computer network , the device drivers, ports etc. Regional and Language Settings (intl.cpl) Various regional settings can be altered, for instance:

The way numbers are displayed (e.g. decimal separator). How Currency values are displayed, including the Currency sign. Time and date notations, such as the date separator and whether the clock should be in 12 or 24 hours.

Cultural location of the user's computer (The time zone is set in Date and Time). Language; Input language. Keyboard layout (mapping between key strokes and characters). Display language for Menus and Dialog Boxes.

Whether files necessary for Asiatic language support must be installed. Installed code pages.

Security Center (wscui.cpl) Renamed "Action Center" in Windows 7 First added in Windows XP with Service Pack 2, Security Center gives the user access to the inbuilt Windows security components, as well as providing information about any existing antivirus software such as McAfee or Zone Alarm. It includes access to Windows Update, where users can specify whether the computer should check for updates regularly (also available through the Windows Update panel), and options for managing internet security settings. It also includes links to internet articles about PC security and current virus threats and notifies the user when the PCs security is compromised. Sounds and Audio Devices (mmsys.cpl) This panel contains various audio-related functions; Change the speaker volume and type and specify whether to show the volume icon in the notification area. Change the sounds played for the system or specific programs when a certain event occurs, i.e. Windows Startup or Critical Stop.

Change default devices for music playback, recording, voice recognition, MIDI etc. Change the Sound card settings and whether to use Hardware acceleration.

Display the audio devices installed on the computer, and allows them to be configured. Speech (Sapi.cpl) This applet has two main functions, the first is specify settings for Speech synthesis, allowing the user to select the voice the computer should use to narrate text and how fast it should read. The second is to specify settings for Speech recognition, allowing the user to set up different profiles detailing how the computer should deal with an individuals dialect, for instance; The amount of grammatical errors in a persons voice (punctuality sensitivity). The speed at which the person speaks, and the time delay between words.

This also allows the user to access the voice recognition training wizard, in which an individual 'teaches' the computer to recognize a person voice interactively using the microphone. System (Sysdm.cpl) This is used to view and change core system settings, a user can for instance:

Display general information on the user's machine such as the amount of RAM, CPU speed and type, the version of Windows the system is using and the manufacturer. Edit the computer name in a network workgroup. Manage and Configure hardware devices, and view information such as the manufacturer, user access and driver version of any hardware device installed on the system via Device Manager. Enable/Disable system features such as automatic updates and System restore monitoring.

Specify advanced features such as performance logs, virtual memory settings and roaming profiles. Taskbar and Start Menu (rundll32.exe shell32.dll,Options_RunDLL 1) Allows the user to change the behavior and appearance of the task bar and Start Menu;

Specifies whether to use Windows XP/Vista or Classic 9x/Me styles on the taskbar and start menu. Whether the taskbar should Auto-Hide. Whether to show the clock in the notification area. Allows the user to manage the tray icons. Advanced options such as whether to show Printers & Faxes in the start menu and whether to

display My Documents as a menu or as a link to a new window. User Accounts (nusrmgr.cpl) This allows the user to configure their account and other accounts used in the system, should they have sufficient privileges. They can change their username and password, their picture (if enabled) and their .net passport. If the current user has an administrators account they can also add, delete and modify other user accounts as well as make changes to core system settings. This panel also specifies whether the guest account should be active and whether to use the Welcome screen while Windows loads. Interoperating with NetWare

Understanding NWLink
Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Understanding NWLink
The NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (NWLink) is a Network Driver Interface Specification (NDIS)-compliant, native 32-bit implementation of Novell's IPX/SPX protocol. NWLink supports two networking application programming interfaces (APIs): NetBIOS and Windows Sockets. These APIs allow communication among computers running Windows and between computers running Windows and NetWare servers. The NWLink transport driver is an implementation of the lower-level NetWare protocols, which include IPX, SPX, RIPX (Routing Information Protocol over IPX), and NBIPX (NetBIOS over IPX). IPX controls addressing and routing of packets of data within and between networks. SPX provides reliable delivery through sequencing and acknowledgments. NWLink provides NetBIOS compatibility with a NetBIOS layer over IPX.

Interoperating with NetWare resources


Depending on what platform you are using and what resources that you want to access, you may need to use NWLink in conjunction with other tools. The following table lists several interoperability options that use NWLink.

Platform Windows Windows NetWare client

Running NWLink NWLink and Client Service for NetWare IPX with NetBIOS, Named Pipes, or Windows Sockets support IPX

Can connect to Client/server applications running on a NetWare server NetWare servers for file and print services

Computers running Windows (with NWLink installed) running IPX applications such as Microsoft SQL Server NetWare client Servers running Windows Server 2003 (with NWLink installed) for file and print services For a Windows client to access file and print resources on a NetWare server, Client Service for NetWare must be installed on the Windows client in addition to NWLink. For more information, see Novell NetWare integration overview.

Interoperating with Microsoft resources


By default, the file and print sharing components of Windows use NetBIOS over IPX to send file and print sharing messages. Alternatively, you can disable NetBIOS so that the file and print sharing messages are sent directly over IPX. This is known as direct hosting. While direct hosting may be more efficient, it causes an interoperability issue: A direct hosting client can only connect to a direct hosting server. Direct hosting clients include computers running Microsoft Network Client for MS-DOS, Windows for Workgroups, Windows 95, and Windows 98. Direct hosting servers include computers running Microsoft Network Client for MS-DOS, and all Windows-based computers. The following table lists several interoperability options that use IPX.

Platform Microsoft Network Client for MSDOS Windows for Workgroups Windows 95 Windows 98

Running IPX only (direct hosting)

Can connect to File and print shared resources on computers running: Microsoft Network Client for MS-DOS Windows for Workgroups Windows 95 Windows 98 Windows NT Windows 2000

Microsoft Network Client for MSDOS Windows for Workgroups Windows 95 Windows 98 Windows NT Windows 2000 Important

NetBIOS over IPX

File and print shared resources on computers running: Microsoft Network Client for MS-DOS Windows for Workgroups Windows 95 Windows 98 Windows NT Windows 2000

You cannot use direct hosting of IPX to gain access to resources on any computer acting as a direct host server from a computer running Windows. Computers running Windows do not include a direct hosting client for NWlink. For example, while you can connect by using direct hosting of IPX to resources on a computer running Windows from a computer running Windows 95 or Windows 98 (where NetBIOS is disabled by default for performance reasons), you cannot connect by using direct hosting of IPX to the computer running Windows 95 or Windows 98 from the computer running Windows. For detailed instructions about enabling direct hosting, see Enable direct hosting of IPX. Client Service for NetWare is not available on 64-bit versions of Windows Server 2003 and Windows XP. Gateway Service for NetWare is included in Windows 2000 Server. It is not included in the Windows Server 2003 family. Computers running operating systems in the Windows Server 2003 family cannot be IPX routers.

You might also like