RE: OfficeJet 7410 All-in-One & 2003 Terminal Services - HELP

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Greetings Eduardo.

As old as this thread is you would think the problem was resolved. Actually,
I never received a clear cut answer nor was I able to continue
troubleshooting. The person I was trying to resolve this for lost contact
with us. A few months later (ie. today) I just received a phone call with the
same problem. So, I'm back to square one trying to troubleshoot the problem.

The only logical conclusion I come to is A) I will not recommend a TServices
user purchase an HP All in One, or B) MS needs to provide better
documentation to resolve this problem.


"Eduardo Pietri" wrote:

> Eugenio,
>
> Were you able to fix this problem? I had a similar problem, the difference
> was that the local printer is listed in the local machine, but printing to it
> doesn't do a thing.
>
> Any ideas?
>
> Eduardo
>
> "eugenefl" wrote:
>
> > Greetings all.
> >
> > SPECIFICATIONS: (host) Windows Server 2003 w/ Terminal Services, (client)
> > WindowsXP Pro SP2, (printer) HP OfficeJet 7410 All in One
> >
> > SCENARIO: A Remote Desktop user with WinXP Pro SP2 with a locally installed
> > (USB) HP OfficeJet 7410 cannot print to his 7410 while connected to our
> > Windows Server 2003 via Terminal Services.
> >
> > PROBLEM: Although the printer is installed correctly and can be printed to
> > locally, when connected via Remote Desktop / TS the printer does not appear
> > in his remote session. I was able to duplicate the problem and correct it on
> > my end but his computer is persistent in not displaying the printer while
> > remotely connected.
> >
> > TROUBLESHOOTING: Connected and installed the OfficeJet 7410 directly to the
> > Terminal Server and confirmed a correct driver install; simulated problem by
> > connecting the 7410 to a laptop outside of our network and was able to
> > correctly display the 7410 in an RDC session - success; Problem still
> > persists on the user's end; Verified user had "Local Resources > Printers"
> > checked; Verified user was able to print locally.
> >
> > Thank you in advance for any assistance you can provide. If I have missed
> > anything please let me know.
> >
> > Eugenio
.

Relevant Pages

  • RE: OfficeJet 7410 All-in-One & 2003 Terminal Services - HELP
    ... was that the local printer is listed in the local machine, ... A Remote Desktop user with WinXP Pro SP2 with a locally installed ... > Terminal Server and confirmed a correct driver install; ... > connecting the 7410 to a laptop outside of our network and was able to ...
    (microsoft.public.windowsxp.work_remotely)
  • OfficeJet 7410 All-in-One & 2003 Terminal Services - HELP
    ... A Remote Desktop user with WinXP Pro SP2 with a locally installed ... Connected and installed the OfficeJet 7410 directly to the ... Terminal Server and confirmed a correct driver install; ... connecting the 7410 to a laptop outside of our network and was able to ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Internal and external IP resolution
    ... The problem is that if the user for any reason looks for MAILSERVER.OURDOMAIN.COM while off the network "before" connecting internally the name will naturally be resolved by an external DNS from the ISP and will naturally resolve it to the external IP. ... If they boot up and correctly connect to the VPN before firing up Outlook or addressing MAILSERVER.OURDOMAIN.COM, the IP will be resolved properly by our internal DNS to 192.x.x.x ... As far as RPC over HTTPS I was under the assuption that I had to have the Exchange Server as the Global Catalog. ...
    (microsoft.public.windows.server.networking)
  • RE: SBS 2k3 SP1 : Cannot install Sharepoint Services
    ... I know that you cannot WSS on SBS 2003 SP1 server. ... After finish the installation, ... <Contacts public folder. ... <I found a lot of solutions but the resolve doesn't work on my server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Update Failures KB834707, KB885884
    ... Please try following the steps listed below to resolve the issue you are ... the Windows Update site is unable to modify ... > George, after you have run both the commands, ... > Update site and see if you can install the updates. ...
    (microsoft.public.windowsxp.general)