I set up some W2K machines under Samba 2.2.1a for printing using the spoolss
features in that Samba release. I now have Samba 3.02a, and have been
forced to use:
disable spoolss = yes
Now, the W2K machines give the error dialog could not connect to printer
because the Windows box is still
I've tried to log dropped packets, but on a big network there are too many
to
sort out. In putting conditions on the logging, I've found that the dropped
packets do not have a source address of an individual machine, or a unicast
address, or a broadcast address. I know something is being dropped
Recently, Windows 2000 SP4 clients have developed a problem when using a
network printer connected to a Samba print share.
Some applications are OK. But take, well, notepad, for example. Selecting
a local printer is normal, but there is a two minute delay (!) in selecting
a network printer.
No, it does not appear to be webclient. There seems to be no such service
on even the latest Win2K.
It appears there is some kind of anti-worm change in the MS-RPC code
contained in the latest security patches.
Samba 2.2.8a will hang for about a minute. Samba 3.0.2a will hang for
about three
