The Epson Stylus Color 1160 on Samba/Windows 2K

I did not need to add Samba or CUPS as they already exist on a full White Box Linux installation, as does parallel port support.

I changed my smb.conf file to read:

[global]

    workgroup = FRED
    netbios name = SERVER
    server string = samba server
    printcap name = /etc/printcap
    printing = cups
    log file = /var/log/samba/%m.log
    max log size = 50
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    username map = /etc/samba/smbusers
    password server = None
    guest ok = yes
    dns proxy = no

[homes]
    comment = Home Directories
    browseable = no
    writeable = yes

[printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    guest OK = yes
    writable = no    
    printable = yes
    create mode = 0700
    print command = lp -d %p -o raw %s; rm -f %s
    lpq command = P%p
    lprm command = P%p %j
    use client driver = yes

And restarted Samba and CUPS.

Then I installed the printer on Windows 2000 using the Add Printer Wizard and selected the Linux server.  Windows asked for a driver and I installed the Epson driver from the manufacturer’s disc.

The printer appeared as stp on IP_ADDRESS – a little unintuitive, but the test page printed OK.

It now appeared that the stp printer is seen by CUPS as a raw printer – printing from Open Office on the Linux box itself produced that infinite PostScript printout that we all know so well.  I reinstalled the Epson via the CUPS web administrator as a second printer, stp1, and so far this works from Open Office if chosen from the list at print time.

However, The Gimp still uses stp quite happily.

Obviously the setup for this printer is fairly complex as it is a fairly uncommon one.

Only time will tell if this works for everyone!


Samba Notes

For group shares, ensure the UNIX group is right.

UNIX directory permissions should be 775 (user rwx, group rwx, other r-x), or 770 (user rwx, group rwx, other ---) unless you want read-only.

Change permissions on all files in all subdirectories:

chmod -R 775 *

Samba and Windows 98

If Windows 98 is not set up for separate users, you cannot connect to a Samba share.

Go to Control Panel.  Select Passwords icon, then User Profiles tab.  Then choose radio button "Users can customize their preferences....".  The check BOTH the options for User profile settings.

Then select Change Passwords tab on the left of the dialog box.

If the Change Passwords tab is not there, you must click on OK, then reboot.  Then when Windows restarts, give it the username and password for the Samba share.  You will then be asked if you want to have a profile.  Answer Yes.  Windows will create a separate profile and password file for you.  Now you can connect to Samba.

If you have a Change Password tab, select the Change Windows Password button.  Change your password to the one for the Samba share.



Help!  I Can't Save My Spreadsheet to the Samba Server!


After a network outage, you may find it impossible to save an Excel spreadsheet you had open and had already saved before the outage, if you change it and then try to save it again.

This happened with a Samba server and a complex 1.2Mb spreadsheet.  The spreadsheet could be saved in My Documents but attempts to save it to the Samba server caused error messages such as "Data has been lost" or "Disk Full".

Solution:

On the server there were several 1.2Mb files with nonsense names and no file extensions, such as CeCd4100 or just long strings of numbers.  The time stamps were for times when attempts had been made to save the spreadsheet.

Deleting these temporary files then made it possible to save the spreadsheet without errors.

Cause

Excel saves its files in this way:

A temporary file with a random name and no extension is created in the folder specified in Save As, or in the destination it was opened from.

If the file is changed, the original file is deleted and Excel renames the temporary file to the filename as specified in the Save As dialog, which unless specified by the user, would be the original name.

In this instance, the network connection dropped out and it appears that Excel could not make a connection between the temporary files and the file being saved.

This issue has nothing to do with Samba or with file permissions, but is a "feature" of MS Excel.


Home  |  Problems Solved | Printing  | Samba | Windows Corner | WBEL to CentOSOddments