[Bug 840474] Re: Can't connect via samba from Vbox XP Guest when restricting IP with hosts allow in smb.conf

[Launchpad Bug Tracker]

[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

** Changed in: samba (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/840474

Title:
  Can't connect via samba from Vbox XP Guest when restricting IP with
  hosts allow in smb.conf

Status in “samba” package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:	Ubuntu 10.04.3 LTS
  Release:	10.04

  apt-cache policy samba
  samba:
    Installed: 2:3.4.7~dfsg-1ubuntu3.7
    Candidate: 2:3.4.7~dfsg-1ubuntu3.7
    Version table:
   *** 2:3.4.7~dfsg-1ubuntu3.7 0
          500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          500 http://archive.ubuntu.com/ubuntu/ lucid-security/main Packages
          100 /var/lib/dpkg/status
       2:3.4.7~dfsg-1ubuntu3 0
          500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages

  
  I'm assuming this is a bug, as it worked before.

  I have a WinXP VirtualBox guest that I like to share folders with via
  samba (please don't suggest using the VBox shares option as a
  workaround).  In the past, I was able to restrict access to just the
  XP Guest via

  hosts allow = 192.168.56.0/255.255.255.0

  in the smb.conf file, as the vboxnet0 interface is on that IP range
  (it's 192.168.1.101).  "bind interfaces only = true" is commented out,
  as are all "interfaces" lines.  At some point (I'm not sure when, as I
  don't use the XP Guest that frequently) this stopped working.  If I
  comment out the hosts allow line such that access is available for
  everyone, then the XP Guest can connect.

  I have the same problem if I comment out "hosts allow" and have

  bind interfaces only = true
  interfaces = lo vboxnet0

  The first setup listed has worked previously, so I'm filing it as a
  bug.  Again, by simply changing the smb.conf by commenting out the
  "hosts allow" line and restarting samba, I have access to the shares
  (so the shares are being put up properly), and I'm asked for my samba
  username and password when accessing from the guest, so I think that
  end of it is behaving properly.  There seems to be something wrong
  with how it's set up to filter on IP or interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: samba 2:3.4.7~dfsg-1ubuntu3.7
  ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-generic i686
  Architecture: i386
  Date: Sat Sep  3 12:45:34 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SambaServerRegression: Yes
  SourcePackage: samba
  UbuntuFailedConnect: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/840474/+subscriptions