Cannot view shared files using samba on peer to peer with XP Pro

[wrates]

Hi all,

Am currently having problems with our network setup which is all Windows machines but I have just added another machine running Suse 10.2.

There are 8 machines in total on the network, 7 on XP Pro and 1 on Suse all running via a peer-to-peer network rather than a domain. Each computer has a static IP address (we need to use static ones). All we need running is simple folder sharing across the network.

The problem is on the Linux sharing, the network card is configured correctly and all machines will ping each other and the linux machine has no problem accessing the shared folders on the xp machines. When viewing the network from the Windows machines, the Linux machine shows up along with the shared folders, yet it always asked for a login and password before I can access the folders - even though I have the security set to "share" rather than "user" - as I do not need any kind of authorisation to access the folders for my uses.

Any ideas?

Thanks

[swerdna]

Well, Ii you've got share level security, you need to reduce the permissions on the shared forlder in linux to match that. Typically a folder belonging to user "billy" has permissions drwxr-xr-x whereas "share level", a hangover from win95/98 days, implies drwxrwxrwx. So try that. Then there's the possibility of needing to allow guest access in the Samba configuration file (if you use KDE). Assuming that you have a share (made otherwise than by the sharing facility in Nautilus), it will have a definition in the Samba configuration file like this:

[Sharename]
path = /path_to/shared_folder/
guest ok = yes
read only = no

You can check and edit the share definition with this command in a terminal/shell/console:

kdesu kwrite /etc/samba/smb.conf

And just to be on the safe side, turn the firewall off in Suse until you get this working, saves wondering whether the firewall is interfering.

Swerdna

[lightsycle]

I just turned off the firewall. Made sure that Samba was installed and configured, and disabled the linux firewall.

[Bugrem]

Hi

The default Samba guest user is nobody. If you set a reasonable password for nobody, then use nobody/password from the XP machines, you should gain access. Worked for me.......

HTH

B.

[rmckim]

Hi all,

Am currently having problems with our network setup which is all Windows machines but I have just added another machine running Suse 10.2.

There are 8 machines in total on the network, 7 on XP Pro and 1 on Suse all running via a peer-to-peer network rather than a domain. Each computer has a static IP address (we need to use static ones). All we need running is simple folder sharing across the network.

The problem is on the Linux sharing, the network card is configured correctly and all machines will ping each other and the linux machine has no problem accessing the shared folders on the xp machines. When iewing the network from the Windows machines, the Linux machine shows up along with the shared folders, yet it always asked for a login and password before I can access the folders - even though I have the security set to "share" rather than "user" - as I do not need any kind of authorisation to access the folders for my uses.

Any ideas?

Thanks

I'm fairly certain from what I've read that the differences in encryption are the source of the prob. Linux doesn't encrypt and Windows does - so they can't arrange to communicate in the first place - something like that.

The registry CAN be tweaked to send unencrypted name/passwords, apparently, but long term it reverts back to a stable, encrypted state, so tweaking doesn't seem to solve the communication prob with finality.

I've resigned myself to one way communication: Suse 10.3 ---> MSHOME nodes only for file transfer and sharing. It works OK I guess.... inconvenient tho.

I have been singularly unable to find out how to remedy the prob so far.

If you ever discover the true answer to this dilemma I hope you post it.

Thanks in advance.

[swerdna]

I've resigned myself to one way communication: Suse 10.3 ---> MSHOME nodes only for file transfer and sharing. It works OK I guess.... inconvenient tho.

I have been singularly unable to find out how to remedy the prob so far.

If you ever discover the true answer to this dilemma I hope you post it.

Thanks in advance.

I've solved it with utter finality.
Make the share like I said above (unless you use Nautilus R-click to make a share).
Make your [global] in the file /etc/samba/smb.conf like this:

[global]
workgroup = what you use is common for all hosts
netbios name = whatever you have for your hostname, different for all hosts
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:
# 3 lines for on-the-fly usershares made in Nautilus
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
# 4 lines to enhance network browsing - but only one LMB per workgroup
domain master = No
local master = Yes
preferred master = Yes
os level = 65

then restart with this in a terminal as root: rcnmb restart and rcsmb restart


Swerdna