|
Jim wrote:"On one of our *OUTQs which is a TCP/IP attached printer a 300+ page report "coughed" and started printing again from page 1. In the writer job I see a few of these messages. Is there anything we can do to prevent this? Or is it just caused by network traffic. Because we tried 10 minutes later and it worked fine." Mike wrote: "95 percent of the time it winds up being a duplicate IP address." Jim - Like Mike, I see this message quite often, too. Unlike Mike, it usually winds up being another job already printing on that printer (from a PC app). Luckily, the report doesn't usually begin printing again from page 1. Not sure what you would do to prevent it but it seems to me that your first chore is to determine whether it's duplicate addresses, other reports, or something else. Jim also wrote: "Isn't DHCP on our NT Server side of the network supposed to stop that though?" Only if you add the static printer address to the list of addresses that are not handed out by DHCP. HTH, Steve
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.