🚀 go-pugleaf

Most print servers widgets either use raw TCP/IP sockets or lpr.
Very few actually run SMB or CIFS.
There is no need to run any form of netbios if you do not require SMB to the
print server widget, and I am not aware of any current widgets that require
you to use SMB, nor any current ones that require netbeui. Virtually all
modern
print server widgets either speak raw TCP/IP over port 9100 or use lpr
or either or both.
SMB is overkill solely for supporting a print server.

"David Taylor" <djtaylor@bigfoot.com> wrote in message
news:MPG.178bb15abe10a84198979c@news.cis.dfn.de...
> > Back up and start over.   NetBEUI is a red herring.   Printer sharing
> > utilizes this protocol.  Even so, The TCP stack on all Windows versions
> > supports (tunnels) NetBEUI so all you need is to see is "TCPIP" in the
> > connection's setup.
>
> Sorry but there's just too much misinformation floating around in this
> thread!  NetBEUI provides a protocol stack in its own right, the API
> layer that is exposed is NetBIOS.  NetBIOS which is a programming API is
> available to use over other protocols such as a TCP/IP stack or IPX/SPX.
>
> File and print sharing utilises the SMB protocol also known as CIFS.
>
> > you wanted to share the printer to other computers in your workgroup,
then
> > netBEUI would come into play.  Again, though, it is there by virtue of
> > having TCPIP loaded.
>
> No, you'll be communicating using SMB by sending these packets by
> calling upon NetBIOS (which in fact is optional) over the TCP/IP stack!
> NetBEUI is doing nothing and doesn't need to be present whatsoever.
>
> David.