Connect workgroup computers to a domain printer

[ReverentCreature]

I have a set of workgroup computers that I am not allowed to connect to a domain. On the domain controller I have a IP connected ethernet printer which is not wireless compatible but is mapped to all the domain clients. I can browse to type in a password and connect this printer to the workgroup clients but it does not stay after reboot. Please can you advise me what I need to do to lift the security to enable this to work. Thanks

[MatthewL]

Why don't you just install it locally on each PC pointing the port at the IP address like you do on the server?

[ADMaster]

I have a group of computers in this situation too. I don't want to put them on direct IP because that would bypass papercut.

I mapped a drive letter to a share on the print server, ticked the boxes to reconnect, remember password and use alternate credentials.

In testing I found a reboot off network would cause the printer to fail, a double click of the mapped drive reconnected everything.

In practice I have only had to walk a few users through clicking on the network drive to get printing working.

I explained to the users from the start, if printing doesn't work make sure you can open this drive.

 

This has worked reasonably well in my opinion, although some users complain because they don't need to do this at other sites. I think that complaint is directed more at papercut then the drive though.

[MatthewL]

Have you tried the new mobility print function if you are still in maintenance? There is a windows installer which would be ideal for this and it will prompt per print job for them to put in their AD credentials. Let me know can talk you through it if you are up to date.

[ADMaster]

I don't want to derail the thread too much, that was just my background for needing to connect printers in this way. However I did just update to 17 so may have to look into that for next school year.

[ReverentCreature]

Why don't you just install it locally on each PC pointing the port at the IP address like you do on the server?

 

Hi Matt, I don't know why I didn't think of that!!! I'll give it a go! Windows found its IP address as a web service direct to the printer but it didn't seem to like installing that.

[MatthewL]

Don't use WSD just add the printer as a local printer and in port option create a TCP/IP port. I always disable WSD on devices 1 to stop them been detected but to save issues down the line i.e. if I replace it I can keep the same IP and often driver depending on printer type.