If you use Samba from a Windows client, filename case sensitivity can be a big problem. UNIX systems pay attention to character case. In other words, test.txt and Test.txt are entirely different files. Case sensitivity can be a problem when you're using some applications, such as text editors and decompression programs from a Windows client, to write data to a UNIX server. Some client packages don't pay attention to case sensitivity in filenames, and others do. Typically, software "Designed for Windows 95 and NT" works best. As people say on the Internet, YMMV (your mileage may vary), depending on the client OS and software you use. Be sure to test carefully.
UNIX and NT Integrated
So you see, integrating UNIX and NT for simple file and print services isn't very difficult. Keep in mind that you can do lots of other functional things with Samba--I've only scratched the surface here. So make sure you read all the manual pages and text files, and be aware of the pitfalls I pointed out. One final note, you can locate information on where to get help using Samba in the included Support.txt file. So, now that you've gotten UNIX and NT integrated to some extent, perhaps it's a good time to tackle that Novell or VMS server.
Samba builds a multilane expressway between NT and UNIX systems.
Samba runs on UNIX, enables a UNIX host to establish shares that Windows clients can map, and enables UNIX clients to map shares on Windows hosts.