hi les.... thanks for the replies... i managed to get it working enough to test it... the transfer from windows to linux is working ok, although my initialproblem wasn't due to either the FTP or the Samba... in case this helps anyone else... my initial problem was an apparent slowness with transferring data from a windows box to a Linux FTP server.. everyting is on the same segment/network... i had wondered if something was going wrong with the FTP app/server.. and explored Samba as another way of checking what the issue was/is... it turns out the issue seems to have to do with the Windows configuration of the nic card ... i've wound up setting the nic to 100 full duplex and 100 transfer... this seems to have solved the issue as both the FTP and the Samba file transfer are much faster, closer to what i would have expected... -bruce -----Original Message----- From: Les Mikesell [mailto:lesmikesell@xxxxxxxxx] Sent: Monday, June 12, 2006 9:33 AM To: bedouglas@xxxxxxxxxxxxx Cc: 'For users of Fedora Core releases' Subject: RE: Samba Guru... On Mon, 2006-06-12 at 09:01 -0700, bruce wrote: > update. > > it appears that i can now see the linux "share/folder" in the windows > network. i can in fact copy a file to the linux folder on the linux box, see > the file on the windows box, and copy the file to another folder on the > windows box... > > however, when i try to copy a windows file and place it in the samba share > on the windows side, i get an "access denied" message... i never get > prompted for a user/passwd... > > thoughts/comments.. The piece you are probably missing is that samba users get mapped into some linux user and the normal linux permissions apply as well as the extra ones you specified in smb.conf. Usually the right thing do to is set security = user, log in to the windows box with the same name as the linux box, and use the default entry for the home share. In this mode, your linux home directory will only show up as a share for the windows box where you log in with the same name. If you want to share things among different windows boxes you might put them all in the same group and use the force group and create modes to make sure all the users in the group will have access. > # Security mode. Most people will want user level security. See > # security_level.txt for details. > # Use password server option only with security = server > ; password server = <NT-Server-Name> > # bdouglas.. not sure if needed... > security = SHARE This means you can connect/browse without authenticating so the home share can't work the right way (i.e. it won't know who you are before presenting the share list). > [windows] > path = /windows > writeable = yes > guest ok = yes This means you don't authenticate at all. Any connection is mapped to the guest user, which probably doesn't have write access to the files/directories. And if there are untrusted boxes on the network you don't want it to. -- Les Mikesell lesmikesell@xxxxxxxxx
