I know that's a silly title, but that's the shortest way I could describe it.
I'm a field engineer for an office equipment company, and I'm looking for an app, tool, or utility that does something very specific.
Quite often requests for service are placed on office machines when the problem truly lies in the network, or the machine sending the print job. Many times, one specific machine, or workgroup, or building cannot print, but others can. This is of particular importance to us as calls placed due to machine failure/malfunction are covered under our customers service contracts, but calls placed due to network/machine issues are billable at a high rate for time and mileage (especially important covering a multi-state area). A full billable day (including drive time) can exceed $1000.00, so customers get a bit upset at receiving this bill if they don't believe the problem was caused by their network, and our directors get a little cranky if refuse to pay.
You'd think that the mere fact that it is possible to print from one machine, but not another would be sufficient to convince the local "IT guru" that he has a network issue. You'd be wrong. I've actually heard the phrase "It can't be the network. I installed it myself!" So, this is what I'm looking for...
I'd like to be able to unplug the office machine, and plug my laptop into the same jack.
I'd like to then assign my laptop the same IP address as the now disconnected printer.
I'd like it to show (in plain english) any print jobs that were received (and if possible - sender, document name, file size, etc).
I'd like it work even across multiple switches and routers.
I'd like it to accept print jobs from any OS and any print driver.
My thinking is that if I can show Mr. IT Guru, a specific list of print jobs that made it to that wall jack and where they came from (and more importantly which ones didn't), I might relieve alot of stress for company and client. Is something like this even possible????????????
I'm sorry this was such a long convoluted post, or if this is the wrong forum or heading, or if this is just the wrong site to be asking...
Pinging the IP address or network name of the printer should tell you if its the network or computer. If it pings fine then it is 99.99% chance its the computer. Only other probable cause could be if they are using a print server or shared printers connected directly to a pc instead of the network.
As for what your looking for, I don't know of anything like that off the top of my head.
Message edited by sturm on 04-01-2009 at 06:20:59 PM
------------------------------I ain't signing nothin
Reply to sturm
I appreciate your response. Diagnosing the problem isn't so much my problem, as is convincing a school administrator, office manager, or IT person of the result.
I realize that it's going to be tough to find something like this. May just have to find someone to create it.
I know that's a silly title, but that's the shortest way I could describe it.
You'd think that the mere fact that it is possible to print from one machine, but not another would be sufficient to convince the local "IT guru" that he has a network issue. You'd be wrong. I've actually heard the phrase "It can't be the network. I installed it myself!" So, this is what I'm looking for...
I'd like to be able to unplug the office machine, and plug my laptop into the same jack.
I'd like to then assign my laptop the same IP address as the now disconnected printer.
I'd like it to show (in plain english) any print jobs that were received (and if possible - sender, document name, file size, etc).
I'd like it work even across multiple switches and routers.
I'd like it to accept print jobs from any OS and any print driver.
People usually set up network printers by choosing "Network Printer" option. What it means is the PC will send out broadcasts to find and send jobs to the printer, which means it is limited to one subnet or broadcast domain. If you want to print across different subnets through routers & switches, set up a TCP/IP based printer port. Go to Add New Printer > Local Printer, deselect autodetect > Create New Port > type in IP address > so on and follow instructions there. I believe this is different from print server route and web-based printing http://xxx.
Quote :
My thinking is that if I can show Mr. IT Guru, a specific list of print jobs that made it to that wall jack and where they came from (and more importantly which ones didn't), I might relieve alot of stress for company and client. Is something like this even possible????????????
Though I haven't done, I am sure adding a print server in front of the printer will do it by keeping logs. If off-the-shelf print servers can't maintain logs, then set up a UNIX print server. Print server here will centralize control. Without it, you'll be hard-pressed due to many machines.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.