The protocol that ILS servers use is LDAP and that is
public.
However - NetMeeting uses some custom dynamic
attributes - i.e. additional fields in the LDAP
packets that are sent to the server. So if you'll
have to figure out what those are and how they work
before you're going to be able to create a compatible
server.
If you're developing a client software - one easy
thing to do might be to check out the NetMeeting SDK
and their ILS sample app.
Ciril Thomas
--- David Vydra <[EMAIL PROTECTED]> wrote:
>
> I need a directory server similar to ILS for the
> custom software I am
> writing in Java. Is ILS protocol public?
> Are there other public directories I could use?
> Any help would be appreciated.
>
> Thanks,
>
> David
>
> At 06:43 AM 9/24/99 -0700, you wrote:
> >
> >Dave,
> >Thanks. It worked like a charm.
> >Paul
> >
> >--- Dave Auger <[EMAIL PROTECTED]>
> >wrote:
> >>
> >> It is not quite intuitive but the following did
> work
> >> for me.
> >>
> >> Regards
> >> Dave
> >>
> >>
> >> The following is taken from the NetMeeting
> Resource
> >> Kit: technical
> >> information for organizations documentation in
> >> CHAPTER 3 Directory Servers
> >> located at:
> >> http://www.microsoft.com/netmeeting/reskit/
> >>
> >> Adding ILS Support for NetMeeting 2.1 and Future
> >> NetMeeting Versions
> >> You must add settings for version attributes in
> >> order to support NetMeeting
> >> 2.1 and future NetMeeting versions.
> >>
> >> To add NetMeeting version attribute support
> >>
> >> 1) Click Start, point to Programs, point to
> >> Microsoft Site Server, point to
> >> Administration, and then click Site Server
> Service
> >> Admin (MMC).
> >> 2) Right-click Membership Directory Manager, and
> >> then click Properties.
> >> 3) Type 389 for the Port, type your server name
> for
> >> the Host name, and then
> >> click
> >> OK.
> >> 4) Click Logon using, type your administrator
> name
> >> for the User name, type
> >> the
> >> LDAP service Password, and then click OK.
> >> 5) Click the plus sign beside Membership
> Directory
> >> Manager to expand that
> >> section.
> >> 6) Click the plus sign beside ou=Admin to expand
> >> that section.
> >> 7) Right-click cn=Schema, point to New, and then
> >> click Attribute to start
> >> the New
> >> Attribute Wizard.
> >> 8) On the Welcome screen, click Next.
> >> 9) To define the new attribute, type ilsA26279966
> >> for the Name, type
> >> ils-attrib5
> >> for the Display Name and for the Description, and
> >> then click Next. All
> >> entries
> >> are case-sensitive.
> >> 10) Follow the instructions on the remaining
> wizard
> >> screens, accepting the
> >> default settings for the attribute syntax and
> string
> >> syntax constraints.
> >> 11) Click cn=Schema.
> >> 12) In the right window, right-click
> >> cn=rtApplicationUser, and then click
> >> Properties.
> >> 13) On the Class Attributes tab, click Add,
> select
> >> ils-attrib5, and then
> >> click
> >> OK.
> >> 14) Verify that ils-attrib5 has been added to the
> >> Class Attributes list, and
> >> then
> >> click OK.
> >> 15) In the right window, right-click cn=rtPerson,
> >> and then click Properties.
> >> 16) Repeat steps 13 and 14 for cn=rtPerson.
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Eric Baber [mailto:[EMAIL PROTECTED]]
> >> Sent: 22 September 1999 18:27
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: [NetMeeting] Using MS Site Server
> for
> >> ILS
> >>
> >>
> >>
> >> Hi Paul,
> >>
> >> > It seems that Site Server replaces ILS with
> its
> >> LDAP
> >> > implementation. The MS site states that ILS is
> no
> >> > longer supported, and to use Site Server.
> >>
> >> Aha, ok... we use the ILS and I don't really know
> >> very much about the LDAP
> >> implementation.
> >>
> >> > I just can't seem to get a client to be able
> to
> >> talk to find the
> >> directory (communicate). >You are saying that a
> >> simple hostname or IP
> >> address will due?
> >>
> >> Yes, it used to. For example, our ILS is on
> >> 195.224.182.226 . If you enter
> >> that into the directory field you should get our
> >> directory - try that, and
> >> give me a ring when you see me there if you like.
> >> And/or e-mail me the IP
> >> address of your server and I'll see if I can find
> >> it.
> >>
> >> > Does NM client expect to talk to the directory
> on
> >> a particular IP port
> >> number?
> >>
> >> Probably, although I've never had to specify one,
> so
> >> I assume there's a
> >> default port number built in which it tries to
> use.
> >>
> >> Eric
> >>
> >>
>
>-----------------------------------------------------------------------
> >> http://www.meetingbywire.com/Mailinglist.htm for
> >> unsubscribe information
> >>
>
>-----------------------------------------------------------------------
> >>
> >>
> >>
>
>-----------------------------------------------------------------------
> >> http://www.meetingbywire.com/Mailinglist.htm for
> >> unsubscribe information
> >>
>
>-----------------------------------------------------------------------
> >>
> >>
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Bid and sell for free at http://auctions.yahoo.com
>
>-----------------------------------------------------------------------
> >http://www.meetingbywire.com/Mailinglist.htm for
> unsubscribe information
>
>-----------------------------------------------------------------------
> >
> >
> >
>
-----------------------------------------------------------------------
> http://www.meetingbywire.com/Mailinglist.htm for
> unsubscribe information
>
-----------------------------------------------------------------------
>
>
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------
