search for: befound

Displaying 4 results from an estimated 4 matches for "befound".

2004 May 03
0
Windows XP client - intermittent 'network name cannot befound' loading profile
Hello Tim, I have verified and recreated your problem. As soon as I switch SAMBA option security=share , I have exactly the same problems like you, when trying to access a SAMBA share via Windows "Add Network Places" The only option I have to logon is DOOMIT\Guets (DOOMIT is the NetBIOS Name of my samba server). HOWEVER: There *aren't any* problems, if I try to map the share as
2004 May 11
1
[Fwd: Re: Windows XP client - intermittent 'network name cannot befound' loading profile]
Doesn't really resolve the issue, but in my case the problem went away when using physical machines rather than virtual machines. The environments are identical - RH ES 3.0 with Windows XP sp1a client (no hotfixes or GPO settings applied). Thanks for everyone's help. On Fri, 2004-05-07 at 15:38, Michael Vermaes wrote: > On Fri, 2004-05-07 at 15:16, Clint Sharp wrote: > > >
2004 May 03
2
Windows XP client - intermittent 'network name cannot be found' loading profile
I have seen a number of postings which seem similar to the problem I am having, but am yet to find a fix for my situation. Problem is as follows: - Samba 3.0.2 rpm installed on Red Hat Enterprise ES 3.0, configured as PDC with ldapsam backend - Windows XP Professional client joined to the Samba domain. The XP client successfully joins the domain and can browse and access shares (including the
2004 May 04
0
Windows XP client - intermittent 'network name cannotbefound' loading profile
...@lists.samba.org > > [mailto:samba-bounces+lists=davey.net.au@lists.samba.org]On Behalf Of > > Michael Vermaes > > Sent: Monday, 3 May 2004 2:04 PM > > To: samba@lists.samba.org > > Subject: RE: [Samba] Windows XP client - intermittent 'network name > > cannotbefound' loading profile > > > > > > Thanks for the quick reply John. I tried setting the local GPO option as > > described in the article, but the problem still occurs. The issue > > described in the article is not exactly what I am experiencing - the > > event id i...