Dislikes: 0
Originally Posted by mnchstr2k
Actually had a customer with a network printer set up with a wireless adapter. One thing they did not do was password protect the adapter so anyone that discovered the new wireless ip address could print to it. So a joker found the new wireless receiver and started printing all sorts of obscene jokes on the printer with his laptop.
Once had a small 2 man office where I had hooked up a MFD printer on their network. The guy in charge had no clue how networks and printers work, could not give me any info on any of the settings.
2 weeks after setting him up he called me as he wanted to add another user to scan to his desk top. I explained how he could scroll through the device and follow the network to each user, just as I did earlier with him watching. He then asked me his network name, I paused, rolled my eyes and told him that is like me asking him what my dog's name is.
We used to have a very large customer that tried to pawn off their IT work to us, even though they had their own IT department. Most often it was embarrassingly basic. For example:
The maintenance folks reposition a MFP somewhere else in the building. They can figure out how to plug in the power plug. So I get service call saying that it won't print. When I talk to the IT gentleman he says it won't ping. When I get there I discover there is no network cable, and no network port within 100 feet. It seems our IT professional is glued to his fricking desk chair. That was the first one I billed.
A few days later I get a call that the MFP won't print in color, and true enough, it's not printing in color. Upon closer examination I see that the IT professional installed an HP4 print driver. Do you think that might be why it's not printing in color? That was the second one that I billed.
A couple of weeks later I get another call for not printing. More accurately it prints a few of the pages, than drops off the network. I plug my laptop into the network drop and start a continuous ping back to the print server. I get:
<1ms
<1ms
<1ms
<1ms
=5ms
=10ms
=56ms
=247ms
=Request Timed Out
=Request Timed Out
=Request Timed Out
=1047ms
=52ms
<1ms
<1ms
etc. etc.
How can the MFP cause this when it's not even on the network now? It's my laptop doing the ping. That was the third one that I billed. They started doing their own IT at that point. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
I am all to familiar with incompetent IT Nubs, seems to me these kids graduate college and think they are Bill Gates and don't know there ass from there elbow most of the time... Inflated Egos with no brains but have that piece of paper they worked 4 years or more for that Mom and Dad paid $$$$$$$ for.
Last edited by copiertec; 07-06-2019 at 09:13 PM.
Been there done that quite a few times with the networked copiers. Especially fun was one contract IT "specialist" that insisted that "all printers will work with the HP 4 drivers. It's the standard" Finally got so fed up after going to one customer the third time I billed them travel and time spent when the IT genius kept telling them the hp 4 drivers would be fine printing to a 50 ppm copier on ledger sized paper. Yes the service calls were for paper jams when the print driver would only print to letter legal and they were using ledger sized paper. I had to print from my laptop to the ledger sized paper without problems. And then showed the office manager on one of their pc's the lack of proper driver . Handed her the cd from the supply tray of the copier and had her install the drivers and test it. I would specifically refuse to install drivers though when the computer network was under contract to anyone else. We were warned in class to avoid that sort of problem and were also told to make sure there was no IT service agreement with another company. Seems a few of the earlier tech went back and did install drivers and when anything went wrong with any of the pc stations the contract IT people would blame the copier tech and then bill outrageous sums to "fix what the untrained technician screwed up"
was given a job one afternoon, customer couldn't print or scan to/from copier, got there the next morning, it was working fine, that afternoon customer logged the same call, went in the following morning, it was fine, again, in the afternoon customer logged the same call, I happened to be near, and sure enough....the copier was offline, checked the copier, there were no lights for the network, traced the network across the room to the router, there were no lights on, as the extension lead it was plugged into was switched off at the mains.... I mentioned this to the receptionist, "oh" she said, "that's so and so's desk, he finishes at 1 and turns everything off when he goes"......
Tip for the day; Treat every problem as your dog would.....If you cant eat it or f*ck it....then p*ss on it & walk away...
We got bought out by another company. I got was sent on three calls where the brand new copier/printer quit printing within the first two weeks. I get there and find out the copier quit printing when the office manager left and turned off their computer. Turned out our supervisor was installing the drivers on that pc and then just sharing the printer on the network when he set up and delivered the copier. You probably know that if you share a printer then that pc must be left on. The users of those particular computers always turned it off when they left the office for more that thirty minutes. Finally had it out and showed Mr. "I know how to set these up, you can't teach me anything" that if a printer is shared and the pc with drivers installed is shut off then the copier/printer is now no longer on the network either. He did not believe me until I set up a machine we were getting ready for delivery the next day in our shop. Set it up on the parts order pc and then shared it on three other pc's. Then turned off the parts pc and the printer would not print from the other three machines either after we sent test prints from all four computers. His only explanation was he set the machines up as shared printers because then he did not have to spend all that extra time installing drivers on the other computers.
" Stupid is as stupid does"- Forrest Gump
I had an interesting one some years ago.
Customer had an MFP set up to scan to folder on a server share. I got a couple calls about not being able to scan, but every time I attended the call, in the morning, it seemed to be working. After some prying they finally showed me the 'server', which turned out to be a Windows XP box and not really a server OS at all. Apparently when everyone in the office was in for the day they started having issues, exactly 10 employee PCs! Non-server Windows OSs can handle only 10 concurrent connections, so once the 10th PC was turned on and accessed the 'server' the MFP was bumped and not allowed to reconnect. Call out for not scanning! Argh!
Customer was completely oblivious to the restriction on the XP machine.
I love the customers that use a piece of crap computer and refer to that as "our sever", but always call the Copier Company when their devices will not scan or print and think it's the copier. How about investing in a "real" server and stop with cheap workarounds. Gotta love those " we are using a completely wireless system here." Geez... no wonder the copier keeps losing connectivity, with your 20+ devices and your $25.00 wifi router you bought on Shamazon. But, I see all that stupidity and cheapness as job security, keep 'em coming $$$$$$$.
Thanks: 
Likes: 
Reply With Quote
Bookmarks