Hello DaveC,

DaveC schrieb/wrote:

Your Windows clients with at least Windows 2000 could access the shared
printer(s) using IPP, so there's no need for SMB.

I don't know; I haven't ever used it.
Just tell it not to bother you with connections to Ports 137-139 and
445. Or uninstall it.

Hello DaveC,

DaveC schrieb/wrote:

Deactivate SMB using your "Directory Services" Utility.

Gruss,
Christian

"smb client" continually wants to connect to some server. Whenever Little
Snitch puts up a window, I choose "Deny", "any connection", and "forever".
But immediately after this, smb client asks again:

192.168.1.12 on TCP port 445 (microsoft-ds)

According to System Preferences > Network > TCP/IP, that's the IP address of
my computer. No other computers are on the network.

I looked at the settings for Little Snitch, and the one and only rule for
"smb client" is "Deny any connection forever".

I do have a USB printer attached that I am sharing with other Macs and PCs
over the wireless network. This requires "Printer Sharing" and "WIndows
Sharing" be turned on in System Preferences. But I can't imagine that these
features would result in smb client trying to access the computer it's
running on. But then, I don't know much about the inner workings of xNIX or
OS X.

What am I doing wrong?

Ideas?

PowerBook G3/400; OS X 10.3.9; Little Snitch 1.2.1

Hello Gary,

Gary Carroll schrieb/wrote:

Ah.
Then you've got to add your printers to papd.conf by hand, and you can
delete the "cupsautoadd" line.

That's right.
Have you built your own netatalk, or is it the version packaged by
your distributor?

Hello Gary,

Gary Carroll schrieb/wrote:

That's because OS X uses CUPS, too.

[..]

Have you "exported" your printers using netatalk?
My papd.conf looks like this:

LaserJet 6MP:\
:pr=|/usr/bin/lp -d LaserJet6:\
:pd=/usr/local/etc/netatalk/laserjet6.ppd:

And printing from MacOS 9 clients works like a charm.
Is your papd started at all? Does your kernel support AppleTalk?

Since I am not sure where the problem lies I will explain the situation,
then give my suspicions. I am using a Linux (Fedora core 5) cups print
server. (FC5 linux uses cups and is very similar to OSX in configuration
files.) This server will serve Mac OSX, OS 9.x, Windows (XP and 2000) and
AS400s.
The OSX and Windows use IPP and work perfectly. AS400 is using
LPR and also works. I have also tested printing from Windows via
LPR ("create new port"), and this works also. Just less
conveniently that IP printing.

The 9.x boxes don't work at all. I have tried to enable Appletalk via
netatalk and can share directories on the Linux box with 9.x by connecting
with Appleshare. However, 9.2 does not see printers shared by Linux. I
tried to connect using "Apple Desktop Printer Utility" to create an LPR
printer, connect to IP address and queue name. The utility says it can see
the printer (I think this just verifies the IP address, not port) but
after creating the printer, jobs fail to send. The error message is that
the printer is not accepting jobs.

Since I am not sure where the problem lies I will explain the situation,
then give my suspicions. I am using a Linux (Fedora core 5) cups print
server. (FC5 linux uses cups and is very similar to OSX in configuration
files.) This server will serve Mac OSX, OS 9.x, Windows (XP and 2000) and
AS400s.
The OSX and Windows use IPP and work perfectly. AS400 is using
LPR and also works. I have also tested printing from Windows via
LPR ("create new port"), and this works also. Just less
conveniently that IP printing.

The 9.x boxes don't work at all. I have tried to enable Appletalk via
netatalk and can share directories on the Linux box with 9.x by connecting
with Appleshare. However, 9.2 does not see printers shared by Linux. I
tried to connect using "Apple Desktop Printer Utility" to create an LPR
printer, connect to IP address and queue name. The utility says it can see
the printer (I think this just verifies the IP address, not port) but
after creating the printer, jobs fail to send. The error message is that
the printer is not accepting jobs.

In article <1159277183.762749.131080@i42g2000cwa.googlegroups.com>,
booksmartbilly@gmail.com wrote:

booksmartbilly@gmail.com wrote:

Apparently, this was the result of the printer being asleep. Once I
woke the printer and attempted another install everything went well.

Thank you Matt for your guidance.

Regards,

Bill

booksmartbilly@gmail.com wrote: