Re: smb and 95
To add to the mistery, I have one win95 machine that works just
fine with two linux samba servers, but I have three win95
machines that refuse to connect, stating that the share name is
incorrect.
Anyone have any clues ??
The users now all have accounts on the linux server and I have
used all three levels of access (server, user and share) but
have not had any luck. I am assuming it is something obscure
with the win95 machines, but in the system description they are
all using the exact same version of win95 (4.00.950 B) which is
the osr2 release I believe.
I read through the samba docs and applied the plain password
registration file on one of the non-working win95 boxes, but
that did not help either.
I have tried a number of different uses, but they all act in the
same way.
I really have no clue what is going on, and assume that it is
something wacky with windoze, maybe to do with regional
software, some is English(British) and some is
English(International). But I am only guessing....
Last resort is to upgrade the machines to win98, which seems to
work just fine on six machines that I have tried with the samba
servers.
Hope some one can help,
John
John Stevenson wrote:
>
> Hello,
>
> I am having problems installing printers on win95 machines. I
> am using a linux server running debian slink and have been able
> to set up clients running windows98 to use the linux printer,
> but windows 95 refuse to acknoledge that the server even exists.
>
> Attached is my smb.conf file.
>
> ----------------------------------------------------------------
> ;
> ; /etc/smb.conf
> ;
> ; Sample configuration file for the Samba suite for Debian GNU/Linux
> ;
> ; Please see the manual page for smb.conf for detailed description of
> ; every parameter.
> ;
>
> [global]
> printing = bsd
> printcap name = /etc/printcap
> load printers = yes
> guest account = nobody
> invalid users = root
>
> ; "security = user" is always a good idea. This will require a Unix account
> ; in this server for every user accessing the server.
> ; security = user
>
> ; Change this for the workgroup your Samba server will part of
> workgroup = OA.NL
>
> server string = %h server (Samba %v)
>
> ; This socket options really speed up Samba under Linux, according to my
> ; own tests.
> socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096
>
> ; Passwords are encrypted by default. This way the latest Windows 95 and NT
> ; clients can connect to the Samba server with no problems.
> encrypt passwords = yes
>
> ; It's always a good idea to use a WINS server. If you want this server
> ; to be the WINS server for your network change the following parameter
> ; to "yes". Otherwise leave it as "no" and specify your WINS server
> ; below (note: only one Samba server can be the WINS server).
> ; Read BROWSING.txt for more details.
> wins support = no
>
> ; If this server is not the WINS server then specify who is it and uncomment
> ; next line.
> wins server = 172.16.1.10
>
> ; Please read BROWSING.txt and set the next four parameters according
> ; to your network setup. There is no valid default so they are commented
> ; out.
> ; os level = 0
> ; domain master = no
> ; local master = no
> ; preferred master = no
>
> ; What naming service and in what order should we use to resolve host names
> ; to IP addresses
> name resolve order = lmhosts host wins bcast
>
> ; This will prevent nmbd to search for NetBIOS names through DNS.
> dns proxy = no
>
> ; Name mangling options
>
> preserve case = yes
> short preserve case = yes
>
> ; This boolean parameter controlls whether Samba attempts to sync. the Unix
> ; password with the SMB password when the encrypted SMB password in the
> ; /etc/smbpasswd file is changed.
> unix password sync = false
>
> ; For Unix password sync. to work on a Debian GNU/Linux system, the following
> ; parameters must be set (thanks to Culus for pointing this out):
> passwd program = /usr/bin/passwd %u
> passwd chat = *New\spassword:* %n\n *Re-enter\snew\spassword:* %n\n *Password\schanged.* .
>
> ; The following parameter is useful only if you have the linpopup package
> ; installed. The samba maintainer and the linpopup maintainer are
> ; working to ease installation and configuration of linpopup and samba.
> ; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
>
> ; The default maximum log file size is 5 MBytes. That's too big so this
> ; next parameter sets it to 1 MByte. Currently, Samba rotates log
> ; files (/var/log/{smb,nmb} in Debian) when these files reach 1000 KBytes.
> ; A better solution would be to have Samba rotate the log file upon
> ; reception of a signal, but for now on, we have to live with this.
> max log size = 1000
>
> [homes]
> comment = Home Directories
> browseable = no
>
> ; By default, the home directories are exported read only. Change next
> ; parameter to "no" if you want to be able to write to them.
> read only = no
>
> ; File creation mask is set to 0700 for security reasons. If you want to
> ; create files with group=rw permissions, set next parameter to 0775.
> create mask = 0775
>
> ; Directory creation mask is set to 0700 for security reasons. If you want to
> ; create dirs. with group=rw permissions, set next parameter to 0775.
> directory mask = 0775
>
> [printers]
> comment = All Printers
> browseable = yes
> path = /tmp
> printable = yes
> public = yes
> writable = yes
> create mode = 0700
>
> ; A sample share for sharing your CD-ROM with others.
> ;[cdrom]
> ; comment = Samba server's CD-ROM
> ; writable = no
> ; locking = no
> ; path = /cdrom
> ; public = yes
> ;
> ; The next two parameters show how to auto-mount a CD-ROM when the
> ; cdrom share is accesed. For this to work /etc/fstab must contain
> ; an entry like this:
> ;
> ; /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
> ;
> ; The CD-ROM gets unmounted automatically after the connection to the
> ;
> ; If you don't want to use auto-mounting/unmounting make sure the CD
> ; is mounted on /cdrom
> ;
> ; preexec = /bin/mount /cdrom
> ; postexec = /bin/umount /cdrom
Reply to: