You are not logged in.

#1 2007-04-18 13:09:29

ilovefridge
Member
Registered: 2007-04-18
Posts: 22

(probably quite simple?) Samba troubles

I've set up a few shared folders using samba, and I can see them both in Arch and over the network in XP. Although when I try to open any of them, in either OS, it says they aren't accessible. Here is the the log of my XP machine trying to connect:

[2007/04/18 13:49:15, 0] param/loadparm.c:lp_do_parameter(3438)
  Global parameter guest account found in service section!
[2007/04/18 13:49:15, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2007/04/18 13:49:15, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2007/04/18 13:49:16, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2007/04/18 13:49:16, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2007/04/18 13:54:53, 1] smbd/ipc.c:api_fd_reply(290)
  api_fd_reply: INVALID PIPE HANDLE: 72e3
[2007/04/18 13:58:04, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2007/04/18 13:58:04, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused

As you can see it goes on about CUPS server. I don't have a printer installed on my Arch machine, and although i have one on my XP machine, it isn't shared. I put the 'printing = cups' line in anyway in the smb.conf but it hasn't made any difference. Here is my smb.conf file as it stands at the moment:

[global]
workgroup = MSHOME
security = share
restrict anonymous = no
log file = /home/steve/.sambalog.log .%m
max log size = 50
server string = MrServer
unix extensions = no
printing = cups

[Downloading]
comment = Downloading
path = /home/steve/Downloading
force user = steve
read only = no
guest ok = yes
case sensitive = no
strict locking = no
msdfs proxy = no

[Completed_Downloads]
comment = Completed_Downloads
path = /home/steve/Completed_Downloads
force user = steve
read only = no
guest ok = yes
case sensitive = no
strict locking = no
msdfs proxy = no
guest account = steve

[Music]
comment = Music
path = /home/steve/Music
force user = steve
read only = no
guest ok = yes
case sensitive = no
strict locking = no
msdfs proxy = no

[DVDs]
comment = DVDs
path = /home/steve/DVDs
force user = steve
read only = no
guest ok = yes
case sensitive = no
strict locking = no
msdfs proxy = no

If anyone could guide me in the right direction that would be great! It's been troubling me for a while now! Thanks very much,

Steve

Offline

#2 2007-04-19 10:15:10

Captain Spaulding
Member
Registered: 2006-11-16
Posts: 115
Website

Re: (probably quite simple?) Samba troubles

Just like the error message says, you shouldn't put a global parameter in a service, ie. share, section. Move the entry guest account = steve into the global section and the error should disappear. You also might want to run testparm to further check your Samba config.

Offline

#3 2007-04-19 11:20:04

ilovefridge
Member
Registered: 2007-04-18
Posts: 22

Re: (probably quite simple?) Samba troubles

agh, I'm an idiot for not seeing that line! I just got caught up in CUPs stuff. Thanks very much anyway! I'm sure it'll work now! thanks again!

Offline

Board footer

Powered by FluxBB