Xp printing (IP broadcast)

  • Thread starter Thread starter Mike Scriven
  • Start date Start date
M

Mike Scriven

I have a mixed network of 150 PCs. Of those, 25 XP boxes
and the rest 9X. I notice on my Syslog that the XP boxes
are trying to communicate with the IP of 192.0.0.192.
This is the default IP on the HP 4300(as well as most
jetdirects). I have turned the auto look for printers on
XP and still no luck. Any ideas?

PS> I have also disabled IP on the jetdirect. So, I
dont know if its still coming from the XP or coming from
the jetdirect.

Any help would be greatly appreciated.

Mike Scriven
 
Mike Scriven said:
I have a mixed network of 150 PCs. Of those, 25 XP boxes
and the rest 9X. I notice on my Syslog that the XP boxes
are trying to communicate with the IP of 192.0.0.192.
This is the default IP on the HP 4300(as well as most
jetdirects). I have turned the auto look for printers on
XP and still no luck. Any ideas?

PS> I have also disabled IP on the jetdirect. So, I
dont know if its still coming from the XP or coming from
the jetdirect.

Any help would be greatly appreciated.

Mike Scriven
Click to expand...


Windows XP's auto search for printers and shared folders ( NetCrawler )
is searching for windows shares, not JetDirect boxes.
So turning off the NetCrawler won't stop this.

Yes, the factory default on JetDirect boxes is usually 192.0.0.192.
But you are expected to change that to an address suitable for your LAN.

If the XP box is probing for 192.0.0.192, then it may be for one of these
reasons:

-There's an HP autodiscovery utility running?
Disable it.
-Someone set up a TCP/IP port in the printer properties, pointing to
192.0.0.192
Delete the TCP/IP port, and create one that points to the correct IP
address.

Why did you disable TCP/IP on the JetDirect?
What protocol is being used to communicate with the printer?
How do you want the network printing configured?

There's a couple of ways to configure JetDirect printing:

1) Set up a TCP/IP port on each machine on your LAN, pointing at the
printer.
Then each user prints directly to the printer. This is only advisable
in a small ( 2 or 3 PC ) LAN. Network Printers are not very good at
handling a whole bunch of people hitting it simultaneously.

2) Set up a TCP/IP port to the printer on one machine only, ( the
server, if you have one, a win2000/2k3 server is best, but not necessary )
and call
it a print server. Share the printer on that machine. Now have all users
print to the shared printer on the server. This way the print queue is
maintained by a server which is much better at dealing with a whole bunch of
users hitting it at once. The print jobs are then queued on the server
andspoon-fed to the little
network printer in nice , easily digestible spoonfuls. This is really the
only way to do it in a big network.
 
Back
Top