Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Problems with Samba

edesignuk

edesignuk

Moderator emeritus
Original poster
Mar 25, 2002
19,232
2
London, England
In 10.2 I had no problems at all, I could get to my home folder from my PC by \\quicksilver\jelliott, I would authenticate with my OS X username and password and I'd be in.
Now in 10.3, samba is running, but I cannot authenticate with my OS X login (even tried to authenticate as root!).
Anyone got any ideas, this is a serious issue for me :(
 
Yup, I can also connect and authenticate over FTP from PC to Mac if I enable FTP on the Mac, it's just Samba that's giving me issues :(
 
I wish I could be of more help right now, but I'm waiting for my copy of Panther
from Amazon.

What does your /etc/samba/smb.conf read?

[EDIT] Whoops, my bad. I'm thinking of Linux. Hold on, I'm searching for smb.conf
on my powerbook (which is at home) from work. [/EDIT]


-jeff
 
Code: 
; Template configuration file for smbd.
; ============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.  It also provides
; a public share point for generally exporting stuff.
;
; Some things to check out:
;
; 1: Make sure that the user specified in "guest account" exists. Typically
;    this will be a user that cannot log in and has minimal privileges.
;    Often the "nobody" account doesn't work (very system dependant).
;
; 2: You should consider the "security =" option. See a full description
;    in the main documentation and the smb.conf(5) manual page
;
; 3: Look at the "hosts allow" option, unless you want everyone on the internet
;    to be able to access the shares you export here.
;
; 4: If you want to support printers, add/uncomment the relevant entries.
;
[global]
  server string = PowerMac G4
  veto files = Temporary Items/Desktop */TheFindByContentFolder/TheVolumeSettingsFolder/Network */
  hide dot files = yes
  client code page = 437
  coding system = utf8
  guest account = unknown
  encrypt passwords = yes
  printing = cups
  map to guest = Bad User
  
[homes]
   comment = User Home Directories
   browseable = no
   read only = no
   create mode = 0750
  
[music]
   comment = iTunes files
   path = /Users/jelliott/Music/iTunes/iTunes Music
   browseable = yes
   read only = no
   create mode = 0750

;[public]
;   path = /tmp
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

;[printers]
;  path = /var/spool/samba
;  comment = All Printers
;  guest ok = yes
;  writeable = no
;  printable = yes 
;  browseable = no
I added in the music share info from a guide on macosxhints, but it wasn't doing this that stopped it working or anything, I couldn't get it to work before touching it.
Could someone else with Panther please post the contents of their smb.conf (/etc/smb.conf)? Thanks!
 
No, should I, I never had to in 10.2. What does it do? Thanks.

edit: BTW, if this is to do with DNS and name resolution, I have a Win2000 Svr that runs my own local DNS, so if I nslookup the hostnames of any of my machines they get resolved to a LAN IP.
 
Anywhere in the [homes] section.


My last thought for you if none of this works is to add another user
and try authenticating with his username and password. That way you would
know if something is screwy for your user.

Don't know about OS X, but sometimes root isn't allowed for Samba usage.



-jeff
 
Look's like Apple changed the password authentication, along with relocating stuff in Panther. So there are password problems, along with broken links.
Originally posted by sbromlin:
Originally posted by sbromlin:
Under Jaguar I used to run UW-IMAP (using SSL) as a mail with no difficulties. Under Panther, I can get the imap daemon responding to requests, but no matter what I try, it responds to "LOGIN user passwd" with "NO Login Failed". It seems that something has changed with authentication in Panther, but I've yet to figure out what.
I've tried compiling imapd with Kerberos authentication, in addition to plaintext through ssl.
Any ideas?
Click to expand...

I've discovered why. In `man getpwent` it
describes than Panther has changed the
authentication behaviours, and all password
checks now need to go through the DirectoryServices API. This will mean a not insignificant amount of work to get UW-IMAP working in Panther (I've hacked it to work locally)
Click to expand...
 
Originally posted by Sun Baked
Look's like Apple changed the password authentication, along with relocating stuff in Panther. So there are password problems, along with broken links.
Click to expand...
So does this just mean I am totally stuffed until Apple fix it?
 
Originally posted by edesignuk
So does this just mean I am totally stuffed until Apple fix it?
Click to expand...
Probably, glanced at the Apple Discussion site and it doesn't sound like a login problem. A lot more like a bug (or several).

The login authentication seems like one many problems, or they work for some occasionally.
 
Originally posted by Sun Baked
Probably, glanced at the Apple Discussion site and it doesn't sound like a login problem. A lot more like a bug (or several).

The login authentication seems like one many problems, or they work for some occasionally.
Click to expand...
Perfect! :mad: I don't believe this! I use Samba to access my Mac constantly, this is gonna cause me know end of problems. Nice one Apple.
 
Could someone please post the contents of their smb.conf file? (/etc/smb.conf) Like the clever lad I am, I've been playing about with it trying to get the damn thing to work, and didn't make a backup of the origional :rolleyes:

Thanks!

P.S. Pls post using the
Code: 
 tags, thx :)
 
I'm not quite sure what the
Code: 
 tags are, but here is the entire code:

; Template configuration file for smbd.
; ============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and 
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.  It also provides
; a public share point for generally exporting stuff.
;
; Some things to check out:
;
; 1: Make sure that the user specified in "guest account" exists. Typically
;    this will be a user that cannot log in and has minimal privileges.
;    Often the "nobody" account doesn't work (very system dependant).
;
; 2: You should consider the "security =" option. See a full description
;    in the main documentation and the smb.conf(5) manual page
;
; 3: Look at the "hosts allow" option, unless you want everyone on the internet
;    to be able to access the shares you export here.
;
; 4: If you want to support printers, add/uncomment the relevant entries.
;
[global]
  guest account = unknown
  encrypt passwords = yes
  auth methods = guest opendirectory
  passdb backend = opendirectorysam guest
  printer admin = @admin, @staff
  server string = Mac OS X
  unix charset = UTF-8-MAC
  display charset = UTF-8-MAC
  dos charset = 437
  use spnego = no
  client ntlmv2 auth = no

  workgroup = NIFTY
[homes]
   comment = User Home Directories
   browseable = no
   read only = no

;[public]
;   path = /tmp
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

[printers]
  path = /tmp
  printable = yes

That's it.  The only thing that would be different is the workgroup.

I'm having a hell of a time with Samba too.  I windows user can see my folders fine, but I can't connect to myself, not even if I make a 2nd user and use their login info.  A lot of people who use Samba shares are having problems... :(
 
I'm having similar issues. I used to be able to access my Windows machine from the my Mac and vica versa with no problems at all with 10.2. With 10.3 I have so far only managed to access the Mac from the Windows machine and the speed is slow - particularly to establish the connection or open a folder. If I try to access the Windows machine from the Mac I have to use the IP address (machines are not being discovered as they used to ), I am then asked for a username and password which I enter, then it tells me that I cant login as the machine was not found :mad: . At this time the icon of the Windows machine disappears but not the name, and another Icon comes up next to it.

I guess this sounds confusing but the upshot is I can only connect Windows to Mac so much more time on the Windows machine at the Moment :(
 
Originally posted by moko
I'm having similar issues. I used to be able to access my Windows machine from the my Mac and vica versa with no problems at all with 10.2. With 10.3 I have so far only managed to access the Mac from the Windows machine and the speed is slow - particularly to establish the connection or open a folder. If I try to access the Windows machine from the Mac I have to use the IP address (machines are not being discovered as they used to ), I am then asked for a username and password which I enter, then it tells me that I cant login as the machine was not found :mad: . At this time the icon of the Windows machine disappears but not the name, and another Icon comes up next to it.

I guess this sounds confusing but the upshot is I can only connect Windows to Mac so much more time on the Windows machine at the Moment :(
Click to expand...

I hear ya... It was showing other workgroup computers for awhile, but it just stopped. Mac networking has a long way to go... :(
 
Panther smb.conf

This is the unmodified default Panther smb.conf file located in /etc

; Template configuration file for smbd.
; ============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap. It also provides
; a public share point for generally exporting stuff.
;
; Some things to check out:
;
; 1: Make sure that the user specified in "guest account" exists. Typically
; this will be a user that cannot log in and has minimal privileges.
; Often the "nobody" account doesn't work (very system dependant).
;
; 2: You should consider the "security =" option. See a full description
; in the main documentation and the smb.conf(5) manual page
;
; 3: Look at the "hosts allow" option, unless you want everyone on the internet
; to be able to access the shares you export here.
;
; 4: If you want to support printers, add/uncomment the relevant entries.
;
[global]
guest account = unknown
encrypt passwords = yes
dos charset = 437
unix charset = UTF-8-MAC
auth methods = guest opendirectory
passdb backend = opendirectorysam guest
printer admin = @admin, @staff
server string = Mac OS X

[homes]
comment = User Home Directories
browseable = no
read only = no
create mode = 0750

;[public]
; path = /tmp
; public = yes
; only guest = yes
; writable = yes
; printable = no

[printers]
comment = All Printers
browseable = no
printable = yes
public = no
writable = no
create mode = 0700
path = /tmp
 
Solving all G5 Panther SAMBA problems...

Ok, maybe it doesn't solve all of them, but using Webmin, I've been able to get some control of sharing between an XP machine and my G5 with 10.3. (I have two G4s with 10.2.6 and 10.2.8 that have not been a problem.)

To make it work, install Webmin. Then setup the SAMBA server with these settings:
/etc/smb.conf
/usr/bin/smbpasswd
/usr/bin/smbstatus
/usr/bin/smbpasswd
/usr/sbin/smbd
/usr/sbin/nmbd
/usr/sbin/swat
smbgroupedit = none
/usr/bin/pdbedit
/usr/bin/net

Afterwards, I setup some shares, ran "Convert Unix users to SAMBA users", reloaded the server, and two shares worked. Some features remain elusive such as automatic user mapping, group control, and exactly how 10.3 implements samba shares.
 
Guest account setup

Running Panther on a g3 500 on a t1 LAN. Has anyone attempted to set up windows style read only shares and gotten it to work? I would like to set my computer up as a limited read only server for others to access. Is there a way of doing this without them logging in?
 
I'm guessing the issue here may not be OS X, since I've had some odd problems with Fedora Core 2 (Linux) as well. Panther uses Samba 3 (like Fedora does), while I believe Jaguar used Samba 2.x. Some things about Samba look to have changed a fair bit.

Feel free to correct me if I'm wrong...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back