Re: HP OfficeJet 6210/7210/PSC 750 printers & Windows Server 2003 w/Terminal Services

Daniel wrote:

Greetings,

I'm trying to help a client setup a Windows Server 2003 platform to
host their application to support their furniture stores. One store has
a HP OfficeJet 6210, the other has an OfficeJet 7210 printer. I am
attempting to setup support for each store so they can use Terminal
Services/Remote Desktop into the server to use their application, yet
still have the ability to print to their local HP OfficeJet printers.
I'm finding out that Windows Server 2003 Terminal Services is not
picking up their printers when logging into via Remote Desktop, and my
attempts to add the appropriate drivers on the server have been less
than successful.

Based on my reasearch on the internet, it appears that HP does not
produce drivers for "Server" based platforms for consumer level inkjet
printers (Nevermind the "Office" part of the "OfficeJet" name). The
store with the OfficeJet 7210 is running Windows XP Professional and
the store with the OfficeJet 6210 is running Windows XP Home. Their
respective pritners are installed locally and work just fine. How do I
get these HP printers to cooperate with Terminal Services under Windows
Server 2003?

The client is also wanting to be able to access their application from
home as well, and they have an DeskJet 450 & PSC 750 All-in-one
printer.

Any suggestions would be appreciated.

Thank you
Daniel


If I understand correctly, you are running the application on the server
that is remote from the user and want to use the local printers. Since you
are using Remote Desktop the printers need to be visible to the Windows
2003 box.

I assume these are all on the same network. Is this correct? If so, I see
two possibilities.

1) Share out the printers from the local PCs and install them as remote
printers as seen by the 2003 PC.

2) Buy a JetDirect print server for the 6210 and put the printers on the
network. (7210 has networking built in.) (You may not have the full
functionality with the 6210 on the network.) This way, both printers may be
seen by the 2003 Server.


Refer to this link.
http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&cc=us&dlc=en&product=391153&lang=en&docname=bpu04830

Hope this helps.

craigm



http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&cc=us&dlc=en&product=391153&lang=en&docname=bpu04830
.

Relevant Pages

  • Re: Network printing - HowTo?
    ... Microsoft Windows Debugger Version 5.2.3790.3959 ... Please check your debugger configuration and/or network access. ... Guess I'm wondering if sharing my network printers off of a server is ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Multiple issues (Server & Desktop) since last Windows Updates
    ... and I am still fighting problems since the reboot after the updates. ... since SP1 on our main Domain controller, which is also DNS server for itself ... I have another two Windows Server 2003 Standard servers that I ... Lexmark printers printer, ...
    (microsoft.public.windows.file_system)
  • Re: Client no longer connects to printer on Server
    ... The Windows Firewall has detected an application listening for incoming ... The Security System could not establish a secured connection with the server ... I am loathe the remove the machine from the network, ... Opening the Printers and Faxes dialog both shared printers are ...
    (microsoft.public.win2000.printing)
  • Re: Ternimal Server system requirments
    ... I can imagine from coming from NT4 what experiences you have had. ... (more like just praying that tommorow the server was ... were unknown to Windows, and had to hack some weird file to make it work. ... I have had no problems with printers and I have ...
    (microsoft.public.windows.terminal_services)
  • Re: Ternimal Server system requirments
    ... (more like just praying that tommorow the server ... were unknown to Windows, and had to hack some weird file to make it work. ... and associate it with applications crashing, ... I have had no problems with printers and I ...
    (microsoft.public.windows.terminal_services)