problem with remote desktop - LOGONREM.DLL error (not the usual question)

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

I generally remote desktop from work into my home computer. Recently this
stopped working and I started receiving an error about
LOGONREM.DLL not supporting remote desktop. I researched this and read
about how some applications replace MSGINA.DLL, I'm not running any
applications mentioned. The only thing I can think of is that my Cisco VPN
client integrates with the XP logon process so you can connect to the VPN
before logging into windows. I searched Cisco's website about this and it
said that it's not compatible with LOGONREM.DLL, so I guess they've seen
this before too. I searched my machine for LOGONREM.DLL (obviously it
should be in %systemroot%\system32, but it's not, nor is in anywhere else on
the machine.

So, I check the registry and see ....Winlogon\GinaDll = logonrem.dll
(there is also an entry named GinaDll.OLD pointing to logonrem.dll as well).
I don't understand how that can be possible and the machine even boots if
this file doesn't exist anywhere. I have no idea how or why the GINA was
changed. At least if I could find this file, I could check properties to
see who wrote it. I'd hate to change this entry back to msgina.dll and find
myself unable to boot because something else somewhere is messed up. Any
thoughts?
 
OK, this gets stranger..... I found the file on my system, but it's in the
directory of an old version of XP I no longer use. It's located in
c:\winxp\system32\logonrem.dll. I boot off of f:\windows now and
%systemroot% is clearly f:\windows. Why the hell is it looking and finding
this file? The registry just says GinaDLL = logonrem.dll, it doesnt specify
a path, and c:\winxp or winxp\system32 certainly isn't in the path (nor
should this use the path). I'm am so at a loss........ I checked the DLL
which is dated 1997 (and the system boots?!?!?) and there is no information
about it.
 
Well, I'm back in business, just pointed it back to msgina.dll and we're OK.
I'm still dumbfounded as to how this happened and how it even worked....
one
of those things I may just never understand.
 
Back
Top