S
S
Sergey2015-06-16 12:49:56
Windows
Sergey, 2015-06-16 12:49:56

How to beat print brakes?

We have a domain based on Windows 2012. Print server - windows 2008
A bunch of motley users. In the bulk of Windows 7 and MAC OS
Printers, servers, users - all in different VLANs. Access to printers only through a print server.
Problem: Printers take a long time to print.
Also, if you go to the printer properties, you can wait 2 minutes until they open.
I watched Wireshark what was going on and saw this:

531049	1627.773421000	192.168.100.11	192.168.90.222	SMB2	466	Create Request File: x64\3\Xerox\Product Data\Public\DCPs\x2UNIVI6\V5.0\886M\de\w_ink_low.htm
531050	1627.773755000	192.168.90.222	192.168.100.11	SMB2	386	Create Response File: x64\3\Xerox\Product Data\Public\DCPs\x2UNIVI6\V5.0\886M\de\w_ink_low.htm

When you close the properties, then this:
560582	1663.616699000	192.168.100.11	192.168.90.222	SMB2	146	Close Request File: x64\3\Xerox\Product Data\Public\DCPs\x2UNIVI6\V5.0\MTAI\es\w_ink_low.htm

Apparently, when opening the properties, some files are trying to be loaded from the print server. There are many of these files, and they are not on the print server!
The question is, what is it? This is fine? How to get rid of it?
Just got the brakes.
PS. Interestingly. The sphere from which the files are downloaded is not visible on the server itself. But you can enter it from a user's computer. And when you open the properties of the printer, about 20 thousand files are downloaded from this balls. And every time.
I suspect that most likely this is some kind of archive that is rummaged through the spooler.
PS2. What has been done:
1. I tried to disable "two-way data exchange" - it did not help.
2. Connected to the printer network. Checked the availability of DNS - it works
3. Opened the access of the printer network to the Internet for verification - it did not help
4. I tried to print from the print server - everything works with a bang!
5. I tried to connect the printers to the user's computer "directly" - it works. But it is necessary through a print server. So not an option.
6. I deleted the printer on the user's computer, cleaned the %windir%\system32\spool\PRINTERS folder, then set up the printer again - everything worked.
It remains to understand why, and what caused the massive glitch. Reinstalling printers on all computers is not an option. Since half of the computers are MACs. And I have no idea what to clean out there.

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question