FW: samba port 135 conflict with dce service on hpux

[Kumar, Arjit (SSTO)]

Hi Andrew,

>> Is there a good reason why you can't run up a Linux VM for the AD DC?
We are working official to enable AD DC on HP-UX 11i v3 at IA-64 platforms.
We can’t stop dced service running on port 135 on hpux.
Please suggest alternatives for the same.

Regards,
Arjit Kumar

From: Arjit Gupta [mailto:arjitk.gupta at gmail.com]
Sent: Monday, January 15, 2018 12:03 PM
To: Kumar, Arjit (SSTO) <arjit.kumar at hpe.com>
Subject: Fwd: samba port 135 conflict with dce service on hpux


Arjit Kumar


---------- Forwarded message ----------
From: Andrew Bartlett <abartlet at samba.org<mailto:abartlet at samba.org>>
Date: Fri, Jan 12, 2018 at 1:50 PM
Subject: Re: samba port 135 conflict with dce service on hpux
To: Arjit Gupta <arjitk.gupta at gmail.com<mailto:arjitk.gupta at gmail.com>>
Cc: samba-technical <samba-technical at lists.samba.org<mailto:samba-technical at lists.samba.org>>


On Fri, 2018-01-12 at 09:15 +0100, Volker Lendecke via samba-technical
wrote:
> On Fri, Jan 12, 2018 at 11:51:51AM +0530, Arjit Gupta via samba-technical wrote:
> > Please suggest possible impact if we start  EPMAP (End Point Mapper)
> > service on port other then 135 or if any other solution is available.
>
> It just won't work. You must use a machine where Samba can take over
> 135. Alternatively, you could start patching Samba to register its
> services via the existing EPMAP. This might be possible, but not
> without significant code changes in Samba.

Additionally, Samba as an AD DC on HP-UX is just going to be a
snowflake: one of a kind.  Take this as a warning that this has never
been tested and is strongly advised against.

Is there a good reason why you can't run up a Linux VM for the AD DC?

Andrew Bartlett

--
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba