• Choose a category
• All
• Classic-Fiction

linux:~ # export CFLAGS="-Wall -O -D_GNU_SOURCE -D_LARGEFILE64_SOURCE"

linux:~ # gcc client/mount.cifs.c -o client/mount.cifs

linux:~ #install -m755 -o root -g root client/mount.cifs /sbin/mount.cifs

The system is now ready for configuration, so let's get on with some serious exercises in sharing files with the other world.

Accessing Remote Windows Files and Printers

Soon we will connect to a file share on a Windows system. We assume that the Windows system has a static IP address, and that we are not using DNS. Name resolution is rather important in networking operations, particularly with Windows clients, so let's configure the /etc/hosts file so that it has the following entry:

192.168.1.250 emacho

There should, of course, also be an entry for the IP address of the Linux system we are on.

Now check that the /etc/hosts entries are working:

linux:~ # ping emacho

PING emacho (192.168.1.250) 56(84) bytes of data.

64 bytes from emacho (192.168.1.250): icmp_seq=1 ttl=128 time=2.41 ms

64 bytes from emacho (192.168.1.250): icmp_seq=2 ttl=128 time=2.16 ms

64 bytes from emacho (192.168.1.250): icmp_seq=3 ttl=128 time=2.16 ms

64 bytes from emacho (192.168.1.250): icmp_seq=4 ttl=128 time=2.02 ms

64 bytes from emacho (192.168.1.250): icmp_seq=5 ttl=128 time=2.01 ms

64 bytes from emacho (192.168.1.250): icmp_seq=6 ttl=128 time=3.90 ms

--- emacho ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 5004ms

rtt min/avg/max/mdev = 2.015/2.447/3.905/0.667 ms

OK, it works. Now we are really ready to begin file sharing.

Using the FTP-like smbclient to access Windows

It makes a lot of sense to first establish that our Linux system can communicate with the Windows system using Samba. The simplest way to do this is to use the Samba client tool, the smbclient command, to query the Windows machine so it will tell us what shares are available.

Let's perform an anonymous lookup of the Windows machine:

linux:~ # smbclient -L emacho -U%

Domain=[MIDEARTH] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment

--------- ---- -------

Error returning browse list: NT_STATUS_ACCESS_DENIED

Domain=[MIDEARTH] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment

--------- -------

Workgroup Master

--------- -------

This is not very encouraging, is it? The lookup failed, as is evidenced by the reply Error returning browse list: NT_STATUS_ACCESS_DENIED. This is caused by a Windows machine configuration that excludes anonymous lookups . So let's repeat this lookup with a valid user account that has been created on the Windows XP Home machine.

An account we can use on our example system is for the user lct with the password 2bblue4u. Here we go:

linux:~ # smbclient -L emacho -Ulct%2bblue4u

Domain=[EMACHO] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment

--------- ---- -------

IPC$ IPC Remote IPC

SharedDocs Disk

print$ Disk Printer Drivers

Kyocera Printer Kyocera Mita FS-C5016N KX

Domain=[EMACHO] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment

--------- -------

Workgroup Master

--------- -------

Success! We now know that there is a share called SharedDocs on this machine. In the next step we will connect to that share to satisfy ourselves that we have a working Samba connection.

In this step we connect to the share itself, then obtain a files listing, and then download a file. This is an interesting example of the use of the smbclient utility:

linux:~ # smbclient //emacho/SharedDocs -Ulct%2bblue4u

Domain=[EMACHO] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

smb: \>

Success again! This is good. Now for a directory listing:

smb:\ dir

. DR 0 Thu May 19 12:04:47 2005

.. DR 0 Thu May 19 12:04:47 2005

AOL Downloads D 0 Tue Sep 30 18:55:16 2003

CanoScanCSUv571a D 0 Thu May 19 12:06:01 2005

desktop.ini AHS 129 Sun Jul 4 22:12:14 2004

My Music DR 0 Sat Apr 16 22:42:48