Hi folks,

As an experienced win user who's finally ditched the poxy thing in favour of a much better Linux OS... I need the help of some smart people here to fill in the gaps in my knowledge - quite a few of them I'm afraid.

Can anyone get me started by answering this question :

After setting up my network consisting of 3 remaining XP pcs with Suse 9.2 on the fourth, and successfully browsing to the 'archive' drive I want to access... why does Suse tell me that it cannot access file either with a message that the smb protocol died unexpectedly or simply saying "unable to access remote fileS"

Is this some kind of conflict of access rights?

HELP :-D

Eliot.

hi eliwood, welcome to lq. what step have you taken to setup the samba server on the suse machine, have you added the proper users, do those users have rights from the windows side? sorry for so many ?'s, but, the problem your having is pretty general. the first thing we need to do is pinpoint the problem a little deeper, then we can solve it.
good luck.

The permissions on the directory that you want to share with Samba could be set wrong. You can use chmod to change it to 777 on the directory. This will let everybody in for that directory. You will also have to do the same for files but keep in mind of security. Usually files are set as read for everybody. Next Samba has to be set up to browse on the shared directories to certain users or by guest (everybody). Post what you have in /etc/samba/smb.conf.

Sorry for being off of topic, but when did suse 9.2 come out? I would like to get ahold of that.

That's a typo, Suse 9.1 is the latest release -- J.W.