TS printing problems client side

  • Thread starter Thread starter John Levy
  • Start date Start date
J

John Levy

Hi,

I have a customer who is in PA on a LAN connected to the
internet via a partial T1 at 256K. They connect to their
CA office using Terminal Services on Win 98 machines and
Remote Desktop on newer XP machines. The CA office is
connected via DSL and are running a 2000 Server box (sp4)
with Terminal Services and an NT 4.0 application server
for the one necessary application.

They have consistantly had printing problems trying to get
print commands redirected to the local machines from the
server. I have read everything that I can get my hands on
relative to the problem and directed the SysAdmin in CA to
a couple of KB articles that should have helped the
problem.

The last article (302361) is one that has been referred to
before on this group and it talks about implementing a
RegEdit at the following location.

HKEY_CURRENT_USER|Software\Microsoft\Terminal Server
Client\Default\AddIns\RPDPR

The problem is that when she moves down the Registry tree
on the 2000 server there is NO entry for \Terminal Server
Client\ or anything beyond it at all.

On the WinNT server she can get to \Default\ but there is
no \Addins\RDPDR.

Excuse me but what is happening here?

Answers or suggestions anyone.

John
 
The reghack to enable redirection of all ports has to be made on
the client, not on the server.
 
Hi Vera,

Thanks for the post. Why did I assume that the edit had to made on the
server? Why did MS not point out the obvious?

Is this going to apply to XP, Win2K and 98?

They are using all of the above.

I am running a Win2K box and Remote Desktop. I went into my registry
and there is no Terminal Server folder there for me to drill down
through either.

I will be visiting my clients office this afternoon and will check
their machines then.

Thanks,

John

PS Thanks for the hit on my other post in another thread. I didn't
originate the post but am grateful that someone did.
 
answers are inline...
-----Original Message-----
Hi Vera,

Thanks for the post. Why did I assume that the edit had to made on the
server? Why did MS not point out the obvious?
Click to expand...

The article does state that this is a client fix, but the
wording is a little iffy. At the top of that
knowledgebase article there is a "feedback" option. Why
don't you give your feedback about the article and help to
improve it?
Is this going to apply to XP, Win2K and 98?
Click to expand...

Yes, it will apply to all of those.
They are using all of the above.

I am running a Win2K box and Remote Desktop. I went into my registry
and there is no Terminal Server folder there for me to drill down
through either.
Click to expand...

If that registry entry isn't there, then I could just
create it. If that doesn't fix your problem, then I would
try to reinstall the RDP client.

-M
 
Back
Top