Kicking a Cash Drawer in a Server 2003 Environment / Net Use
Posted on 2006-04-25
I'm trying to kick a cash drawer in a server 2003 environment with remote clients (XP Pro). Here's my configuration:
Cash drawer is attached to a host PC as COM4 (Generic/Text Only driver - shared out). It's remapped to LPT2. S/W is installed on a File Server running Server 2003. It's set to kick the cash drawer on the host PC on LPT2. So far so good. The s/w can kick the drawer on the host pc.
I need to (per the s/w developer) map the remote PCs' LPT2 to the host PC, which I do by issuing a "net use LPT2: \\pcname\printershare /Persistent:yes" command.
The cash drawer is kicked by sending a Ctrl-G command. At a command prompt I issue Echo [ctrl-g]>lpt2 and nothing happens. When monitoring the print queue on the host PC I see the "print job" come in from the remote PC, but it fails and I have to cancel it.
I've tried setting the print properties on the host pc's Generic print driver to print directly to the printer (no spooling). This is when I get an Access Denied on the remote PC when I issue kick drawer command. I do not get prompted for a username/password. All users are part of a single domain. I think I'm failing in one of two areas but am not sure:
1) All of these user accounts have "user" privileges. I'm not sure that I can map a local printer port (LPT1) to a remote PC unless the user has admin rights. This is what prompted me to use LPT2 and not LPT1 (even though there is no local printer attached to LPT1). If this is the case then how do I get around it?
2) I have granted full rights to the users who I want to access the shared printer on the host. This had no effect. Just for testing, I made the host pc and one remote clients administrators (not a live environment yet) to see if I could get past the access denied - no change. Is this a local policy issue on the host pc? This wouldn't make sense to me since local policy is overridden by domain policy.