08-30-2009
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.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i stumbled upon something that gave some nice instructions on how to convert FreeBSD passwords from md5 to blowfish. it was simple and straight forward and it worked.
i'm running samba on the machine.
now i know the tutorial i was following had something where a user's samba and machine... (1 Reply)
Discussion started by: xyyz
1 Replies
2. AIX
Hello
Can someone help how to install samba on aix 5.3,
I go to tha samba page and i download two files
opt-samba-base.tar.gz
opt-samba-3.0.28-AIX5.tar.gz
and I read the readme file but there is a file that miss and I dont know if I need to do this necessary
"You can now verify... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies
3. AIX
Ok I'm still trying to figure AIX out, I was used to HP-UX until they switched our server to AIX in February and all of the other servers are Linux which appears to be much more friendly. AIX is, well, NOT.
I am trying to install Samba so I can copy files onto a Windows SQL server - that's all... (5 Replies)
Discussion started by: rball
5 Replies
4. UNIX for Advanced & Expert Users
I've had some recent success compiling some simple programs to my home directory without root access (wget, screen, less).
My Question is this: Can I compile a complex program like Samba WITHOUT root access to my home directory? Or are the multiple library dependencies going to cause an issue?... (2 Replies)
Discussion started by: goldfish
2 Replies
5. Solaris
OS: Solaris 10
I downloaded a binary from samba.org (3.0.24)
I extracted the file and ran the following command:
# ./configure --prefix=/usr/sfw --with-configdir=/etc/sfw --with-winbind
Now I am trying to understand the compile process but I can't find many answers online
... (10 Replies)
Discussion started by: Keepcase
10 Replies
6. Red Hat
hi,
i have an rpm, and i am looking at the presinstall script. i can see it takes in an argument, but what i do not know is how this argument is passed to the script? is there something that calls the preinstall script? i thought the preinstall script was the first thing executed.
thanks (2 Replies)
Discussion started by: JamesByars
2 Replies
7. Red Hat
Hey all,
I'm not sure if this possible but I had tested it out manually during the installation (placed a sleep in the pre-installation) and it worked. I'm trying to have a pexpect script to log into the mysql and input a new row for the pre-installation, which will end up displaying on a web... (1 Reply)
Discussion started by: karljbaker
1 Replies
8. Solaris
I have two simple questions
First is :can dhcp server NATIVE of solaris perform dhcp
updates of bind via dnssec like dchpd on linux?
Second: Is possible to build a pdc with samba and iplanet ldap server?Or is better with openldap?
I never found howto or discussions about iplanet server.
Thanks (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
9. Solaris
Hi all, I'm trying to update my samba 3.5.10 to 3.6.5 due to security CVE issued with 3.5.
I downloaded and unzipped, did the make and make install and the ./configure.
I didn't use any changes to it and it said it installed correctly added it to my path and it looks like it's operating... (6 Replies)
Discussion started by: mattymatt79
6 Replies
10. Solaris
Hello this is samiulla. i face this issue. i installed samba with pkgadd after i install i add paths for that.
-bash-3.00# echo $PATH
/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/local/samba/sbin:/usr/local/samba/bin/
-bash-3.00#
when enter this commad smbd -D i got this error
smbd -D... (3 Replies)
Discussion started by: samiulla
3 Replies
LEARN ABOUT DEBIAN
cupsaddsmb
cupsaddsmb(8) Apple Inc. cupsaddsmb(8)
NAME
cupsaddsmb - export printers to samba for windows clients
SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ]
DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura-
tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below.
OPTIONS
cupsaddsmb supports the following options:
-H samba-server
Specifies the SAMBA server which defaults to the CUPS server.
-U samba-user[%samba-password]
Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character,
then the text following the percent is treated as the SAMBA password to use.
-a
Exports all known printers. Otherwise only the named printers are exported.
-h cups-server[:port]
Specifies a different CUPS server to use.
-v
Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems.
SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In
order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer
driver download share, as follows:
[global]
load printers = yes
printing = cups
printcap name = cups
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = root
This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system
as needed.
MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or
higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for
64-bit drivers.
The CUPS printer driver is preferred over the Microsoft driver since it supports the page-label, job-billing, and job-hold-until options
fully on all printers. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get
the Adobe driver to support Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
ps5ui.dll
pscript.hlp
pscript.ntf
pscript5.dll
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
CUPS POSTSCRIPT DRIVERS FOR WINDOWS
cupsaddsmb can use the CUPS v6 PostScript printer driver for Windows, which is available for download from the CUPS web site.
The CUPS printer driver is preferred over the Adobe and Microsoft drivers since it supports the page-label, job-billing, and job-hold-until
options fully on all printers. However, currently only Windows 2000 and higher is supported by the CUPS driver, so you will also need to
get the Adobe driver to support Windows 95, 98, and Me clients.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
cups6.inf (from www.cups.org)
cups6.ini (from www.cups.org)
cupsps6.dll (from www.cups.org)
cupsui6.dll (from www.cups.org)
ps5ui.dll (from your Windows system)
pscript.hlp (from your Windows system)
pscript.ntf (from your Windows system)
pscript5.dll (from your Windows system)
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME
cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site
(http://www.adobe.com).
The Adobe driver does not support the page-label, job-billing, or job-hold-until options.
Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named
below:
[Windows 95, 98, and Me]
ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
ICONLIB.DLL
PSMON.DLL
Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
KNOWN ISSUES
Getting the full set of Windows driver files should be easier.
SEE ALSO
smbd(8), smb.conf(5), http://localhost:631/help
http://www.cups.org/windows/
COPYRIGHT
Copyright 2007-2011 by Apple Inc.
25 July 2007 CUPS cupsaddsmb(8)