Ok It's MS$ but has anyone managed to get it working with an FQDN?
Got it installed and it works fine until you try to ypbind to it!
Seems that it will only take the domaninane up to the first full stop
e.g test.here.there actually as far as NIS is concerned is just test
and that's all it will bind to!
This is really a show stopper for me at the moment as I need an FQDn
to attempt to migrate to M$ active directory with an active NIS
domain.

TIA

cheers,
Len

On 2007-03-09, Len Cuff <len.cuff@ntlworld.com> wrote:
> Ok It's MS$ but has anyone managed to get it working with an FQDN?
> Got it installed and it works fine until you try to ypbind to it!
> Seems that it will only take the domaninane up to the first full stop
> e.g test.here.there actually as far as NIS is concerned is just test
> and that's all it will bind to!
> This is really a show stopper for me at the moment as I need an FQDn
> to attempt to migrate to M$ active directory with an active NIS
> domain.

Have you looked at Quest's Vintela? Marvellous piece of software. Install,
type one command line, bingo! You Unix host is on AD.

(I leave the philosophical discussion of the horror of using some scabby
piece of M$ junk for authentication on Unix for another time.)

--
Ignorance more frequently begets confidence than does knowledge: it is those
who know little, not those who know much, who so positively assert that this
or that problem will never be solved by science.
[email me at huge {at} huge (dot) org <dot> uk]

Hey Len,

I've seen Microsoft's NIS working fine at customer sites; so - in general -
I think you should be able to get it working. But I regret, I don't know the
grizzly config details. Maybe ask in the "Services for Unix" newsgroup:
point your newsreader to server msnews.microsoft.com then find newsgroup
microsoft.public.servicesforunix.general. Some of Microsof's SFU/SUA support
guys regularly hang out there, and are quite helpful.

Also grab Microsoft's "Windows Security and Directory Services for UNIX"
kit, if you haven't already seen it:

http://www.microsoft.com/downloads/d...displaylang=en

This gives detailed step-by-step guides to several Windows-Unix different
scenarios. It's useful ... and free :-)

FWIW, Unix-Active Directory Integration is much better in Windows 2003 R2,
which puts Unix-friendly RFC 2307 extensions right into the base Active
Directory schema.

If you want an easy-to-configure solution, look at Quest's Vintella, or
Centrify's DirectControl. These products automate a lot of the configuration
which you need to perform manually, when using the bare Microsoft bits.
These are both good products; but of course, you need to pay for them.

Under the April 2004 settlement, Sun and Microsoft are supposed to be
buddies, not enemies :-). But sometimes it's hard to see evidence, except up
at the web services layer, where they co-operate on some WS-* standards.

Hope it helps a bit,
Andrew