There are some particular issues with Samba and Windows NT

1) When you mount a printer using the print manager in NT you may find
the following info from Matthew Harrell <harrell@leech.nrl.navy.mil>
useful:

------------
        I noticed in your change-log you noted that some people were
still unable to use print manager under NT.  If this is the same problem
that I encountered, it's caused by the length of time it takes NT to
determine if the printer is ready.

The problem occurs when you double-click on a printer to connect it to
the NT machine.  Because it's unable to determine if the printer is ready
in the short span of time it has, it assumes it isn't and gives some
strange error about not having enough resources (I forget what the error
is).  A solution to this that seems to work fine for us is to click
once on the printer, look at the bottom of the window and wait until
it says it's ready, then clilck on "OK".

By the way, this problem probably occurs in our group because the
Samba server doesn't actually have the printers - it queues them to
remote printers either on other machines or using their own network
cards.  Because of this "middle layer", it takes an extra amount of
time for the NT machine to get verification that the printer queue
actually exists.

I hope this helped in some way...
-----------


2) Samba does not yet support dual filenames. Some NT applications
(particularly 16 bit apps), don't like the long filenames returned
from the trans2 directory search functions. The proper way of fixing
this is to get Samba to return "dual" filenames. With dual names the
application gets mangled 8.3 names if that's what it needs and long
filenames otherwise. 

Hopefully this will be fixed in a future release of Samba.

