Quote:
Originally Posted by
Leppie
glad to hear it's working fine.
i think you already set up the workgroup name during the debian install, so the system did not have to prompt you again for that. also, with the vast user comunity debian packages are constantly updated and improved, so installation may be slightly different from the howtos you find on the internet.
i know the hackoramo page, but thought that the debian admin page would have been better since it covers both install and configuration
.
i think apt is superb, sometimes it cannot resolve all dependencies on its own but most of the time it's no problem. also when you get to that stage, most probably you don't need that guidance that badly anymore.
have you been able to resolve the issue with your nics?
yeah the NIC issue is resolved. I haven't proven the cause beyond all shadow of a doubt, but it seems to be an issue of not automatically connecting to the wireless network the first time around, you have to make a manual selection, after which the connection is automatic. Also the neignbor's wireless often intrudes into my space, that may be part of that issue. I hadn't noticed that at first. Also there are issues with not finding a DHCP server, that seems specific to wireless, at least during the install, I ended up doing a manual configuration with fixed ip and all is fine.
---------- Post updated 08-30-09 at 12:24 AM ---------- Previous update was 08-29-09 at 09:27 AM ----------
Quote:
Originally Posted by
Leppie
1. as far as i know you require 3 packages (samba, samba-client and samba-common, which will be installed as a dependency for both server and client package) to use the samba server for both linux and windows shares.
2. you don't have to have a linux domain, or ldap, or etc. just a workgroup name which you set in the /etc/samba/smb.conf file.
have a look at
this page for more info.
with regards to point 2, things aren't going the way i hoped. ok, here's what I have
A windows user and a linux user with the same name and password.
The unix user was created with useradd -m to create the home directory. So the user will have write access to that directory. I also used smbpasswd and created the exact same password in Samba
in my smb.conf, under [homes], I have tried read only = no and writeable = yes, both separately and together. making sure to restart smbd each time.
As the Windows user, I can map to the home directory no problem, but it appears to be read-only I can copy files from the share but not to the share. I would have though that with all that I did, I would have write access to the share.