I don't know the specifics of the Cisco software you are using, but I
am familiar with this general class of problems. It could be
redescribed as follows:
A service running in session 0 needs to pop UI. Rather than pop UI in
the appropriate session, it pops the UI in session 0.
You need to contact Cisco and explain what you are seeing. On their
end, the Cisco service needs to communicate with some process running
the in the proper user session to pop UI.
On Wed, 14 Jan 2004 11:10:58 -0800, "CLsuppt"
<(E-Mail Removed)> wrote:
>Scenario:
>
>Multiple users access a Win2k terminal server to VPN out
>to a client site. Must use terminal services for easier
>management of connection (As oppossed to allowing each
>individual user VPN from their desktop).
>
>Currently using Win2k terminal services and Cisco Client
>4.02a.
>
>Problem.
>
>After you terminal in to the server and attempt to run
>the client. THe cisco secuirty login prompt appears on
>the physical server desktop as oppose to the terminal
>client. why?
>
>
>If i use a windows xp box with remote services
>enabled...it works fine. But without multiple sessions it
>limits its use.
>
>So how come it works via RDP in one scenario and not the
>other. Is citrix a possible solution to this (i have no
>experiences with citrix).
>
>thanks.
This posting is provided "AS IS" with no warranties, and confers no rights
|