Prev: SAMBA and Windows 2008 TSE licence Server
Next: [Samba] "unix extensions = on" is incompatible with Mac OS X Finder
From: Paul Venzke on 14 Feb 2010 22:20
On Sun February 14 2010 10:44, Robert J. Hansen wrote:
> I am trying to get Samba 3.4.0 (on an Ubuntu 9.10 box) set up as a
> file server for my home. The router is 10.1.10.1; the Ubuntu box
> ("chronicles") is 10.1.10.2; the OS X box I'm using for testing
> purposes ("job") is 10.1.10.3. From job, I can see ports 139 and
> 445 on chronicles are open. Neither box has 'chronicles' or 'job'
> listed in its /etc/hosts file.
>
> When browsing via IP address, \\10.1.10.2 can see shares on
> \\10.1.10.3 and vice-versa. Browsing by name, though, gets me
> absolutely nowhere. The Ubuntu box is able to resolve \\chronicles
> as being itself, but it can't look up \\job for love or money.
> (Additionally, discovering shares via the browser doesn't work --
> but I suspect this is related to my apparent problems with nmbd.)
>
> I have followed the checklist in chapter 38 of the Samba HOWTO
> Collection, up through step 8 where things go haywire. "Fix the
> nmbd installation" is listed as the way to overcome this, but
> unfortunately the checklist is a little sparse on precisely how to
> do this.
>
> In step 6 (run "nmblookup -d 2 '*'"), I discovered that I had to
> explicitly give it a target. By itself, executing that command on
> chronicles (10.1.10.2) did not discover job (10.1.10.3). By
> changing the command line to "nmblookup -B 10.1.10.3 -d 2 '*'", I
> was able to get a response back from job. This seems a little
> strange to me: step 6 seems to imply this should only be necessary
> if the two machines are on different subnets.
>
> My smb.conf file follows:
>
> =====
>
> [global]
> server string = %h server (Samba, Ubuntu)
> interfaces = 10.1.10.2, 127.0.0.1
> map to guest = Bad User
> obey pam restrictions = Yes
> pam password change = Yes
> passwd program = /usr/bin/passwd %u
> passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*
> . unix password sync = Yes
> syslog = 0
> log file = /var/log/samba/log.%m
> max log size = 1000
> name resolve order = wins bcast lmhosts host
> os level = 65
> preferred master = Yes
> domain master = Yes
> dns proxy = No
> wins support = Yes
> usershare allow guests = Yes
> panic action = /usr/share/samba/panic-action %d
> hosts allow = 10.1.10.0/24, 127.
> hosts deny = ALL
>
> [homes]
> comment = Home Directories
> valid users = %S
> read only = No
> create mask = 0700
> directory mask = 0700
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> create mask = 0700
> printable = Yes
> browseable = No
> browsable = No
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/printers
>
> [tmp]
> comment = testing purposes
> path = /tmp
>
>
> =====
>
>
> Thank you all for any help you can provide. I appreciate it.

Robert;

nmbd uses UDP ports 137 and 138. In addition to 139 and 445, smbd
uses the TCP port 135.
--
PV

"We have met the enemy and he is us"; Pogo
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Robert J. Hansen on 15 Feb 2010 11:00
On 2/14/10 10:05 PM, Paul Venzke wrote:
> Robert;
>
> nmbd uses UDP ports 137 and 138. In addition to 139 and 445, smbd
> uses the TCP port 135.

This seems strange, then. There is no firewall on the machine. nmap
reports UDP 137 and 138 as "open|filtered," but there is nothing
listening on TCP port 135.

iptables -L shows absolutely nothing -- no rules in effect.

Looking through the logs is not revealing very much.

At this point is this a Samba problem, or should I instead ask on the
Ubuntu lists?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: SAMBA and Windows 2008 TSE licence Server
Next: [Samba] "unix extensions = on" is incompatible with Mac OS X Finder