[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Samba not accessible with 3.0.8



I'm running a "testing" system.  I previously had a working Samba 3.0.7.
The only differences between my /etc/samba/smb.conf and the version in
/usr/share/samba/smb.conf are the name of the workgroup, encrypt passwords
= true, and I selected the lines for lprng-based printing.

A few days ago, I did an apt-get dist-upgrade; I'm now running samba
3.0.8-2.  I can no longer connect from either Win98 SE or from Win XP
systems.  I can't even browse my server.  I get the message
    \\myserver is not accessible

>From another Linux system, I can connect with smbclient, but I can't
browse with LinNeighborhood.

Looking in /var/log/samba at the log files, it looks as if nmbd is seeing
the browser queries, but discarding them.

Has anyone run into anything like this?  In particular, I see things like

 find_workgroup_on_subnet: workgroup search for PHYSICS on subnet xxx.xxx.xxx.2 1: found.
[2004/12/03 10:41:09, 5] libsmb/nmblib.c:read_packet(757)
  Received a packet of len 201 from (xxx.xxx.xxx.64) port 138
[2004/12/03 10:41:09, 9] nmbd/nmbd_namelistdb.c:find_name_on_subnet(129)
  find_name_on_subnet: on subnet xxx.xxx.xxx.21 - name PHYSICS<1d> NOT FOUND
[2004/12/03 10:41:09, 5] nmbd/nmbd_packets.c:process_dgram(1194)
  process_dgram: ignoring dgram packet sent to name PHYSICS<1d> from xxx.xxx.xxx.64

My Samba server is xxx.xxx.xxx.21.  It is first saying it is able to
find PHYSICS, but later can't find PHYSICS<1d>.  What's that <1d>?

Is anyone else having similar problems?  It worked prior to this
upgrade, and I haven't changed anything else.

-- 
    Andy Dougherty		doughera@lafayette.edu
    Dept. of Physics
    Lafayette College, Easton PA 18042



Reply to: