Jump to content
|Topic||Stats||Last action by|
|The Reality of the iPhone Line Is a Black Market Nightmare||
|Galaxy/Gainward branded gfx cards.||
|7 Days: A week of new Windows, Minecraft madness, OnePlus woes and a bit of iFun||
|XRECODE II v220.127.116.11||
Posted 22 February 2013 - 19:27
Posted 22 February 2013 - 19:44
Posted 22 February 2013 - 21:34
Yes it is going to. print jobs are huge, and they aren't compressed. a 2 meg word file could be a 100meg raw file (which is what gets sent to the printer), it depends on what they are printing. fix this issue by having local printers or by finding a way to transmit the print job compressed over the vpn to the printer network end and uncompress there.
We have done this with terminal servers being accessed over the vpn for years with the use of universal print servers like uniprint, screwdrivers, thinprint, etc. Basically you print on the terminal server, it compresses the print job to your client and it uses your client printer to expand and print the job locally. This worked great for dial up users trying to print locally when using rdp connecting to the server at the office. It saved a ton on bandwidth and kept printing quick vs waiting 30 min to print a job.
Posted 22 February 2013 - 21:53
Posted 22 February 2013 - 22:12
Posted 23 February 2013 - 22:21
I just printed out a 2.9MB pdf. Watching the spooler it was a 800+MB raw file being printed. You can easily see that if I were to print that over the internet it would take a lot of bandwidth and it would take forever to print on a slow connection.
Does he print to the printer there, is that were you are seeing this or does he print to his printer next to him and that is where you are seeing it?
If he is printing next to him through a remote desktop connection or someone is send him a job over the internet, oh yes it will take every bit of that and is absolutely no surprise to me. Just think, how many times I would have to print that to reach your total...maybe 8 copies?
The only way around that is to compress it and get it to spool locally.
Ok, if you aren't printing, how are you monitoring this on your network? Ignore the above if you are sure the end users aren't printing.
"The spoolsv.exe file is located in the folder C:\Windows\System32. In other cases, spoolsv.exe is a virus, spyware, trojan or worm!"
Could be something not nice.
Posted 01 March 2013 - 21:18
Posted 01 March 2013 - 21:47
Posted 07 May 2013 - 23:34