mattlicentia
IS-IT--Management
Hi,
we have a quatum snap server 4100 with lattest upgrade etc. The probelm is that because of how ctrix metaframe xp handles ip address we cannot not set up any security on the snap server as the user just gets told ' access denied'. Quantum say that they do not support metaframe (only after 4k) their email is copied below help please!
Metaframe Spec:
Windows 2000 server sp2 latest hotfixes
Metaframe XPE
matt
Dear Sir,
Terminal Server/Citrix Metaframe is not supported. Snap only supports a one user,one workstation connection. We do not support multiplexed users from one workstation(server). The identity of each user session that establishes a new connection to the Snap from a single workstation overrides the identity of existing connections in simultaneous sessions on the same workstation. In other words, if user A connects to the Snap from the workstation, then user B also connects to the Snap from the same workstation in another session, user A will suddenly have the identity and rights of user B. Therefore it can appear that user A no longer has access, which he doesn't really. There is currently no recommended workaround. Some customers have reported limited success by mapping a separate ip directly. However, this defeats the purpose of terminal server. The connection goes "around" the terminal server/Citrix Metaframe to gain access directly. The change to the registry for NT4 SP4 was to correct a problem with the terminal server software itself. It does not change how it interoperates with the Snap Server.
we have a quatum snap server 4100 with lattest upgrade etc. The probelm is that because of how ctrix metaframe xp handles ip address we cannot not set up any security on the snap server as the user just gets told ' access denied'. Quantum say that they do not support metaframe (only after 4k) their email is copied below help please!
Metaframe Spec:
Windows 2000 server sp2 latest hotfixes
Metaframe XPE
matt
Dear Sir,
Terminal Server/Citrix Metaframe is not supported. Snap only supports a one user,one workstation connection. We do not support multiplexed users from one workstation(server). The identity of each user session that establishes a new connection to the Snap from a single workstation overrides the identity of existing connections in simultaneous sessions on the same workstation. In other words, if user A connects to the Snap from the workstation, then user B also connects to the Snap from the same workstation in another session, user A will suddenly have the identity and rights of user B. Therefore it can appear that user A no longer has access, which he doesn't really. There is currently no recommended workaround. Some customers have reported limited success by mapping a separate ip directly. However, this defeats the purpose of terminal server. The connection goes "around" the terminal server/Citrix Metaframe to gain access directly. The change to the registry for NT4 SP4 was to correct a problem with the terminal server software itself. It does not change how it interoperates with the Snap Server.