Yes! Thursby now have a CIFS Client / Server called DAVE - see http://www.thursby.com/. They test it against Windows 95, Windows NT and samba for compatibility issues. At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from the Thursby web site (the speed of finder copies has been greatly enhanced, and there are bug-fixes included).
Alternatives - There are two free implementations of AppleTalk for several kinds of UNIX machnes, and several more commercial ones. These products allow you to run file services and print services natively to Macintosh users, with no additional support required on the Macintosh. The two free omplementations are Netatalk, http://www.umich.edu/~rsug/netatalk/, and CAP, http://www.cs.mu.oz.au/appletalk/atalk.html. What Samba offers MS Windows users, these packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems) see http://www.eats.com/linux_mac_win.html
The following answer is provided by John E. Miller:
I'll assume that you're able to ping back and forth between the machines by IP address and name, and that you're using some security model where you're confident that you've got user IDs and passwords right. The logging options (-d3 or greater) can help a lot with that. DNS and WINS configuration can also impact connectivity as well.
Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
configuration (I'm too much of an NT bigot to know where it's located
in the Win95 setup, but I'll have to learn someday since I teach for a
Microsoft Solution Provider Authorized Tech Education Center - what an
acronym...)
This field essentially creates 'invisible' sub-workgroups on the same
wire. Boxes can only see other boxes whose Scope IDs are set to the
exact same value - it's sometimes used by OEMs to configure their
boxes to browse only other boxes from the same vendor and, in most
environments, this field should be left blank. If you, in fact, have
something in this box that EXACT value (case-sensitive!) needs to be
provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
your Scope ID is configured as the string 'SomeStr' in Win95 then
you'd have to use smbclient -iSomeStr
To syncronize your PC's clock with your Samba server:
Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba - see: BROWSING.txt *** for more information.
Then add
NET TIME \\%L /SET /YES
All of the above programs are applications that sit on an NT box and allow multiple users to access the NT GUI applications from remote workstations (often over X).
What has this got to do with Samba? The problem comes when these users use filemanager to mount shares from a Samba server. The most common symptom is that the first user to connect get correct file permissions and has a nice day, but subsequent connections get logged in as the same user as the first person to login. They find that they cannot access files in their own home directory, but that they can access files in the first users home directory (maybe not such a nice day after all?)
Why does this happen? The above products all share a common heritage (and code base I believe). They all open just a single TCP based SMB connection to the Samba server, and requests from all users are piped over this connection. This is unfortunate, but not fatal.
It means that if you run your Samba server in share level security (the default) then things will definately break as described above. The share level SMB security model has no provision for multiple user IDs on the one SMB connection. See security_level.txt in the docs for more info on share/user/server level security.
If you run in user or server level security then you have a chance, but only if you have a recent version of Samba (at least 1.9.15p6). In older versions bugs in Samba meant you still would have had problems.
If you have a trapdoor uid system in your OS then it will never work properly. Samba needs to be able to switch uids on the connection and it can't if your OS has a trapdoor uid system. You'll know this because Samba will note it in your logs.
Also note that you should not use the magic "homes" share name with
products like these, as otherwise all users will end up with the same
home directory. Use
This info from Stefan Hergeth hergeth@f7axp1.informatik.fh-muenchen.de may be useful:
A network-printer (with ethernetcard) is connected to the NT-Clients via our UNIX-Fileserver (SAMBA-Server), like the configuration told by Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
This is from Paul Eggert eggert@twinsun.com.
Most likely it's a problem with your time zone settings.
Internally, Samba maintains time in traditional Unix format, namely, the number of seconds since 1970-01-01 00:00:00 Universal Time (or ``GMT''), not counting leap seconds.
On the server side, Samba uses the Unix TZ variable to convert internal timestamps to and from local time. So on the server side, there are two things to get right.
StdOffset[Dst[Offset],Date/Time,Date/Time]
where:
Question:
On NT, I opened "Printer Manager" and "Connect to Printer".
Enter
You do not have sufficient access to your machine
to connect to the selected printer, since a driver
needs to be installed locally.
In the more recent versions of Samba you can now set the "printer driver" in smb.conf. This tells the client what driver to use. For example:
printer driver = HP LaserJet 4L
To find the exact string to use, you need to get to the dialog box in your client where you select which printer driver to install. The correct strings for all the different printers are shown in a listbox in that dialog box.
You could also try setting the driver to NULL like this:
printer driver = NULL
As of SP3, Microsoft has decided that they will no longer default to passing clear text passwords over the network. To enable access to Samba shares from NT 4.0 SP3, you must do ONE of two things: