TS Printing Ports

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Alright, this is the situation
We have a terminal server running on our network, with a handful (10 maybe at the most) who access it. One of them works remotely from home and has a HP 3330 Laserjet. When this user had a 6110 officejet, it worked beautifully. Windows was able to recgonize it after puting in the "net use" command in a small .cmd file in her startup folder. So, when she would connect to the terminal server, it would recognize her printer, and go along it's merry way.

Now, after switching printers, what I have found is that 1- it is not recognized in terminal services, 2- because she is on a dialup connection(only thing availible), I cannot get the printer to map before her VPN connection bombs out (separate issue, working on that as well), and 3- in the error logs, normally a printer that TS doesn't recognize, there is some blurb about it on the error logs, but not with this printer, nothing coming up that it could not recognize the printer or whatever, like it does with any other printer that it does not have in the ntprint.inf file

So, did digging, found that the printer port on the local machine was not a USB port, but actually a DOT4 port. I'd seen this when we were using the other printer, but it was not selected as the printer port, the USB printer port was. One was created when the printer was installed, but not selected as the printer port

So, what I am wondering is should I maybe setup another printer on the machine (not a physical printer, one in Windows) and have it select to use the USB port, or what should I do? Any ideas/suggestions would be great, spent most of the night up working on this...

Erik Helgesta
Waukesha, WI
 
--------------------
Thread-Topic: TS Printing Ports
thread-index: AcQ+fVzCSX3BxtAHRUCA9wC+3RmYdQ==
X-WN-Post: microsoft.public.win2000.termserv.apps
From: "=?Utf-8?B?RXJpayBIZWxnZXN0YWQ=?=" <[email protected]>
Subject: TS Printing Ports
Date: Thu, 20 May 2004 08:16:02 -0700

Alright, this is the situation:
Click to expand...
We have a terminal server running on our network, with a handful (10 maybe
at the most) who access it. One of them works remotely from home and has a
HP 3330 Laserjet. When this user had a 6110 officejet, it worked
beautifully. Windows was able to recgonize it after puting in the "net
use" command in a small .cmd file in her startup folder. So, when she
would connect to the terminal server, it would recognize her printer, and
go along it's merry way.

Now, after switching printers, what I have found is that 1- it is not
recognized in terminal services, 2- because she is on a dialup
connection(only thing availible), I cannot get the printer to map before
her VPN connection bombs out (separate issue, working on that as well), and
3- in the error logs, normally a printer that TS doesn't recognize, there
is some blurb about it on the error logs, but not with this printer,
nothing coming up that it could not recognize the printer or whatever, like
it does with any other printer that it does not have in the ntprint.inf
file.

So, did digging, found that the printer port on the local machine was not a
USB port, but actually a DOT4 port. I'd seen this when we were using the
other printer, but it was not selected as the printer port, the USB printer
port was. One was created when the printer was installed, but not selected
as the printer port.

So, what I am wondering is should I maybe setup another printer on the
machine (not a physical printer, one in Windows) and have it select to use
the USB port, or what should I do? Any ideas/suggestions would be great,
spent most of the night up working on this....

Erik Helgestad
Waukesha, WI
Here is your solution....
Q302361: "Printers That Use Ports That Do Not Begin With COM, LPT, or USB
Are Not Redirected in a Remote Desktop or Terminal Services Session"
support.microsoft.com/?id=302361

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
That works. Wish I had found that earlier.
I think for now I will just use the shared printer option and connect the server to that machine for now
When the user is able to bring their PC in, I will try to do the regedit maybe then, and see what happens

Thanks
Erik Helgestad
 
Erik, here are some useful resources for printing in a Terminal Services environment

http://www.workthin.com/tsp.ht
http://www.printingsupport.co
http://hem.fyristorg.com/vera/IT

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Erik Helgestad wrote: ----

That works. Wish I had found that earlier.
I think for now I will just use the shared printer option and connect the server to that machine for now
When the user is able to bring their PC in, I will try to do the regedit maybe then, and see what happens

Thanks
Erik Helgestad
 
Back
Top