thin client printing

[nix45]

MetaFrame XPa FR3/SP3
Windows 2000 SP4

I'm having a problem installing printers in Windows 2000/MetaFrame XP that are directly attached to a thin client via a standard parallel port (LPT1). In WinNT TSE/MetaFrame 1.8, when you want to add a local printer, you would select Network Printer - Client - LPT1. In Windows 2000/MetaFrame XP, LPT1 isn't an option. The printer has to be installed in the operating system on the thin client in order for it to show up in the Add Printer Wizard. Is it possible to install printers in this way in Windows 2000/MFXP? I can't imagine that you would lose this simple feature in an upgraded version of the product.

Thanks,
Chris

 

[muddyjohn]

This might have been a bug in the old version, But you have to install the printer on the local pc.

 

[nix45]

Sorry, I don't understand what your saying. A bug in the old version of what? Everything worked in MF 1.8 / WinNT TSE, which is the old versions of both MetaFrame and Windows. I'm running the latest versions of MetaFrame XP (FR3/SP3) and Windows (SP4), and I can't install locally attached printers on thin client, like we used to be able to in MF 1.8.

Chris

 

[ascotta]

I think that in the MMC you need to right click on printers and go into the client printer bit. They get treated as CE devices. Sorry I don't have the CMC here at home but I am sure you will know what to do when you see it.

 

[nix45]

So I have to manually add every client printer attached to all of our thin clients? Is it possible for the client to add the printer themselves like they could back in MetaFrame 1.8 / WinNT 4.0 TSE?

Thanks,
Chris

 

[carhartd]

This is what I did I just added the printers to the network using HP jet direct cards and then I added the printer to the Citrix servers using IP and then setup security using groups so that everyone wouldn't see every printer

Hope this helps

 

[nix45]

carhartd, I think you are a little confused on what I am asking. I need for users with printers attached directly to LPT1 on their thin clients to be able to install those printers in their Citrix sessions. Back with WinNT TSE/MF 1.8, you could add a client printer by specifying LPT1. With Win2K/MFXP, it seems you can only add client printers that are installed in the clients operating system (WinXP, Win2000 Pro, etc...). With thin clients, its not always possible to install the printers in that way.

Chris

 

[macho17]

Local printer setup in a ICA Connection.

Uncheck the use printer Configuration Utility under options inside your ICA connection on the Winterm.

After installing the printer to the LPT1 port on the Winterm, follow these instructions...

1. Click on Configure tab then highlight your connection and click on Edit button. Click on Options and remove the check from the box labeled Use Printer Configuration Utility. Click on OK.

Printer setup from session.

1. Connect to the MetaFrame Server with your Winterm terminal and log in.

2. Click on Start, select Settings | Printers.

3. From the Printers dialog box, double click the Add Printer icon. Click on the Network printer server radio button. Then click the Next command button.

4. From the Shared Printers selection menu in the Connect to Printer dialog box double click on the Client icon. You will then see printer ports listed below it. Click to highlight the port that you are using, and then click on the OK command button.


Some examples below show a Winterm terminal identified with a default name (WBT008064124A4A#LPT1. If the Winterm was assigned the client/terminal name "Pinky," for example, then that port would be identified as "Pinky#LPT1:

 

[nix45]

Yeah, thats how its *supposed* to work, but doesn't in my farm for whatever reason. I have a test network and it works fine in that way on that farm, but on my production farm it fails when you try to add a printer in that way. The second you click on the Client\ClientName#\LPT1: printer in the Add Printer Wizard, it says this under Printer Information, "Error: The printer name is invalid". Its supposed to say "Ready" when it works. When you try to install it, this is the error...

"Could not connect to the printer. You either entered a printer name that was incorrect or the specified printer is no longer connected to the server. Click Help for more information."

I only get this error on my production farm, it works fine in my test farm. I actually called Citrix on this and paid the $400, but I got a Citrix tech who had to ask me how to open the CMC because the shortcut on the desktop was missing. He also couldn't figure out what server he was logged into and had to ask me. Seriously, no joke, and we're paying him $400. You should see the extremely un-professional emails (all lowercase, no periods, commas, question marks, or anything) that he sends me too. I'm waiting for him to escalate the case so we can get someone who knows what they're doing.

Chris