Like what you see? Get it in one document for easy printing!
Click Here!
Use coupon code "certiguide" to save 20%!
(Expires 2004/12/31)

NEW! Network+ N11-003 2005 Beta Exam Study Guide - Just $9!
Get It Here!

Custom Search







Table Of Contents  CertiGuide to Network+
 9  Chapter 0110: Network Operating Systems (NOS)
      9  IV  User Manager for Domains

Previous Topic/Section
IV  User Manager for Domains
Previous Page
Pages in Current Topic/Section
1
Next Page
Printing, Client Connectivity
Next Topic/Section

File Sharing, Client Connectivity

In Windows, you can share a folder by right-clicking on it, selecting the Sharing option, clicking the Share this Folder radio button, and filling in the appropriate details such as the name this resource will be identified by, to network users, and the description of what is found there.

A Windows client can access the folder by browsing for it in Network Neighborhood (My Network Places on Windows 2000), which is found on the desktop. Alternately, a shared folder can be accessed from the command line, via the net use command. To do this, you need to know the name of the shared folder and the server on which it is located. Once you know these things, you can map a local drive to the location of the shared folder, so that you can access that folder as if it was a local disk drive. To do this, use a command of the form:

NET USE X: \\ servername\sharename

Where X: is an unused drive letter you’d like to map the resource to, servername is the name of the server containing the resource, and sharename is the shared folder’s sharename. The \\ servername\sharename syntax is called a UNC (Universal Naming Convention) path. The UNC path begins with two backslashes \\. Following that is the name of the server and then a slash \ and the shared folder name. You’ll see that a similar UNC syntax is also used for mapping to network printers from the command line.

Client computers running other operating systems may be able to access files shared by a Windows computer if the operating system understands the Windows File Sharing protocol. (The most famous example of another client operating system that can access files shared by a Windows system is Linux, whose Samba utility allows it to do so. Of course, in Linux, it’s not a point-and-click GUI feature, but rather a facility that must be accessed by command line).

An interesting feature of some client versions of Windows is that they include the AppleTalk protocols for accessing Macintosh files and printers on the network. On some versions, such as Windows 2000 Professional, AppleTalk is installed by default.


Previous Topic/Section
IV  User Manager for Domains
Previous Page
Pages in Current Topic/Section
1
Next Page
Printing, Client Connectivity
Next Topic/Section

If you find CertiGuide.com useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider buying an inexpensive PDF equivalent of the CertiGuide to Network+ from StudyExam4Less.com. (Use coupon code "certiguide" by December 31, 2004 to save 20%!) Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

CertiGuide for Network+ (http://www.CertiGuide.com/netplus/) on CertiGuide.com
Version 1.0 - Version Date: November 7, 2004

Adapted with permission from a work created by Tcat Houser and Helen O’Boyle.
CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.