In addition to knowing how to configure a station’s hardware, you must be able to configure a Windows workstation to connect to the different types of network operating systems (NOSes) that might be on your network. For the Network+ exam, you should be able to configure these workstations to connect to the following operating systems:
The process for configuring Windows to connect to these various operating systems is basically the same for all server OSes (only the workstation software component differs very slightly), so we’ll just cover the two most popular client operating systems’ network configurations.
Configuring a Windows 9x Network
The configuration of a Windows 9x network centers on the Control Panel’s Network program. From this one interface, you can configure client software, protocols, NICs, and the network services you want this machine to perform. To access the Network program, select Start _ Settings _ Control Panel and double-click Network in the Control Panel window that appears.
Windows 9x will display the Network window. The Network window has three areas of interest: the Components list, the Primary Logon list, and the File and Printer Sharing button. If you already have some networking components installed, you can simply right-click the Network Neighborhood icon on your Desktop and choose Properties from the pop-up menu.
First, let’s review the four basic types of networking components that can be added in the Network panel. This screen can be reached by clicking Add on the Configuration tab.
The Select Network Component Type window
The networking components are as follows:
Client As mentioned before, the client is software that allows your machine to talk to servers on the network. Each server vendor uses a different way of designing its network access. Therefore, if a computer needs to get to both a Novell and a Microsoft network, the computer must have two pieces of client software installed, one for each type of server. The three network client groups supported by Windows 9x are for Microsoft, Novell, and Banyan servers.
UNIX/Linux clients are also supported natively, but they use their own set of tools (e.g., Ping, nslookup, etc.) and don’t require the installation of a client piece in this area.
Adapter The adapter is, technically, the peripheral hardware that installs into your computer, but in this case, it refers to the software that defines how the computer talks to that hardware. If you do not have the proper adapter software installed, your PC will not be able to talk properly to the NIC, and you will not be able to access the network until you change the adapter to one that is compatible with the hardware. It is often best to think of an adapter as simply a network driver, which is what it really is. Many adapters are supported by Windows 95, and Windows 98 and the more recent versions support even more, with support for more recent hardware. Adapter drivers can also be downloaded from most NIC vendors’ websites.
Protocol Once the client service and the adapter are installed, you have cleared a path for communication from your machine to network servers. The protocol is the computer language that you use to facilitate communication between the machines. If you want to talk to other people, you have to speak their language. Computers are no different. Among the languages available to Windows 9x are NetBEUI, NWLink (IPX/SPX), and TCP/IP.
Service A service is a component that gives a bit back to the network that gives it so much. Services add functionality to the network by providing resources or doing tasks for other computers. In Windows 9x, services include file and printer sharing for Microsoft or Novell networks.
Let’s suppose you want to connect to Microsoft servers on your network (including Windows XP, 2000 Server, 2000 Professional, Windows NT, or Windows 9x with sharing enabled). To connect to this network, you must have at least the following three components (services, the fourth component, are not required at this point):
To install a client and protocol for use with your network adapter, follow these steps:
When it is first installed, TCP/IP is configured to expect that a special server, called a Dynamic Host Configuration Protocol (DHCP) server, is available on the network to provide it with information about the network. If a DHCP server is not available, the protocol will not function properly. Consult your administrator to see whether the network uses DHCP or static addressing. In static addressing, all TCP/IP settings must be manually added, and in this case, you will need additional information from the administrator. The list of components should reflect your additions and show which network components are currently installed on this machine. If there are a number of components, a scroll bar appears on the right side of the screen. The scroll bar allows you to see all of the clients, network adapters, protocols, and services that might be installed. Once the client and protocol are installed, you will have all the software you need to connect to the network. At this point, just a few choices remain. Don’t close that Network program yet!
Selecting the software you want to install
Determining Your Primary Logon
A Windows 9x workstation can support multiple simultaneous network types. For example, a user can log in to both Novell and Microsoft networks, assuming that both network clients are installed and configured correctly. The Primary Network Logon drop-down list determines which network type you will log on to first. If you have not yet installed a network client, this list will only give you one option: Windows Logon.
We have already installed a Microsoft network client, so select the Client for Microsoft Networks as the primary logon.
Once you have made this selection, click OK. The Network program will close, and you will be asked to restart the computer so that the new settings can take effect. (You may also be asked for the location of any files that Windows can’t find, so you may have to insert your Windows CD.) Until you reboot, the network will not function. When the machine restarts, the network should be available.
Configuring a Windows 2000 Network Client
For the most part, the concepts behind configuring Windows 9x are the same as the concepts for configuring in Windows 2000. You still need a client, a protocol, and an adapter, for instance, but the difference is in how they are configured.
First, the Network program is now called Network and Dial-up Connections and is organized differently. When you first access the Network and Dial-up Connections window, you will see that, instead of a list of all components, you are greeted simply by a Make New Connection icon and a Local Area Connection icon.
To add client software and protocols, right-click the LAN connection and select Properties. You should find that everything you need is in place because the client and IP are installed by default on the LAN adapter.
The Network and Dialup Conncetion
Configuring Windows Clients for NetWare Network Access
Both Windows 9x and Windows 2000 handle the addition of a network client for NetWare in similar ways. Add (for Windows 9x) or install (for Windows 2000) the client, and the NetWarecompatible NWLink protocol will be automatically installed for you as well. Once you have these, you will be presented with a NetWare logon option screen on startup, where you can choose which NetWare server or tree you wish to log on to.
The tree is a group of machines that share security and configuration information. Both Novell’s NDS and Microsoft’s Active Directory use tree structures to store information and authenticate users. To access the NetWare tree more efficiently, frequent NetWare users should download the newest version of NetWare’s own client software for 9x/2000. It is available at www.novell.com/download.
Networking Related Tutorials
|Network Security Tutorial|
Networking Related Interview Questions
|Network Technical Support Interview Questions||Networking Interview Questions|
|CCNA Interview Questions||Network Security Interview Questions|
|Computer Network Security Interview Questions||Hardware and Networking Interview Questions|
|CCNP Interview Questions||Routing Protcol Interview Questions|
|CWNA (Certified Wireless Network Administrator) Interview Questions||Border Gateway Protocol (BGP) Interview Questions|
|Enhanced Interior Gateway Routing Protocol (EIGRP) Interview Questions||Virtual Private Network (VPN) Interview Questions|
|Controller Area Network (CAN bus) Interview Questions||Cisco Network Engineer Interview Questions|
|Storage Area Network Interview Questions||Network Troubleshooting Interview Questions|
Networking Related Practice Tests
|Network Technical Support Practice Tests||Networking Practice Tests|
|CCNA Practice Tests||Network Security Practice Tests|
|Computer Network Security Practice Tests||Hardware and Networking Practice Tests|
|CCNP Practice Tests||Routing Protcol Practice Tests|
|CWNA (Certified Wireless Network Administrator) Practice Tests||Border Gateway Protocol (BGP) Practice Tests|
|Enhanced Interior Gateway Routing Protocol (EIGRP) Practice Tests|
The Osi Model
Network Operating Systems
Wired And Wireless Networks
Wan And Remote Access Technologies
Network Access And Security
Fault Tolerance And Disaster Recovery
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.