[Samba] Windows can't see my Samba shares...

Tue Aug 9 04:00:34 GMT 2005

I'm using hosts allow correctly.  Please read below.

>From http://us1.samba.org/samba/docs/man/smb.conf.5.html ...
hosts allow (S)
...
    You can specify the hosts by name or IP number. For example, you
could restrict access to only the hosts on a Class C subnet with
something like allow hosts = 150.203.5. .
...

That's the default location for the smbpasswd file and the one that it
was reading, according to testparm -v, but I tried specifying it as
you suggested anyway... no results.

By the way, I have and can use Ethereal.  I've tried it with a filter
like "port 137 or port 137 or port 138 or port 139 or port 445".  I
just don't know how to interpret the results.  If anyone here
understands the Ethereal output, I can post results.

Thank you,
    Vince

On 8/8/05, raulanaya at netzero.com <raulanaya at netzero.com> wrote:
> 
> Two things,
> First, your IP hosts allow = 192.168.1.??  is missing the last one or two characters.
> Second try adding this definition to the [global] section.
> "smb passwd file = /etc/samba/smbpasswd"
> Let me know if this fixes your problem.
> -Raul
> 
> 
> -- Vincente Aggrippino <vaggrippino at gmail.com> wrote:
> Ok... I'm really stumped.  I have checked thoroughly.  I've performed
> all of the steps in the checklist from the HowTo... except for the
> nmblookup parts.  The arguments to nmblookup seem to be based on an
> old version.  I'm hoping someone will have an idea.  Here's the whole
> situation...
> 
> Server:
> Fedora Core 3
> Linux myserver 2.6.11-1.35_FC3 #1 Mon Jun 13 00:52:08 EDT 2005 i686
> i686 i386 GNU/Linux
> Samba v3.0.14a latest Fedora RPM available downloaded from samba.org today
> -----
> Client:
> Microsoft Windows XP Professional, Service Pack 2
> Firewall disabled
> Workgroup name: HOME
> -----
> smb.conf:
> # Samba config file created using SWAT
> # from 127.0.0.1 (127.0.0.1)
> # Date: 2005/08/08 14:03:44
> 
> # Global parameters
> [global]
>     workgroup = HOME
>     server string = home.aggrippino.com
>     security = SHARE
>     guest account = testsmb
>     username map = /etc/samba/smbusers
>     log file = /var/log/samba/%m.log
>     hosts allow = 192.168.1.
> 
> [tmp]
>     comment = temporary files
>     path = /tmp
>     guest ok = Yes
> 
> [homes]
>     read only = No
>     guest ok = Yes
> -----
> I created a new user named testsmb on both the server and the client
> for the purpose of testing this setup.  The password is the same.
> -----
> On the client, if I try to "View Workgroup Computers", there is a long
> delay, then it tells me the following:
> 
> Home is not accessible.  You might not have permission to use this
> network resource.  Contact the administrator of this server to find
> out if you have access permissions.
> 
> The list of servers for this workgroup is not currently available.
> -----
> I have the server host resolution in the WinXP hosts file.
> 
> Ping works perfectly from the client to the server.
> -----
> I have the client host resolution in /etc/hosts.
> 
> Ping works perfectly from the server to the client.
> -----
> >From the command prompt on the client, the command "net view \\home"
> returns the following after a long delay.  I have the same result when
> I use the IP address.  I get the same result if I try to use a
> specific resource.  i.e.: "net use x: \\home\tmp" ...
> 
> System error 53 has occurred.
> 
> The network path was not found.
> ----
> On the server, I have issued the command "smbpasswd -a testsmb" and
> typed the same password as used by the Linux user ID and by the WinXP
> user ID.  I've also issued the command "smbpasswd -e testsmb".  I've
> stopped and re-started the samba daemons.  I've rebooted the client.
> -----
> I know it's not my gateway/firewall/router because because I also use
> a vmware virtual machine with WinXP Pro and some shares.  The shares
> from the virtual machine on the same physical server are normal on the
> client.  Incidentally, the virtual machine can't see the server's
> shares either.  However, vmware employs some version of samba
> internally and that works perfectly between the server and the VM.
> 
> I don't run ipchains or iptables.
> -----
> 
> I must be configuring something wrong.  vmware uses Samba for it's
> sharing and that works fine.  The network is working fine.  Otherwise
> the VMs shares wouldn't be available.
> 
> I'll be very grateful to anyone with a solution.
> 
> Thank you,
>     Vince Aggrippino
>     vaggrippino at gmail.com
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
> 
> ______________________________________________________________________
> Surfing so fast you won't believe it's not broadband!
> Try NetZero HiSpeed 3G.
> Visit http://www.netzero.com to sign up today!
> 
>