Set up samba.

Sekar Thiagarajan sekar at ee.washington.edu
Sat Dec 22 18:37:00 PST 2001



In this scenario, it will help to have a WINS server installed with an
internal ip 192.168.0.xxx that will translate the wins name properly.
Your smb.conf should have "remote announce = 192.168.0.xxx"

Sekar..

============================================================
Sekar Thiagarajan Ph 206-221-5163
Mgr, EE Computer Operations Fax 206-543-3842
University of Washington sekar at ee.washington.edu
Seattle, WA 98125
============================================================

On Sat, 22 Dec 2001, William Rowden wrote:


> Needing transparent file transfer from Linux (Red Hat 7.2) and

> Windows 98, I started Samba. (NFS requires perhaps purchasing and

> then installing a client on several PCs. Windoze 98's handling of

> ftp sites is not consistent. That leaves SMB.)

>

> The Linux server knows itself as hurston at 192.168.0.1; there's no

> local DNS. As I understand it, the NetBIOS broadcasts should work

> without DNS. I find this broadcast network frustrating, though, as

> shares disappear as they time out and reappear on use. (BTW, the

> DHCP server is a router, not the Linux server.) Pings work to and

> from the Win98 boxes at various 192.168.0 addresses.

>

> Working through doc/samba-2.2.1a/docs/textdocs/DIAGNOSIS.txt, I get

> the following failure in "TEST 8" from the Win98 PCs:

>

> C:\WINDOWS>net view \\hurston

>

> Error 53: The computer name specified in the network path

> cannot be located. Make sure you are specifying the

> computer name correctly, or try again later when the remote

> computer is available.

>

> For this one of the suggested solutions is "fixup the nmbd

> installation." I'm confused, and recommendations for doing this

> would be welcome. I've set "log level = 2", but nothing appears in

> "/var/log/samba/log.nmbd" except messages about winning elections.

>

> I've tested "/etc/samba/smb.conf":

>

> [root at hurston samba]# testparm smb.conf

> ...

> Processing section "[tmp]"

> Loaded services file OK.

>

> >From the Linux box, "smbclient -L" works for all Linux and Win98

> shares. The only difference is that the Win98 boxes consider one of

> themselves the master, while the Linux box considers itself as

> master. The following setting in "smb.conf", however, results in an

> unbrowseable network for the Win98 boxes when `smbd` restarts:

>

> preferred master = yes

>

> Note that "smb.conf" file has the following:

>

> [tmp]

> comment = Temporary file space

> path = /tmp

> read only = yes

> public = yes

>

> In case it helps, here are some of the previous tests:

>

> [root at hurston samba]# nmblookup -B hurston __SAMBA__

> INFO: Debug class all level = 2 (pid 11322 from pid 11322)

> added interface ip=192.168.0.1 bcast=192.168.0.255

> nmask=255.255.255.0

> querying __SAMBA__ on 127.0.0.1

> Got a positive name query response from 127.0.0.1 ( 192.168.0.1 )

> 192.168.0.1 __SAMBA__<00>

>

> [root at hurston root]# nmblookup -d 2 '*'

> INFO: Debug class all level = 2 (pid 11542 from pid 11542)

> added interface ip=192.168.0.1 bcast=192.168.0.255

> nmask=255.255.255.0

> querying * on 192.168.0.255

> Got a positive name query response from 192.168.0.3 ( 192.168.0.3 )

> Got a positive name query response from 192.168.0.5 ( 192.168.0.5 )

> 192.168.0.3 *<00>

> 192.168.0.5 *<00>

>

> [root at hurston root]# smbclient //hurston/tmp -Uguest%

> INFO: Debug class all level = 2 (pid 11543 from pid 11543)

> added interface ip=192.168.0.1 bcast=192.168.0.255

> nmask=255.255.255.0

> Anonymous login successful

> Domain=[HARLEM] OS=[Unix] Server=[Samba 2.2.1a]

>

> Am I overlooking something?

>





More information about the Linux mailing list