Maximum PC

Yet for some reason when I try to access the share from Windows, I can't connect to it.

The network path \\canvasback\fah coiuld not be found

Help me.

Do you see the share under Network Neighborhood? Check the permissions over again, as well as the user/owner of the folder. Make sure that the user and owner of the folder is the user that's trying to access the share itself. That could be the problem.

I see the system in Network Neighborhood, but not the share itself.

When I click on the system, I get

"\\Canvasback is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The network path was not found."

My initial thought is pcguest does not have appropriate permisions applied throughout the entire share.

I beleive all you need to do is apply the right perms with chmod and it has to be applied to that directory and every directory under it.

1. As furball said, check perms on /fah
2. If you haven't already, add pcguest to your samba users (smbpasswd -a -n pcguest) -- though I would expect to see bad username/password if this was the problem
3. Try the "guest only" option (although you do have guest ok, which should be sufficient, and is the same as my "public" option)
4. Check samba log (mine is /var/log/samba/log.smbd and log.nmbd) after attempting to visit share, see if it has any info

My incoming share has the following options:



Some of those are redundant, but you get the picture.

My /usr/local/share/samba/in directory is world writable.

/fah is set to 777

I tried adding some redundent flags in my smb.conf

Still no workie



The only thing in my log is:


I have added a hosts file on my other workstation so it can find canvasback and I can ping by name to the machine.

Just because I've been burned by this before...Did you do that via a chmod or chmod -R

The first just sets the folder only. The later will set everything in /fah including the folder itself.

Excellent question. I'm pretty sure it's 777 all the way down.

I'm starting to think it's a network issue, since the log file isn't even showing anything

Would it help if I used

Security = share

???

I dunno.

Doesn't that point to groups that are setup on there??

We have one box at work that serves as a gateway between networks. People on a private LAN can see the share from \\Samba02, when all the files are on \\Samba01. Samba02 sees the share on Samba01 as an NFS share, and shares it to Windows.

When you create files from the private network, the file is created by "nobody".

Anyhow, I remembered that I had turned on the firewall when I installed. I turned it off, and it sorta works.

Now I can browse the share , I just can't map a drive to it.

I think HK47 mentioned in chat that this is working now.

Yeah, it didn't work at 4pm, and it did at 8pm. :wtf: