samba - May 2005 - REPOST No 3 - Browsing Problem on Samba 3.0.14 PLEASE HELP!!!

Hello Experts,

I have a severe Problem with my current samba installations. Here in my
Home-Office networt I have a dual-CPU machine with Debian Sarge, hosting
some samba 3.0 shares and as well being a host for 4 vmware-sessions (Vmware
Workstation v4.52, with 3xServer2003 and 1xXPpro). As well I have a separate
raid5-server with samba 3.0 in the exakt same configuration (of course all
parameters except the hostname etc.).
>From all "real" machines in my network I am able to access all
samba shares
without any hassle. 

But if I try to use a samba share from one of the vmware-machines (which are
connected to the network using the "bridged network" config), I will
be able
to connect to it and to see the three upmost levels of the contained folders
and files (like \\Servername\Sharename\1stLevel\2ndLevel\3rdLevel ).

But if I then try to access the "3rdLevel"-Folder, it takes minutes
and
finally gives an error like "no access to 3rdLevel, you eventually
don't
have the right to access this ressource...bla...bla...The network name is no
longer available". This happens if I try to access the share by connecting
it to al local driveletter as well when trying to type
\\Servername\Sharename to explorer-windows - no difference in behaviour.

The funny thing is, that I can access the share on the raid5-server without
any problems from everywhere.

Does anyone 'round here experience the same problem and does anyone have a
quick solution?

Any help is greatly appreciated,

Best Regards,

Yours Sincereley

 


C.Herdeg
cs/IT solutions

Christoph Herdeg wrote:
>Hello Experts,
>
>I have a severe Problem with my current samba installations. Here in my
>Home-Office networt I have a dual-CPU machine with Debian Sarge, hosting
>some samba 3.0 shares and as well being a host for 4 vmware-sessions (Vmware
>Workstation v4.52, with 3xServer2003 and 1xXPpro). As well I have a separate
>raid5-server with samba 3.0 in the exakt same configuration (of course all
>parameters except the hostname etc.).
>
>>From all "real" machines in my network I am able to access all
samba shares
>without any hassle. 
>
>But if I try to use a samba share from one of the vmware-machines (which are
>connected to the network using the "bridged network" config), I
will be able
>to connect to it and to see the three upmost levels of the contained folders
>and files (like \\Servername\Sharename\1stLevel\2ndLevel\3rdLevel ).
>
>But if I then try to access the "3rdLevel"-Folder, it takes
minutes and
>finally gives an error like "no access to 3rdLevel, you eventually
don't
>have the right to access this ressource...bla...bla...The network name is no
>longer available". This happens if I try to access the share by
connecting
>it to al local driveletter as well when trying to type
>\\Servername\Sharename to explorer-windows - no difference in behaviour.
>
>The funny thing is, that I can access the share on the raid5-server without
>any problems from everywhere.
>
>Does anyone 'round here experience the same problem and does anyone have
a
>quick solution?
>  
>
I don't have the problem.
This about my deepest path into Samba version 3.0.15pre2-SVN-build-6319
\\gate\download\linux\daemons\ldap\padl\xad_oss_plugins-40\idmap_ad
This is on vmware 4.5.2 build 8848, bridged ethernet, vlance virtual device.
Running a 2003 Enterprise server SP1
AMD PCNET Family PCI Eth
linux 2.4.20-28.9smp, basically RH9, kerberos & gcc are homebrew.

Three folders down sounds pretty bizarre.  Maybe you're using the vmxnet 
virtual device?  I had some issues with that if my memory serves me 
correctly.
Regards, Doug

Hi John,

Many thanks for your answers. I've read many Howtos and FAQs and Tutorials
and books about implementing Samba in different infrastructures. In the most
relevant points my configuration use "best practice"-solutions.

According to the topic of WINS-support I must tell you that WINS is simply
not the way of solving problems in a proper and productive
Microsoft-/Linux-environment; I'd rather describe it as a
"quick'n'dirty"-way to solve beginner-troubles.

Yes: all the protocol stacks work perfectly although none of the machines
points to any WINS-server. We did / do not have any WINS-server within our
infrastructure and that's also the way it will be in the future. Yes: the
accessed files and folders are on 777 for testing purposes. Debugging? None.
Due to the fact that I'm originally coming from the windows-side of the
world, debugging is mostly unknown to me ;). If there is no entry in the
event-log after an error happened, I'm lost :(  What ways of debugging were
there?

And, above all that: our Samba- and VMware-solutions worked for over 1,5
years (of course with different releases of Samba) and it worked absoluteley
neat allover the time. The error exists for about two weeks and was never
seen before. So it definiteley has nothing to do with name resolution.

Regards,



Chris

 

-----Urspr?ngliche Nachricht-----
Von: jht@Samba.Org [mailto:jht@Samba.Org] 
Gesendet: Sonntag, 8. Mai 2005 17:03
An: c.herdeg@web.de
Betreff: Re: [Samba] REPOST No 3 - Browsing Problem on Samba 3.0.14 PLEASE
HELP!!!

On Sunday 08 May 2005 08:23, Christoph Herdeg wrote:
> Hello Experts,
>
> I have a severe Problem with my current samba installations. Here in 
> my Home-Office networt I have a dual-CPU machine with Debian Sarge, 
> hosting some samba 3.0 shares and as well being a host for 4 
> vmware-sessions (Vmware Workstation v4.52, with 3xServer2003 and 
> 1xXPpro). As well I have a separate raid5-server with samba 3.0 in the 
> exakt same configuration (of course all parameters except the hostname
etc.).
>
> >From all "real" machines in my network I am able to access
all samba
> >shares
>
> without any hassle.
>
> But if I try to use a samba share from one of the vmware-machines 
> (which are connected to the network using the "bridged network" 
> config), I will be able to connect to it and to see the three upmost 
> levels of the contained folders and files (like 
> \\Servername\Sharename\1stLevel\2ndLevel\3rdLevel
> ).
>
> But if I then try to access the "3rdLevel"-Folder, it takes
minutes
> and finally gives an error like "no access to 3rdLevel, you eventually
> don't have the right to access this ressource...bla...bla...The 
> network name is
Have you checked the permissions on the folders to which access is being
denied?

What debugging have you done? Have you followed the guidelines in the
Samba-HOWTO-Collection? This document can be obtained from:

http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
> no longer available". This happens if I try to access the share by
The message "Network name is no longer available" may originate from a
problem with NetBIOS name resolution. Are you using a WINS server? Have you
read the chapter on network browsing in the Samba-HOWTO-Collection?

Do you have consistent protocol stacks on all machines? Are they all
pointing at your WINS server?

- John T.
> connecting it to al local driveletter as well when trying to type 
> \\Servername\Sharename to explorer-windows - no difference in behaviour.
>
> The funny thing is, that I can access the share on the raid5-server 
> without any problems from everywhere.
>
> Does anyone 'round here experience the same problem and does anyone 
> have a quick solution?
>
> Any help is greatly appreciated,
>
> Best Regards,
>
> Yours Sincereley
>
>
>
>
> C.Herdeg
> cs/IT solutions
--
John H Terpstra
Samba-Team Member
Phone: +1 (650) 580-8668

Author:
The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556
Samba-3 by Example, ISBN: 0131472216
Hardening Linux, ISBN: 0072254971
Other books in production.