Kris Kelley
2002-May-13 16:52 UTC
[Samba] Can't access a linux server using a Win2K client
Hello all. I am new to Samba, so forgive me if this is a stupid question, but I have been unable to figure this out. I have a Red Hat 7.1 box (kernel 2.4.9) with the Samba 2.2.4-2 RPM installed. I am trying to configure it so that Windows 2000 machines within my company's Windows domain can access it. Before diving into anything exotic, I am trying to get this to work without requiring any kind of authentication. So, this is my smb.conf file: [global] workgroup = DEVGROUP security = share netbios name = skunkworx [test] comment = test share path = /export/samba/test read only = no guest only = yes guest account = nobody The relevant directory, /export/samba/test, does exist, and has 777 permissions. When Samba is running, SKUNKWORX shows up in a listing of the Windows domain, but all attempts to access the share have failed with the error message "\\Skunkworx is not accessible. The account is not authorized to log in from this station." An Internet search led me to believe this problem usually happens because Win2K machines use encrypted passwords by default, which a Samba set-up like mine would not support. However, because I am trying to bypass the use of passwords altogether (for now), I do not believe this is my problem. Still, I went ahead and tried the suggested registry hack, enabling Win2K to use plain-text passwords. No dice. I can supply the dump from testparm, and I can also supply the logs from smbd when I tried this with debug level 3, if any of that will help. Any assistance will be greatly appreciated. If this question has been answered before, feel free to direct me to the appropriate archives (I didn't see any search options available). Thank you. ---Kris Kelley
I'm running into the same thing - but I'm going thru the File Explorer and trying to Map a drive manually. It started when I went up to 2.2.4. :/ Jim Hale --- Jim & Kathy's Website Collection http://hale.dyndns.org> -----Original Message----- > From: samba-admin@lists.samba.org > [mailto:samba-admin@lists.samba.org] On Behalf Of Kris Kelley > Sent: Monday, May 13, 2002 6:48 PM > To: samba@lists.samba.org > Subject: [Samba] Can't access a linux server using a Win2K client > > > Hello all. I am new to Samba, so forgive me if this is a > stupid question, but I have been unable to figure this out. > > I have a Red Hat 7.1 box (kernel 2.4.9) with the Samba > 2.2.4-2 RPM installed. I am trying to configure it so that > Windows 2000 machines within my company's Windows domain can > access it. Before diving into anything exotic, I am trying > to get this to work without requiring any kind of > authentication. So, this is my smb.conf file: > > [global] > workgroup = DEVGROUP > security = share > netbios name = skunkworx > [test] > comment = test share > path = /export/samba/test > read only = no > guest only = yes > guest account = nobody > > The relevant directory, /export/samba/test, does exist, and > has 777 permissions. > > When Samba is running, SKUNKWORX shows up in a listing of the > Windows domain, but all attempts to access the share have > failed with the error message "\\Skunkworx is not accessible. > The account is not authorized to log in from this station." > An Internet search led me to believe this problem usually > happens because Win2K machines use encrypted passwords by > default, which a Samba set-up like mine would not support. > However, because I am trying to bypass the use of passwords > altogether (for now), I do not believe this is my problem. > Still, I went ahead and tried the suggested registry hack, > enabling Win2K to use plain-text passwords. No dice. > > I can supply the dump from testparm, and I can also supply > the logs from smbd when I tried this with debug level 3, if > any of that will help. > Any assistance will be greatly appreciated. If this question > has been answered before, feel free to direct me to the > appropriate archives (I didn't see any search options > available). Thank you. > > ---Kris Kelley > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Well, I kind of solved the problem. I noticed that when I installed 2.2.4 (RPM) it made a backup of my smb.conf (called smb.conf.rpmsave) - I deleted the smb.conf, renamed the .rpmsave and Voila! I got my drive access back. :) Jim Hale --- Jim & Kathy's Website Collection http://hale.dyndns.org> -----Original Message----- > From: samba-admin@lists.samba.org > [mailto:samba-admin@lists.samba.org] On Behalf Of Jim Hale > Sent: Monday, May 13, 2002 7:59 PM > To: 'Kris Kelley' > Cc: Mailing List - Samba > Subject: RE: [Samba] Can't access a linux server using a Win2K client > > > I'm running into the same thing - but I'm going thru the File > Explorer and trying to Map a drive manually. It started when > I went up to 2.2.4. :/ > > Jim Hale > --- > Jim & Kathy's Website Collection > http://hale.dyndns.org > > > -----Original Message----- > > From: samba-admin@lists.samba.org > > [mailto:samba-admin@lists.samba.org] On Behalf Of Kris Kelley > > Sent: Monday, May 13, 2002 6:48 PM > > To: samba@lists.samba.org > > Subject: [Samba] Can't access a linux server using a Win2K client > > > > > > Hello all. I am new to Samba, so forgive me if this is a > > stupid question, but I have been unable to figure this out. > > > > I have a Red Hat 7.1 box (kernel 2.4.9) with the Samba > > 2.2.4-2 RPM installed. I am trying to configure it so that > > Windows 2000 machines within my company's Windows domain can > > access it. Before diving into anything exotic, I am trying > > to get this to work without requiring any kind of > > authentication. So, this is my smb.conf file: > > > > [global] > > workgroup = DEVGROUP > > security = share > > netbios name = skunkworx > > [test] > > comment = test share > > path = /export/samba/test > > read only = no > > guest only = yes > > guest account = nobody > > > > The relevant directory, /export/samba/test, does exist, and > > has 777 permissions. > > > > When Samba is running, SKUNKWORX shows up in a listing of the > > Windows domain, but all attempts to access the share have > > failed with the error message "\\Skunkworx is not accessible. > > The account is not authorized to log in from this station." > > An Internet search led me to believe this problem usually > > happens because Win2K machines use encrypted passwords by > > default, which a Samba set-up like mine would not support. > > However, because I am trying to bypass the use of passwords > > altogether (for now), I do not believe this is my problem. > > Still, I went ahead and tried the suggested registry hack, > > enabling Win2K to use plain-text passwords. No dice. > > > > I can supply the dump from testparm, and I can also supply > > the logs from smbd when I tried this with debug level 3, if > > any of that will help. > > Any assistance will be greatly appreciated. If this question > > has been answered before, feel free to direct me to the > > appropriate archives (I didn't see any search options > > available). Thank you. > > > > ---Kris Kelley > > > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Brad Langhorst
2002-May-13 19:34 UTC
[Samba] Can't access a linux server using a Win2K client
Kris Kelley wrote:>Hello all. I am new to Samba, so forgive me if this is a stupid >question, but I have been unable to figure this out. > >I have a Red Hat 7.1 box (kernel 2.4.9) with the Samba 2.2.4-2 RPM >installed. I am trying to configure it so that Windows 2000 machines >within my company's Windows domain can access it. Before diving into >anything exotic, I am trying to get this to work without requiring any >kind of authentication. So, this is my smb.conf file: > > [global] > workgroup = DEVGROUP > security = share > netbios name = skunkworx > [test] > comment = test share > path = /export/samba/test > read only = no > guest only = yes > guest account = nobody > >i wish i could give you some clearer help but i've not done this myself i suggest you take a look in the log files after adding log level = 2 to your global section /var/log/samba/log.smbd another thing to try is to up your sambabox in a different workgroup (ie devgroup2) if you don't know what to make of the results of your log file post them here. brad