Anonymous_User Absent Member.
Absent Member.
899 views

Novell client on terminal server using remote desktop ipvirtualization


Is the Novell client compatible on a terminal server using remote desktop ip
virtualization ?
I was able to is ip virtualization but eDirectory still shows the session
using the server IP address instead of virtual address.

i Would like to be able to use FSSO ( fortigate ) with eDirectory in a rdp
session without any login.

Thank You
Denis Lauzon


Labels (1)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Novell client on terminal server using remote desktop ip

Denis,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.novell.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
Anonymous_User Absent Member.
Absent Member.

=?WINDOWS-1252?Q?R=E9p.=20:=20Novell=20client=20on=20terminal=20s?==?WINDOWS-1252?Q?erver=20using=20remote=20desktop=20ipvirtualization?=

Any help about ip virtualization and eDirectory session ip address ?

Thank You
DenisL


0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

=?UTF-8?Q?Re:_R=c3=a9p._:_Novell_client_on_terminal_server_using_re?==?UTF-8?Q?mote_desktop_ipvirtualization?=

I believe the Novell Client conneccts to eDirectory using whatever routes
its system has defined to reach that server most-directly, and the server
only knows the source IP of that connection. If your goal is to have the
Novell Client use another IP address so that the server sees it coming
from another IP address, you probably need to get your host system (of the
client) to have outgoing packets use that other IP address as their source.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: =?WINDOWS-1252?Q?R=E9p.=20:=20Novell=20client=20on=20terminal?==?WINDOWS-1252?Q?=20server=20using=20remote=20desktop=20ipvirtualization?=

i think, that this is what ip virtualization if supposed to do .
When i open the web browser, my fortigate firewall sees the request from
deprecated address ( 192.168.5.60 ) witch is good, but why is the Novell
client not doing the same thing ?

Thank You
DenisL

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

=?UTF-8?Q?Re:_R=c3=a9p._:_Novell_client_on_terminal_server_using_re?==?UTF-8?Q?mote_desktop_ipvirtualization?=

On 03/21/2016 11:35 AM, Denis Lauzon wrote:
> i think, that this is what ip virtualization if supposed to do .
> When i open the web browser, my fortigate firewall sees the request from
> deprecated address ( 192.168.5.60 ) witch is good, but why is the Novell


I have no idea what "deprecated address" means.

> client not doing the same thing ?


What do your system routes look like? What is the IP address of your
fortigate-whatever vs. the NCP (eDirectory/OES) server? Are they the
same, or on the same network? If not, different routes could apply.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: Rép. : Novell client on terminal server using remote desktop ipvirtualization

"Denis Lauzon" <NoReply@noreply.com> wrote:

> i think, that this is what ip virtualization if supposed to do .
> When i open the web browser, my fortigate firewall sees the request from
> deprecated address ( 192.168.5.60 ) witch is good, but why is the Novell
> client not doing the same thing ?


For what it's worth, what I can recall from investigating the IP
virtualization a couple years ago is that the implementation was
entirely in user-mode Winsock code. Meaning yes, any application
you're running from your desktop -- web browser, FTP client, instant
message agent, etc. -- would all use the virtualized address.
User-mode applications running on the desktop appear to be the only
target of the IP address virtualization, by design.

One such reference in the "Windows 7 / Windows Server 2008 R2: Remote
Desktop IP Virtualization":
https://blogs.technet.microsoft.com/askperf/2009/10/18/windows-7-windows-server-2008-r2-remote-desktop-ip-virtualization/

"User mode applications using Winsock will be able to get Virtual IP’s
– the application itself does not need to be aware of RD IP
Virtualization or need to be changed in any way. However, there are
some caveats – services in Session 0 will not be virtualized, nor will
applications and services running inside the a remote administrator
session. In addition, applications that use named pipes or any other
mechanism besides sockets will not be virtualized."

Kernel-mode drivers -- which like Windows services, are also in
session 0 in addition to using kernel-mode APIs instead of user-mode
Winsock APIs -- are not being intercepted or presented with the
virtual IP address. They continue to only see and use notification of
the "real" network addresses bound on the machine.

This is what we confirmed with the Novell Client; that when IP
virtualization was being successfully used by user-mode Winsock
applications, the kernel-mode drivers were not receiving any
notification or access to those addresses in kernel mode.

I haven't looked for quite some time, but I expect you should see the
same for Microsoft's CIFS (MRxSMB.SYS) as well. Since those
connections -- even if not established by the kernel-mode MRxSMB
directly -- still would be established by the LanmanWorkstation
service running in session 0, and should be using the "real" IP
address just as Novell Client ends up doing.

Alan Adams
Client for Open Enterprise Server
Micro Focus
alan.adams@microfocus.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: =?WINDOWS-1252?Q?R=E9p.=20:=20Novell=20client=20on=20terminal?==?WINDOWS-1252?Q?=20server=20using=20remote=20desktop=20ipvirtualization?=

So ip virtualization will not do the work for me.
That is too bad, i thought i found a way to have single sign on for rdp
session working with my Fortigate firewall like for a standard workstation
with Novell client.

Thank You very much for your response.
Denis Lauzon

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.