Re: RDPCLIP.exe Stalled
- From: "Ralph Howarth" <RalphHowarth@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 8 Apr 2005 13:47:02 -0700
I did setup the auditing like you suggested.
I did compare and "open up" many of the registry key values; but your list
looks more comprehensive than my gross comparison. You mentioned a registry
tool that is better for comparing. What tool is that? Is it a Sysinternals
related tool? I can go there and look.
Thank you for the *.inf file tip. I will try that out. I have sniffed out
*.inf files before and I believe they are ASCII and not binary, if I am not
mistaken.
I am a little bit shy about doing a repair on Win2K Server and then
rebuilding the service packs because I did not install these servers and
there is likely something that I would have to shake down once built back up
to SP4. These servers are also the RDCs running DHCP, DNS, WINS, and some
other stuff like, one is the master browser or something like that. I'm just
concerned that fixing one problem by the repair method most likely will
create another one. I will do that as a last resort. Actually, the last
resort strategy is to build servers from scratch on Windows Server 2003 and
migrate over. These servers are just obtuse because they were upgraded from
NT 4.0 Server and this incident is one of many incidents where things that
are configured to work just don't work (according to the "book"). An example
is that the current server that now is working TS, it disregards the Default
Domain Controller Policy and Default Domain Policy. It enforces its own SAM
on clients that login...the SAM before the server was promoted as an RDC.
Since it is an RDC, I am unable to edit the local SAM. And there are several
other incidents like that. So it seems like it does need a repair windows
performed along with the HP 1200 Series driver that does work on other
servers but not this one.
What threw me off was HP 1200 Series driver also choking the second RDC.
The second RDC simply has not had many issues and seeing the same driver
choke printer redirection led me to believe the driver was not compatible. I
did not try the notepad trick on the second RDC; but I did try it on a member
server where TS redirection persisted to work fine, and it did not come up
either on that third server, so that is weird. And I do not think that
server was a NT 4.0 Server upgraded to 2000; but I could be mistaken.
"Ralph Howarth" wrote:
> Update:
>
> Performed uninstall and reinstall of Terminal Services on the two problem
> servers.
>
> One is now back up with all printer and clipboard redirection capabilities
> and RDPCLIP.exe is now running as a process. The other is still now working
> so I am doing an uninstall of Terminal Services a third time on that one and
> hopefully that one will heal up OK.
>
> One hold-up. The notepad entry is still in the StartupPrograms value but
> Notepad does not open on logon...don't know why not there. Perhaps the
> Terminal Services installation is still partially broke...just not as broke
> as beforehand.
> "TP" wrote:
>
> > Is this the only thing not working properly after
> > your uninstall/reinstall?
> >
> > Some things below for you to check, hopefully
> > they will help.
> >
> > What happens if you run rdpclip.exe manually? If
> > things are normal it should start up and clipboard
> > mapping should start working.
> >
> > What happens if you add notepad to the startupprograms?
> >
> > Temporarily change it to rdpclip,notepad
> >
> > The results should be that notepad starts up automatically
> > when you logon.
> >
> > Is the fDisableClip set to 0 under
> >
> > HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp
> >
> > If fDisableClip is set to 1 rdpclip.exe will terminate, because
> > clipboard mapping is disabled.
> >
> > Check that rdpclip is still listed under Addins
> >
> > HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Addins\Clip Redirector
> >
> > Name REG_SZ RDPClip
> > Type REG_DWORD 0x00000003
> >
> > Thanks.
> >
> > -TP
> >
> > "Ralph Howarth" <RalphHowarth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2EC962C1-4781-41C7-B1C1-6BE644C2816F@xxxxxxxxxxxxxxxx
> > > Recently installed the HP 1200 Series Laserjet driver on a pair of Windows
> > > 2000 Server SP4 machines. Immediately all printer redirection stopped...and
> > > then later realized clipboard redirection was dead too. Uninstalled the
> > > offending drivers from the Print Server Properties. A System Event persisted
> > > even afterwards stating printer redirection had an internal error and failed.
> > > Research on MSDN indicated to uninstall and reinstall terminal services on
> > > the servers via Add / Remove Windows Components. Performed uninstall and
> > > server rebooted. Now reinstalled terminal services.
> > >
> > > RDPCLIP.exe now does not load even though it exists in the system32 folder
> > > and exists in the registry under the rdpwd key for StartupPrograms. This
> > > condition is incidental for both the servers taht the offending printer
> > > driver was once installed.
> > >
> > > Any suggestions?
> >
> >
> >
.
- References:
- RDPCLIP.exe Stalled
- From: Ralph Howarth
- Re: RDPCLIP.exe Stalled
- From: TP
- Re: RDPCLIP.exe Stalled
- From: Ralph Howarth
- RDPCLIP.exe Stalled
- Prev by Date: Re: TS System C Drive displayed when using Citrix Published application
- Next by Date: Re: Setting user TEMP/TMP env.variables?
- Previous by thread: Re: RDPCLIP.exe Stalled
- Next by thread: Re: RDPCLIP.exe Stalled
- Index(es):
Relevant Pages
|
