Home > Articles > Operating Systems, Server > Microsoft Servers

Mapping UNIX/Linux Shares On a Windows Server 2003 Network

  • Print
  • + Share This
Mapping drives from a UNIX/Linux file server doesn't only expand the scope of user storage on your network; it is also a good way for getting rid of complicated worms or viruses on a Windows network. Jesse Smith demonstrates dynamically mapping UNIX/Linux shares on a Windows Server 2003 network.
Like this article? We recommend

If you're an administrator, you are probably familiar with mapping drives on hybrid Windows and UNIX/Linux networks. Although there are numerous ways to do this, the most popular way is to use Samba. This article shows you how to map your UNIX/Linux drives dynamically to users' logging into your Windows 2003 network. With this configuration, a user on your network can log in to any workstation on the network, and the UNIX/Linux drives assigned to them will automatically be mapped to them once logged in. It works well because the drives are dynamically mapped at login time and thus become "roaming" drives. Furthermore, a user only needs to login into the domain. No other login is required to get access to the UNIX/Linux drives.

Mapping drives from a UNIX/Linux file server doesn't only expand the scope of user storage on your network; it is also a good way for getting rid of complicated worms or viruses on a Windows network. You might be asking yourself how this might be so.

Most virus-scanning programs have a folder that you can designate for routing infected files to that cannot be cleaned or deleted. The more complicated viruses or worms often have permissions placed on the files so that the worm can be spawned on the infected machine over and over, thus not allowing you as an administrator or a virus program to clean or remove these core files. Once the infected files are found and routed to a UNIX/Linux file share, they can be easily deleted or removed because the Windows permissions are not understood by the UNIX/Linux file system.

The first part of setting up this configuration is working with Samba, which is a service and management tool that allows you to easily share your UNIX/Linux folders on a Windows network—much like a Windows workstation or server would. Most UNIX/Linux distributions come with one version of Samba or another. The best way to quickly configure the Samba service (or daemon) is by going directly to the Samba configuration file. In the next section, we'll be taking a look at a typical basic configuration of this file. We'll tweak it for our own purposes so we can share any files and folders we want to from our UNIX/Linux system in a Windows domain.

Configuring Samba

Configuring Samba could be an article in itself, so I'll focus only on the sections we need to look at. For purposes of illustration, I will lay out what you should see or have in a similar manner regarding these sections in which your configuration file is concerned. Editing the Samba configuration file (smb.conf) is easy because they are similar to Windows .ini files.

To configure Samba, bring up the smb.conf file on your UNIX/Linux system. The type of flavor or distribution you are running will determine the location of this file. For example, the Linux Redhat distribution has it in a different location (etc/samba/smb.conf) than does Mac OS X running the Darwin flavor of UNIX (usr/local/samba/lib/). Once you locate the file, bring it up in an editor you're comfortable using (Pico, for instance).

Each section of this file is denoted by the section name in brackets. For example, the main section of a typical Samba configuration file is called global, and is denoted with brackets as [global]. Although there are many sections you can add to a basic configuration, we're going to be concerned only with the global and disk shares sections we create. Starting with the global section, let's take a look at what needs to be tweaked here for our Windows domain to pick up the shares we'll later define. You should see a line similar to the following:

workgroup = WORKGROUP

Replace the default parameter WORKGROUP with the name of your Windows server 2003 domain. Your Samba server will appear in this domain. If this line contains a semicolon at the beginning, remove it so that the parameter will become active when the Samba service is started.

Next, we need to make sure that our machine advertises itself with a NetBIOS name for a Windows network. Find the following line to define which name your Samba server will broadcast on the network.

netbios name = hostname 

The name you give would appear in My Network Places on a Windows XP client, for example. You can put any name you like here, and can also leave the parameter as hostname. By leaving it as hostname, the Samba server will advertise itself by its hostname. If you do not show this line in your default configuration, add it anywhere to the global section.

If you're concerned about security and limiting the scope of machines to which your Samba server will allow access, find the line similar to this one:

hosts allow = 192.168.2.0/255.255.255.220

In this example, I am telling the Samba service to authenticate only machines that have an IP within the range of 192.168.2.1 to 192.168.2.35, inclusively. You can define other ranges or subnets by putting a space between each range.

Because Windows clients (after the release of Win95 Band NT 4.0 Service Pack 3) use encrypted passwords to authenticate share access, Samba should also be set to behave similarly. You can set Samba to use encrypted passwords by removing the semicolon from the line encrypt passwords = yes to activate it.

The parameters above have everything to do with how our Samba server broadcasts itself on a Windows network and handles password authentication. They are all we really need to look at in the global section. Now let's take a look at how to define the network shares our Samba server will contain.

Defining Network Shares

The basic default configuration of your smb.conf file will probably have some share definitions or examples. The easiest thing to do is to copy one of these examples and tweak it for your own needs. For example, let's say I want to have a network share called Accounting. I would create a section similar to the one shown below:

[Accounting]
path = /Smb_Act
public = yes
printable = no 
writable = yes

The first line specifies the alias for the share name and also serves as a section indicator for the share. It will give the virtual share name Accounting to the physical share called Smb_Act on our Samba server. The path line tells Samba where to look on the server for the files to share. The third line indicates that this share will need passwords to gain access (I'll talk more about this later). If we indicate a yes here, no authentication is needed to access the share. If you want to allow access to only certain users, you would add the line valid users = and list each Samba user (discussed in the next section), separated by a space that will have access. The fourth line indicates that this is not a print share. All printer shares must have this value set to yes. The last line indicates whether the Accounting share can have files saved or added to it by Samba users.

These are some of the most common parameters when creating a share and should give you a good idea of how to model your share sections. We're now done configuring our smb.conf file, and it's time to create Samba user accounts.

Creating Samba User Accounts

Creating Samba user accounts is an important step because without it, you users could not gain access to the Samba service. It is also very important for Windows domains, as you will see in a bit.

I said at the beginning of this article that a domain user would only to have to log in into the domain, and access to Samba shares would then become available depending on their domain login script—in the same manner as any other Windows network shares. The key here is that when you create a Samba user, make sure that the user has the same credentials as their Windows domain account does.

For example, let's say I have a domain user called Ted. He is an accountant, and I want to give him access to the Samba Accounting share created in the previous example. First, the user must already have a local system account on your UNIX/Linux box acting as your Samba server. In other words, Ted should already have an account on the server. If he doesn't, I would first need to create one before giving him a Samba account.

To give a user a Samba account (Ted in this example), go to the command prompt as root and type the following command:

smbpasswd –a Ted

You will then be prompted to enter a password for the new Samba user. Make sure that it is the same password as the user's Windows domain account. Add all your users in this manner; once finished, you'll need to make sure that the Samba and NetBIOS name services are started. To put it simply, the NetBIOS name service allows your Samba server to translate machine names on Windows networks to IP addresses. To start the Samba service, type the following command at the prompt as root.

smbd start

To start the NetBIOS name service, type the following command at the prompt:

nmbd start

After these services have been started or restarted, we can now go to our Windows domain controller and create or modify user logon scripts to map our new Samba drives, as described in the following section.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020