How to properly set up a remote printer on win2008?

V

Valery2014-09-25 11:29:10

RDP

Valery, 2014-09-25 11:29:10

There are a bunch of clients that connect to the server on Windows 2008R2 64bit
Some of the clients connect remotely via VPN and the printer is connected to them locally, mostly HP M1212|1217 printers.
Standard windows tools that independently forward them via RDP do not work correctly. Windows produces hundreds of copies of these "forwarded" printers marked "redirected", it sounds like this:
HP M1212 (Redirected 10) and these redirected printers do not work.

A particularly acute problem is with remote clients who work in 1C via RDP and it is necessary that the 1C server normally catches printers remote to them.
Tried the classic way. Just add a new printer that is connected to another user.
"\\192.168.1.100\PrinterN1". We install it and ... It seems that everything is fine, but a little something happens, for example, a disconnection happened today, and remote breaks often occur and the printer gives an error 0x000002, and plus it completely refuses to install on a new one. As a result, you need to reboot the printer server ...
Network where the 1C server is located on network # 1 192.168.5.0/24.
The network where the printer is on network #2 192.168.1.0/24. The VPN client is the Zukselevsky router.
How can I configure windows tools or third-party software so that redirected printers via RDP work normally?
By the way, in win2003 there was a hundred times less hemorrhoids with printers through the RDP ...

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

N

nfire, 2014-09-25
@dtho-dtho

The first option is such drivers. It happens. You can try to install the standard PCL6 (or 5e)
The second option is to connect printers as local to the port "\\192.168.1.100\PrinterN1".

V

Valery, 2014-09-26
@dtho-dtho

Variants with a hamster (hamachi) are also considered. I, as it were, installed Hamach on the 1C server and on the client with a printer. After I connected it as a regular network printer "\\10.х.х.х \ Print", but still ... The printer falls off by the end of the day and that's it, even if you crack, it again gives out 0x000002. Rebooting the service with every sneeze is also not an option.