@PaperCut_Software<\/a><\/p>","upvoteCount":1,"datePublished":"2015-10-07T19:57:23.000Z","url":"https://community.spiceworks.com/t/ip-printer-port/441775/2","author":{"@type":"Person","name":"Rod-IT","url":"https://community.spiceworks.com/u/Rod-IT"}},"suggestedAnswer":[{"@type":"Answer","text":"Situation: I changed a old network printer, so I changed almost all driver from the computers of this area. But, some computer still printing to the new printer with a old driver. Incompatible driver makes infinite printer job.<\/p>\n
Question: There is a some free or trial version software to scan TCP/IP ports from computers to identify the hallowed computer and resolve this issue.<\/p>\n
P.D. - Change IP Address from printer is not a option to avoid other issues.<\/p>\n
Share IT: Coming together is a beginning; keeping together is progress; working together is success.<\/p>\n
Henry Ford<\/p>","upvoteCount":7,"datePublished":"2015-10-07T19:43:17.000Z","url":"https://community.spiceworks.com/t/ip-printer-port/441775/1","author":{"@type":"Person","name":"rafacruz","url":"https://community.spiceworks.com/u/rafacruz"}},{"@type":"Answer","text":"
Good morning. i would advise looking into a central print server and utilizing ThinPrint’s virtual driver TPOG for your users this means for an admin when the driver require a change this only need to be done on the central print server and the requirement to go round every machine and update the driver this can now be done in one location. This also means that the interface for the end user is also one layout, reducing the requirement for user training when a new printer is added as we know the what differences between native drivers can be.<\/p>","upvoteCount":0,"datePublished":"2015-10-08T08:41:48.000Z","url":"https://community.spiceworks.com/t/ip-printer-port/441775/3","author":{"@type":"Person","name":"robert-thinprint","url":"https://community.spiceworks.com/u/robert-thinprint"}},{"@type":"Answer","text":"
Print server is the best way. The other option is to go to each computer. Figure out what printers they are actually using. Delete the rest. Highlight any printer, across the top click the Server properties, go to Driver tab, delete all drivers that are not being used.<\/p>\n
Also unders “Resources” on the Spiceworks web page look in “Scripts”. There are batch files and I believe a few VB scripts that will delete the “unused” print drivers after you delete the ones that the user is not using.<\/p>\n
As for the infinite print job sounds like a PS driver was installed and the printer does not have PS capability. Seen this a lot on the Ricoh/Savin line of printers.<\/p>","upvoteCount":0,"datePublished":"2015-10-08T08:55:05.000Z","url":"https://community.spiceworks.com/t/ip-printer-port/441775/4","author":{"@type":"Person","name":"billknight9662","url":"https://community.spiceworks.com/u/billknight9662"}},{"@type":"Answer","text":"
To answer your actual question you have a couple different options to pursue.<\/p>\n
First check out the print log of the affected device. The details vary greatly by manufacturer but most of them will at least have the username for who submitted the job, if your lucky it will even have the workstation that sent it. This should make it easy to trail back to the machine needing updated.<\/p>\n
Your next option is not nearly as easy, but if the log is no help it’s 100% sure to get you the offending PC(s). Get a Hub (not switch) and do a packet capture with Wireshark of the affected devices network traffic. You can determine from the conversation on the wire what IP address is sending to the machine when it goes to the infinite print mode, and make remediation from there.<\/p>","upvoteCount":0,"datePublished":"2015-10-08T12:14:34.000Z","url":"https://community.spiceworks.com/t/ip-printer-port/441775/5","author":{"@type":"Person","name":"williammccoy2","url":"https://community.spiceworks.com/u/williammccoy2"}}]}}
rafacruz
(Rafa Cruz)
October 7, 2015, 7:43pm
1
Situation: I changed a old network printer, so I changed almost all driver from the computers of this area. But, some computer still printing to the new printer with a old driver. Incompatible driver makes infinite printer job.
Question: There is a some free or trial version software to scan TCP/IP ports from computers to identify the hallowed computer and resolve this issue.
P.D. - Change IP Address from printer is not a option to avoid other issues.
Share IT: Coming together is a beginning; keeping together is progress; working together is success.
Henry Ford
7 Spice ups
Rod-IT
(Rod-IT)
October 7, 2015, 7:57pm
2
You should use a print server to avoid this in future, change it there and all clients will get the new settings.
You could also configure a default printer and push the driver via GPO if you wanted.
if you are keen to look at printer management from a network perspective you should look at papercut, there is a free version limited to I think 5 users.
@PaperCut_Software
1 Spice up
Good morning. i would advise looking into a central print server and utilizing ThinPrint’s virtual driver TPOG for your users this means for an admin when the driver require a change this only need to be done on the central print server and the requirement to go round every machine and update the driver this can now be done in one location. This also means that the interface for the end user is also one layout, reducing the requirement for user training when a new printer is added as we know the what differences between native drivers can be.
Print server is the best way. The other option is to go to each computer. Figure out what printers they are actually using. Delete the rest. Highlight any printer, across the top click the Server properties, go to Driver tab, delete all drivers that are not being used.
Also unders “Resources” on the Spiceworks web page look in “Scripts”. There are batch files and I believe a few VB scripts that will delete the “unused” print drivers after you delete the ones that the user is not using.
As for the infinite print job sounds like a PS driver was installed and the printer does not have PS capability. Seen this a lot on the Ricoh/Savin line of printers.
To answer your actual question you have a couple different options to pursue.
First check out the print log of the affected device. The details vary greatly by manufacturer but most of them will at least have the username for who submitted the job, if your lucky it will even have the workstation that sent it. This should make it easy to trail back to the machine needing updated.
Your next option is not nearly as easy, but if the log is no help it’s 100% sure to get you the offending PC(s). Get a Hub (not switch) and do a packet capture with Wireshark of the affected devices network traffic. You can determine from the conversation on the wire what IP address is sending to the machine when it goes to the infinite print mode, and make remediation from there.