Samba Busted - Solved

[dangbert]

Here is the result of running "testparm"

testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Processing section "[pdf-gen]"
Loaded services file OK.
Warning: Service printers defines a print command, but rameter is ignored when using CUPS libraries.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        workgroup = MDVGROUP
        server string = %h
        map to guest = Bad User
        log file = /var/log/samba/%m.log
        max log size = 50
        printcap cache time = 60
        printcap name = cups
        dns proxy = No

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        create mask = 0700
        guest ok = Yes
        printable = Yes
        print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.
        use client driver = Yes
        browseable = No

[print$]
        path = /var/lib/samba/printers
        write list = @adm, root
        inherit permissions = Yes
        guest ok = Yes

[pdf-gen]
        comment = PDF Generator (only valid users)
        path = /var/tmp
        printable = Yes
        printing = bsd
        print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
        lpq command = /bin/true
        lprm command = lprm -P'%p' %j


Here is the result of  smbclient -L computername -U username


Domain=[DEBS] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

        Sharename       Type      Comment
        ---------       ----      -------
        E$              Disk      Default share
        BrotherH        Printer   Brother HL-2040 series
        IPC$            IPC       Remote IPC
        print$          Disk      Printer Drivers
        SharedDocs      Disk     
        ADMIN$          Disk      Remote Admin
        C$              Disk      Default share
        Printer         Printer   Microsoft XPS Document Writer
Domain=[DEBS] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
[root@localhost samba]#

I hope this helps.  We still cannot open Samba from the Control Panel though.

Thanks

Deb

[hankcurt]

There is nothing in the testparm output that indicates a problem in the smb.conf file that would keep samba from starting.  It is really difficult to tell what you might have erased when manually deleting files. You could try installing the packages related to samba by searching "samba" in the package manager and reinstalling the already installed packages.  On my system, this includes:

libcups2
libntlm0
libsmbclient0
libtalloc1
libtdb1
samba-client
samba-common
samba-server
samba-winbind

Also, you could open a konsole window and start the samba control panel by typing

draksambashare

This should start the same samba control panel as you get going through the "Configure Your Computer" panel.  If it fails, look at the konsole window for any errors that it displays.  If it still doesn't start, you might also try reinstalling the configuration utility packages

drakx-net
drakx-net-text
libdrakx-net

The smbclient output that you posted shows that your printer is indeed available from the windows machine.  The next thing I would try on this would be to go through the CUPS configuration.

[Xero]

No idea why it keeps crashing on you. Are you fully updated?

[dangbert]

Here is what I got when I ran "draksambashare" in a terminal as root:

root@localhost samba]# draksambashare
Can't locate Libconf/Glueconf/Samba/Smb_conf.pm in @INC (@INC contains: /usr/lib/libDrakX /usr/lib/perl5/site_perl/5.10.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.10.1 /usr/lib/perl5/vendor_perl/5.10.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.1 /usr/lib/perl5/5.10.1/i386-linux-thread-multi /usr/lib/perl5/5.10.1 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl .) at /usr/sbin/draksambashare line 38.
BEGIN failed--compilation aborted at /usr/sbin/draksambashare line 38.

[Xero]

Perl error. Are you fully updated? Has everything been fully updated?

[ElCuervo]

Perl error. Are you fully updated? Has everything been fully updated?

+1 on this - your inoperative PCC seems to indicate that you are not. By fully updated, we are talking about Reload>Mark all updates>Apply>Apply in Synaptic - the PCLinuxOS mantra!

[hankcurt]

The missing perl module appears to be in the package perl-Libconf. 

I don't have my pclinuxOS machine with me to verify this, but you should probably look for that package and re-install it if simply updating everything, as the previous posters suggested, does not fix it.

[dangbert]

Perl was the problem with Samba loading.  I did a full reinstall of Perl, along with the update off the repository last night and Samba was working this morning.  However, it still does not see the printer.  When I open the Control Panel, Hardware, Printers, Samba opens and gives me the options of either looking for a printer on Parallel 0 or a Manual Setup.  That is with all three search options chosen (including Windows machines).  When I choose the fourth option of looking for a printer at a particular URL and enter the location of the Windows box, it cannot find a printer.

[nerdful1]

That's exactly the problem that suddenly occurred to me a few weeks ago.
When going what used to be the usual route to, PCC, add printers, all I would get is the parallel port and manual option.

So I learned the webpage 631 thing, and get by, but try to explain that to a Linux beginner.

Glad (or maybe not so) see it was not me.

[wayne1932]

I've been wondering what happened to my printer stuff too.  I don't print that much, the printer is connected to my wife's XP machine and I used to be able to print to it.  But since the latest updates, seems like every time I want to print I have to find and reinstall the printer.  And even then it may not work.  It's just easier to drop the file on my wife's desktop and have her print it for me.  Or I can stretch the cable across the room and print directly.  Any way, it's always a hassle. 

[dangbert]

Thanks to Wayne's comment, I think I have found the source of the problem.  I tried to open Localhost and go to page 631 and was told that Firefox could not find localhost.

To do that, I opened a terminal (more on this in a moment) and typed "kdesu firefox" entered the password and I was off to the races, I thought.  I typed "http://127.0.0.1" and was told that Firefox could not find the URL.  I retyped it and substituted localhost for 127.0.0.1 and got the same result.  So, what is blocking, or what could be blocking me, from localhost?

My Firewall is set with all blocks checked except "Everything."

You noticed I used "kdesu" to get to a graphics root terminal.  The "root terminal" off the menu will not work and I have to use the user terminal and do either an "su" or "kdesu" to access a root terminal.  Any idea why?

Thanks for all the help

Deb

[ElCuervo]

127.0.0.1 is loopback address. Your host file works better like this:

alan@alan-ps7112:~$ cat /etc/hosts
192.168.1.6   alan-ps7112   # Added by NetworkManager
127.0.0.1   localhost.localdomain   localhost

You can configure your hosts in PCC. Then http://localhost:631/ should get you to CUPS.

[dangbert]

Okay:

Under CC Hosts I have 127.0.0.1 localhost.localdomain  localhost


Under /etc/hosts I have 127.0.0.1 localhost.localdomain    listed
Under /etc/hostsdeny everything is commented out
Under /etc/hostsallow everything is commented out
under /etc/host.conf I have

order hosts,bind
multi on
nospoof on
spoofalert on

So from the above, I assume localhost is set up.  Am I wrong?

However Firefox cannot reach it.

Thanks

Deb

[ElCuervo]

You should still have a host name like my example, with a similar IP address. In PCC>Network & Internet>Host Definitions, you can Add one that corresponds to your machines IP address and give it a FDQN (fully qualified domain name), too, something like thisbox.dangbert.net.

All that makes it easier for machines to navigate, but I don't think it matters as far as connecting to CUPS. Did you try setting up CUPS through PCC>Hardware>Set up printers...>Configure CUPS?

[dangbert]

I will do the additional entry in CC as you suggested.  Cups works fine on the Linux box, if that means anything.

As for how I was trying to set up the printer, yes it was through the CC, Hardware, Printers.  That is the way I have always done it.

Deb