Windows - Linux Network - problems accessing files

[gilap]

Hello
my second problem...
I have with the aid of a very good how-to been able to set up a Linux-Windows Network.
I can see the Windows folder (Shared Docs) in Suse and from the Windows machine I can see the Samba server. When I dbl-click from the Linux machine on SharedDocs, I'm being told the folder does not exist.
And if I try to access the samba server from the Windows machine I need a password. But neither the root or my user login work.
What do I do?
Please make your answers foolproof, as I'm still a noob with Linux and I definately have no idea about setting up networks.
Thanks
g

[swerdna]

Hi

First turn off the Suse firewall and any third-party firewall on the windows machine until you get this sorted. Makes the problem less complicated.

I can see the Windows folder (Shared Docs) in Suse and from the Windows machine I can see the Samba server. When I dbl-click from the Linux machine on SharedDocs, I'm being told the folder does not exist.

Check the workgroup name in windows and Suse are the same. In Suse the workgroup name is in the file /etc/samba/smb.conf and you can look into that with your file browser. When they are the same, if the problem persists then post here the contents of the file smb.conf at /etc/samba/smb.conf.

And if I try to access the samba server from the Windows machine I need a password. But neither the root or my user login work.
What do I do?

You must add a user to the Samba user database, suppose your username is "billy". Open a console and type this and then follow the bouncing ball:

sudo smbpasswd -a billy

Then supply those credentials from windows.

[gilap]

adding the user to the samba database worked. Windows can now access my files. I turned off the Windows firewall but still get the message, that the folder (shareddocs on Windows) does not exist.
Am I missing something?

swerdna:it was your excellent howto that I followed for setting up the LAN - Thank you very much

[swerdna]

swerdna:it was your excellent howto that I followed for setting up the LAN - Thank you very much

Thanks for the compliment

adding the user to the samba database worked. Windows can now access my files. I turned off the Windows firewall but still get the message, that the folder (shareddocs on Windows) does not exist.
Am I missing something?

Turn off the Suse firewall too for the time being (but I don't think firewalls are the problem here; I just say that to make sure we get less confusion).

Check that SharedDocs sharing settings in windows (if it's xp) is set to "allow network users to alter my files" or like that (can't remember), but I don't think that's the problem. BTW is that the folder "Shared Documents"?

Hmmm... Maybe it's a vista thing? are you using vista and if so: what version of Suse are you using plus what are the vista sharing settings?

[gilap]

I'm using Windows XP & Suse 10.3 64bit.
The folder properties on SharedDocs (yes, Shared Documents - but I think I renamed it ages ago) are set to "allow network users to alter my files". And I did this to the folders inside SharedDocs, but still nothing.

[swerdna]

I'm using Windows XP & Suse 10.3 64bit.
The folder properties on SharedDocs (yes, Shared Documents - but I think I renamed it ages ago) are set to "allow network users to alter my files". And I did this to the folders inside SharedDocs, but still nothing.

2 thoughts:
1: Can you please post the contents of smb.conf located at /etc/samba/smb.conf.

2: And just confirm that you checked the workgroup names are the same for xp and Suse?

[gilap]

Yes, the workgroup names are both the same (MSHOME).
Here's the config:

# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
# Date: 2008-05-28
[global]
workgroup = MSHOME
netbios name = cellar
name resolve order = bcast host lmhosts wins
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700

[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

Thanks for the help.

[swerdna]

I can't see any clear reason why that doesn't work.

Try this: make a new folder in windows, e.g. just nmake "share" as a folder on the desktop. R-click and share it. Then see after a reboot of windows whether you can get to that share over the network from Suse.

That's just to see whether there's anything special or corrupt or whatever about the "Shared Docs" folder, or whether your problem is general to all shared folders on XP.

[gilap]

No success - I'm still being told that the folder does not exist. It is possible though, to copy files from Suse to XP from XP.

[Robbace]

My god. I was pulling my hair out trying to figure out why my Vista machine couldnt log on to my Samba server. Thanks for the post.