I just noticed that JetAdmin has a TCP Discovery under Options>Preferences.
Now, I appear to have two different versions of JetAdmin because the one
on my domain server does not have the options that are on another box. The
one on the domain server was setup to broadcast on it's network AND the one
on the other side of the firewall. So that was where the IP scan was
coming from.
The other box's JetAadmin has more options - you can tell it to just hit
certain IP addresses to find it's printer and it has the (more dangerous)
"broadcast on another network" in the Advanced option.
In any case, it doesn't seem to work very well. I have tried to tell
JetAdmin to look for two JetDirect connected printers but it never finds the
second printer. On the domain server, it already had my mopier but when I
tell it the IP address of an hp6mp it never finds it.
Also noticed in JetAdmin that you can double click on a printer and it
will give you all sorts of SNMP data so that was why it was sending out
scans on the SNMP port. I would bet that it is looking for a certain
MIB item and if it finds it then it knows it has an HP printer.
Now let's see - no one's PC can see the Tektronix printer and lpr on the PCs
is trying to hit every printer on the system before it will let you print
to -Pprinter - why? who knows but if it cannot connect to every one it won't
let you print - wait it's worse than that, even if you don't have a printer
but have a raw lpr port still on the system, it still tries to hit it...ugghhh
Don
|
|
