Archive - Dec 2008

Date
  • All
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31

December 16th

SLP Services , your DA and Netware vs Linux Implementation.

Often I get questions on SLP, what it exactly does and how to implement it.

To answer the first question. SLP stands for ' Service Location Protocol '.

What it does is already in it's name: It's a service running on one or more systems, that hands out a list of services to your clients specifying what services can be found on your network - instantly, without the need to have the clients ' go out and look '.

It can loosely be compared to DNS, which also helps to centrally resolve. With DNS you can resolve system names and certain services (the mail MX for example) to ip addresses and visa versa.
SLP on the other hand, is specific to making it easy for your networked clients to find out where a service is running they are looking for (e.g. location of printer services, timeserver, authentication sources like eDirectory, etc). The service list is built up dynamically and has more detail.

December 5th

DSfW ( Domain Services for Windows ) - aka. AD on eDirectory

As of this week, Novell has launched OES2 SP1.
See the announcement

OES2 SP1 is packed with powerful features and makes for an excellent replacement for your Netware systems.

One *very* cool feature that's included in OES2 SP1, is DSfW.

For those feeling forced to migrate to Windows, mostly because there is high demand for some form of application integration that is only available on AD... DSfW might be your ticket to getting best of both worlds!