Hi. Can anyone help me with this issue I have been battling with for a few days now.
Setup
Site 1 and 2 on the same domain. All server are running Windows Server 2016 Standard
Site 1 =
Server 1 (DC / 192.168.15.220) - New build
Server 2 (Backup / 192.168.15.221) - New build
HP LaserJet Pro (192.168.15.222)
Printer is connected to DC and shared. As a test I can confirm that connecting the Shared HP Printer on Server 2 is successful.
Printer is deployed via GP to users on site 1 - Successfully.
Site 2 = connected via Site-to-Site VPN
Server 3 (DC / 192.168.16.220)
Server 4 (Remote Desktop / 192.168.16.225) - New Build
When connecting Server 3 to the shared printer -
When connecting Server
4to the shared printer - Prompts "No Driver Found" click OK prompts "Connect to Printer, Windows cannot connect tothe printer. Access is denied"
If I then try to create a new printer using the printers IP address on Server 4 - It takes sometime connecting to the printer, followed by a request to install the printer driver (I have downloaded the driver only from HP), once selected the printer drive shows the correct model. This still looks good as it now asks for me to provide a printer name. Once I click next an error appears saying "Printer driver was not installed, Element not found - Frustrating.
I can now go back and just as a test I select any driver which Microsoft has listed as available and I still get the "Element not found" error. It did evenually allow me to selecta generic driver which I then tried to change after install but again his and "Element not found" warning.
Finally anyone from Site 1 who has the HP Shared Printer mapped and connects to the RDP server at Site 2 the printer will appear as a redirected printer without any isses. The GPO for the deployed printer must fail in the background as it hits the errors mentioned above.
I cannot seem to figure it out and I am unable to explain why the printer will successfully connect to Server 3 when I try.
Does anyone have any ideas? Any help or guidence would be greatly appreciated.
Many thanks, Dan