I get similar errors when I have dummy shares (ie shares in smb.conf that point to non-existent directories), check that too.
However if using as PDC, the most common situation is when the samba server is not in the DNS/WINS for given machine. If it is standalone, then make sure there is no AD server in the same workgroup: it can kick out the samba server as not trusted for the domain/workgroup. You can join it into the AD as member server to fix this, and if the AD server is also dns server, it will take care of that too. All said and done, read the docs. It seems like you are missing a part of the network planning. Carlos -----Original Message----- From: [EMAIL PROTECTED] on behalf of John Drescher Sent: Fri 8/3/2007 12:49 PM To: joop gerritse Cc: [email protected] Subject: Re: [Samba] inconsistency? On 8/3/07, joop gerritse <[EMAIL PROTECTED]> wrote: > I am less than familiar with Microsoft, so I guess it might be an FAQ... > > if I click on "network neighborhood" which reveals a Samba server, it shows a > list of all shares. If I click on a share, I get a message "cannot find share > name". Somehow this does not sound logical to me... what is wrong? > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > This is not normal with samba. Perhaps something is wrong with either your permissions on the share or your network browsing (WINS, DNS or lmhosts). John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
