Re: Terminal Services Issue

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 08/14/04 

Date: Sat, 14 Aug 2004 10:55:15 +0200

Hi Deljit,

Why do you use PCAnywhere? Why don't you just provide Terminal Services for
everyone? It is secure enough since it uses 128 bit encryption (just as much
as I use for my on-line banking) by default and you can even raise it up to
140 bit.
You can also use TS to connect to console just like you would with
PCAnywhere...

***************
I also use a software that replaces msgina.dll and with that disables TS.
What works for me is this. Open regedit and drill down

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Here look for REG_SZ that is called GinaDLL and the value will probably be
"awgina.dll" Double click on this REG_SZ and edit "awgina.dll" to
"msgina.dll". Close Regedit and try again...
***************

I hope this helps,

Mike

"Daljit Singh" <dsingh@spryance.com> wrote in message
news:uLAnWCcgEHA.1048@tk2msftngp13.phx.gbl...
> Hi
>
> I have Windows 2003 Server Enterprise Editon.
>
> I loaded PcAnywhere and the Remote people are also accessing that machine.
> On the same machine I have loaded Termnical Services for Internal Purpose
as
> Pcanywhere has limitations for accessing more than one user.
>
> If the Internal user wanted to access the Windows 2003 machine through the
> Remote Desktop of XP they get the error " You Cannot initiate a Remote
> Desktop Connection because the windows logon software on the remote
computer
> has been replaced by incompatible software
C:\WINDOWS\system32\awgina.dll."
>
> Can anyone please help with this so that I can access both at one time.
> Pcanywhere as well Terminal Services.
>
>
>

Relevant Pages

  • Re: lsass.exe problem when logging into terminal server.
    ... It seems that you have installed Terminal Services without licenses. ... On windows 2003 you have to enable Remote Desktop on the System ... Jeffrey Randow (Windows Networking MVP) ...
    (microsoft.public.windowsxp.work_remotely)
  • Allow logon through Terminal Services via Group Policies does not work
    ... I am trying to setup a GPO so that a specific security, say My Remote ... are allowed to logon to any computer on a Windows 2003 domain ... I have created the GPO and linked it from the domain and from the Domain ... Terminal Services is enabled and that Allow log on through Terminal Services ...
    (microsoft.public.windows.group_policy)
  • Re: Connecting "as if right in front of the PC"
    ... In order to use TSC to control a desktop the desktop must be running XP Pro Remote Desktop or be a ... Windows 2003/2000 Server running Terminal Services. ... An alternative, if your desktop is running some other flavor of Windows, is VNC. ...
    (microsoft.public.pocketpc.wireless)
  • Re: Remote Desktop
    ... Just want to point out, that on WIndows 2000 Server, Terminal servics needs ... It can be installed as either in Remote ... In Windows XP and Windows 2003 Server they have the Remote ... full "Terminal Services" functionality, which is the equivalent to Windows ...
    (microsoft.public.win2000.networking)
  • Re: Where do I add Remote Control
    ... Terminal Services -> Allow users to connect remotely using Terminal ... Unfortunately I was looking at a Windows XP SP2 RC machine. ... If this is set to 0, Remote Connections are allowed. ... >I have changed the group policy a long time ago to what I ...
    (microsoft.public.windows.group_policy)