GW to OES2/SLES10

We are still working on upgrading to GW 7.2 on the servers. I am doing test migrations from NW 6.5 to SLEs10/OES2, and used the GW migration utility to move a GW 7.2 Postoffice and domain to the Sles10/OES2 box.
When trying to connect to this PO on the SLES10/OES2 with GW 6.5.7 client, it tells me "the version of Groupwise you are using cannot access this postoffice".
I've looked at all the TID's, tried rebuilding, recovering, validating, recopying the .dc files, etc., and it still does not work. Database version in C1 is 7 for both PO and Domain.
I thought that you could connect to GW 7.x PO with 6.5x client (we actually have many users doing this currently, actually, and it works fine)
I'm running out of ideas. Any suggestions?

Hi, Joe, thanks!
I had a suspicion about that...that **)(%&$ hotpatch has really given me a bunch of headaches!!!
I'll go find a "newer" 7.02 (the HP one) for the server and see what happens...thanks!!!
Originally Posted by Joseph Marton
On Thu, 08 May 2008 15:26:01 +0000, davy2 wrote:
> When trying to connect to this PO on the SLES10/OES2 with GW 6.5.7 client,
> it tells me "the version of Groupwise you are using cannot access this
> postoffice".
> I've looked at all the TID's, tried rebuilding, recovering, validating,
> recopying the .dc files, etc., and it still does not work. Database
> version in C1 is 7 for both PO and Domain. I thought that you could
> connect to GW 7.x PO with 6.5x client (we actually have many users doing
> this currently, actually, and it works fine)
I'm guessing the problem you're having is the wonderful GW hot patch
security fix. Here's the story.
If you are running GroupWise 7 SP2, you can use a GW 7.0 - 7.02 client, or
6.5.6 Update 1 or newer. However, you *can't* run the GW 702HP or newer
client, nor can you run the 656U2 or 656U3 client.
If your server instead is running at least GW702HP or newer (including
SP3) then any client will work.
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!
http://forums.novell.com/

Similar Messages

Help a bonehead - ZfD server modules for desktop agents?

Ok guys, I have to be honest I was really versed on ZfD but it has been a good number of years since I've really touched it. Here is what is going on, we are migrating fully to OES2 SLES10/OES11 and removing all our Netware servers over time. We are at a point where we can retire 2 of our 3 remaining Netware servers if ZfD doesn't require them. We are in the process of also going to Windows 7 on all workstations, we'll use ZCM 11 for them. Here is my question....
What does the Windows Desktop Agents rely on for user related policies? Does it connect to eDirectory directly and read the policies? In other words we have Windows XP Pro workstations running the ZFD Agents. We are only are using the user associated policies for DLU(mandatory remaining profiles) and user associated group policies. We'd like to keep these running and if memory serves they don't call any specific NLMs on the Netware servers, they just read eDirectory for their information.
Is this correct? Please be kind, my ZfD 7 knowledge is simply fading away. Thanks.
-Nyle

Thanks Craig,
I really appreciate the confirmation. That is what I had thought but you know what assuming does. We aren't using any software bundles or Workstation assigned policies only user policies so it sounds like we should be good to go.
Only one more Netware 6.5sp8 server to go, I'm kind of sad to see the end of such a reliable legacy. I hope that Novell can infect the Linux side of the house with the idea that with power, management complexity doesn't have to be the norm. 8^D
-Nyle
Originally Posted by craig_wilson
It's possible to get by without ANY server side components.
The two main server functions are the Inventory Server and Workstation
Import Service.
If you are not worried about Inventory, then the Inventory Server does
not matter.
Workstation Import Service is not required, though not having it is a
slightly larger issue. There are two main things you lose if the WS is
not imported.
#1 - You cannot assign Bundles/Policies directly to Devices, only uses.
Duh :>
#2 - The System Account will not have any File Rights for running User
Associated Bundles set to run as System Directly from a Network share.
However, you could run the bundle as Logged on User or 1st copy the
files local and then run an install as System.
On 7/6/2012 3:26 PM, nlandas wrote:
>
> Ok guys, I have to be honest I was really versed on ZfD but it has been
> a good number of years since I've really touched it. Here is what is
> going on, we are migrating fully to OES2 SLES10/OES11 and removing all
> our Netware servers over time. We are at a point where we can retire 2
> of our 3 remaining Netware servers if ZfD doesn't require them. We are
> in the process of also going to Windows 7 on all workstations, we'll use
> ZCM 11 for them. Here is my question....
>
> What does the Windows Desktop Agents rely on for user related policies?
> Does it connect to eDirectory directly and read the policies? In other
> words we have Windows XP Pro workstations running the ZFD Agents. We are
> only are using the user associated policies for DLU(mandatory remaining
> profiles) and user associated group policies. We'd like to keep these
> running and if memory serves they don't call any specific NLMs on the
> Netware servers, they just read eDirectory for their information.
>
> Is this correct? Please be kind, my ZfD 7 knowledge is simply fading
> away. Thanks.
>
> -Nyle
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

PDHPC did not answer to req. on port 4011

Hi,
I have this problem where my workstations can't boot to PXE. After aprox. 2 to 3 minutes they get an IP address from the DHCP server, but then give me:
ProxyDHCP service did not reply to request on port 4011. Here's the facts:
- Zen7 is installed on OES2 (SLES10-SP1) with no firewall running.
- DHCP and PDHCP are on different machines (DHCP is on windows) so no option 60 is set.
- Workstation and server are (for now) in the same VLAN.
- TFTP, PDHCP and Prebootpolicy services are running and are configured throught their conf files to the best of my knowledge.
I do remember that when I installed zenworks it encountered an non-fatal error on the PXE installation. It does seem to be running, though.
The questions are:
Is there a way to verify that the all services are OK?
Have I missed something?
All help appreciated. If anyone of you needs to look into config files I will be happy to post them here.
Hans

On Wed, 09 Jul 2008 10:36:01 GMT, d1ngetje wrote:
> - DHCP and PDHCP are on different machines (DHCP is on windows) so no
> option 60 is set.
this should be wrong as the message ProxyDHCP service did not reply to
request on port 4011. only shows up if that option is set.
Marcus Breiden
If you are asked to email me information please remove the - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.didas.de

Migrate ZEN 11 SP2 VM to ZEN 11 virtual appliance

I am trying to migrate to zen 11 SP3 but I keep running into compatibility issues with the tools.
My current system is one primary server running zen 11SP2 on OES2/SLES10 64bit and one 64bit SLES 11 satellite server in a branch office .
What I have tried thus far:
-I have tried adding a zen 11SP3 v-app to the zone and then retire the old OES VM but this is not supported b/c you can't have a SP3 machine in an SP2 zone.
-I then tried adding a zen 11 SP2 v-app to the zone and run the SP3 migration tool but the migration tool fails b/c the tool does not support migrating to a v-app.
Can someone give me some direction on how to move to SP3? Should I use the SP2 mig tool or is there an easier solution?
Thank you,
Brad

My ultimate goal is to have a primary ZEN 11 SP3 server running on a ZEN 11.3 v-app (I do not want to buy a SLES license). Would it be easier to follow the replace/restore a zen primary server documentation? I was really hoping for a tool that would move this a long a lot faster.
This is what I hoped would work:
OES2 (unsupported SLES10)
migrate to
ZEN 11.2 v-app (supported SLES11)
now use migration tool to go
ZEN 11.3 v-app (supported SLES11)
Thanks for the help,
Brad
Originally Posted by smflood
On 09/07/2014 15:06, BPainter wrote:
> I have read through that documentation and I do believe it will be
> straight forward once I'm to that point. My current primary server is
> an OES2 virtual machine - this machine doesn't have a supported upgrade
> path to 11.3. So my thought process has been to use a ZEN 11.2 virtual
> appliance and then migrate the data from my OES2 machine. After the ZEN
> 11.2 v-app becomes the primary server I then add the ZEN 11.3 virtual
> appliance and run the migration utility to migrate to 11.3. I haven't
> found in the documentation where it deals with this sort of
> migration/upgrade. The ZENworks 11 Server Migration Guide states to use
> the setup.sh -R from the media to perform a migration, but this fails
> because migrating from my OES2 server to a virtual appliance is not
> supported. So how do I migrate my OES2 server to a ZEN 11.2 virtual
> appliance?
You can't use the ZENworks Server Migration tool to migrate to (or from)
a ZENworks Virtual Appliance.
Are you trying to use the ZENworks Virtual Appliance as a stepping stone
to your final destination or is it your final destination?
There's no need to migrate from ZENworks 11 SP2 on OES2 to a ZENworks 11
SP2 Virtual Appliance as you can install a supported Linux (can't be
Windows since you have OES2) OS (I'd suggest SLES11 SP3) on another
machine (could be virtual) and then ZENworks 11 SP2 followed immediately
by the 11.2.4 Update (to support SLES11 SP3).
See
https://www.novell.com/documentation....html#bookinfo
for the Migration Guide.
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

A failure occurred in the document conversion process

A failure occurred in the document conversion process. The document cannot be viewed at this time.
No matter what I can not view attachments. jpg will render, but it seems like nothing else will be.
I do not see Document Viewer Agent (DVA) as a service in GW 2012 (OES2 SLES10)
Seb

I am having the same issue, but only with wav files.
I can click on the <filename>.wav link and open the attachment fine in a selected program, but if I select the "Play" link, the window switches back to the login page with "[962D] A failure occurred in the document conversion process. The document cannot be viewed at this time" displayed underneath.
Any ideas what this could be?
Emily

ZLMMirror SLE11-Debuginfo-Updates-patches

I have been mirroring some of the repositories from Novell (nu) to my environment.
I have working OES2, SLES10 and SLED10 (SP2), when downloading SLE11-Debuginfo-Updates-patches I stumble in the error:
--------- cut
Error: An error occurred while trying to create the bundle "/Bundles/Novell Updates/SLES11/SLE11-Debuginfo-Updates-patches/patch-dbgsp0-openssl-CVE-2009-1386.patch,openssl-CVE-2009-1387.patch_SLE11-Debuginfo-Updates". (An error occurred while trying to create the object.)
com.novell.zenworks.zlmmirror.server.MirrorServerE xception: An error occurred while trying to create the bundle "/Bundles/Novell Updates/SLES11/SLE11-Debuginfo-Updates-patches/patch-dbgsp0-openssl-CVE-2009-1386.patch,openssl-CVE-2009-1387.patch_SLE11-Debuginfo-Updates".
at com.novell.zenworks.zlmmirror.server.ZLMLocalServe r.createPackageBundle(ZLMLocalServer.java:1640)
at com.novell.zenworks.zlmmirror.server.CatalogProces sor.createLocalBundle(CatalogProcessor.java:494)
at com.novell.zenworks.zlmmirror.server.CatalogProces sor.processBundle(CatalogProcessor.java:257)
at com.novell.zenworks.zlmmirror.server.CatalogProces sor.processCatalog(CatalogProcessor.java:135)
at com.novell.zenworks.zlmmirror.server.ZLMLocalServe r.update(ZLMLocalServer.java:732)
at com.novell.zenworks.zlmmirror.MirrorSession.mirror (MirrorSession.java:513)
at com.novell.zenworks.zlmmirror.MirrorSession.execut eCommand(MirrorSession.java:488)
at com.novell.zenworks.zlmmirror.MirrorSession.execut e(MirrorSession.java:283)
at com.novell.zenworks.zlmmirror.ZLMMirror.executeMir rorSession(ZLMMirror.java:279)
at com.novell.zenworks.zlmmirror.ZLMMirror.main(ZLMMi rror.java:152)
Caused by: com.novell.zenworks.zlman.services.coreapi.admin.C oreAPIFault={_Message=An error occurred while trying to create the object.,_Type=5}
at sun.reflect.NativeConstructorAccessorImpl.newInsta nce0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInsta nce(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Construc tor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at com.novell.zenworks.zlman.services.coreapi.admin.C oreAPIFaultMarshaler.deserialize(CoreAPIFaultMarsh aler.java:35)
at com.sssw.jbroker.web.soap.LiteralEncodingStyle.rea dObject(LiteralEncodingStyle.java:433)
at com.sssw.jbroker.web.soap.LiteralEncodingStyle.rea dObject(LiteralEncodingStyle.java:410)
at com.sssw.jbroker.web.soap.LiteralEncodingStyle.rea dObject(LiteralEncodingStyle.java:372)
at com.sssw.jbroker.web.core.InputStreamImpl.readObje ct(InputStreamImpl.java:278)
at com.novell.zenworks.zlman.services.coreapi.admin.C oreAPIBinding_Stub.createPackage(CoreAPIBinding_St ub.java:5061)
at com.novell.zenworks.zlmmirror.server.ZLMLocalServe r.createPackageBundle(ZLMLocalServer.java:1621)
... 9 more
Caused by: com.sssw.jbroker.web.portable.ApplicationException
at com.novell.zenworks.zlman.services.coreapi.admin.C oreAPIBinding_Stub.createPackage(CoreAPIBinding_St ub.java:5068)
... 10 more
An error occured while processing the request. Please check the log file for details
----------- cut
I suppose the cause is due the filename he is suppose to download and "install" into ZLM 7.3 have a comma (" ,") in the filename itself, which is very unusual.
Could anyone confirm if has been experiencing the same problem, if there is any known patch (I searched for this and so far nothing), is this a bug on the ZLM or in the repository?
Any ideas?
Regards,

Originally Posted by tarvindkumar
This is already known issue under ZLM caused due to eDir's Object length
(FDN) limitation in the Tree. This prevents the object creation too deep in the ZCC folder hierarchy or if the bundle name if very long such that it exceeds the Object RDN length 128. See below ZLM URL . Edir might have documented it
Novell Documentation
Well, according with the documentation you sent, we have the following information:
An error occurred while trying to create the bundle. (The object could not be created. This could be because the name is too long, or the object is too deep in the folder hierarchy)
Source: ZENworks 7.3 Linux Management.
Explanation: The error message is displayed because of the object FDN (Fully Distinguished Name) limitation of 256 characters in eDirectory when you create a bundle object either in ZENworks Control Center or by using the zlman command, or during mirroring.
Action: Do any of the following:
Do not create the bundle object deeper in the folder hierarchy, or with long names.
Ensure that the total FDN of the bundle object from its root container in eDirectory does not exceed 256 characters.
The error has been generated due a path+name that is about 150 characters, if it was 128, probably I would agree that it could be a problem. In the previous version actually that was a problem because of the sizes and it was already solved with actions in the database, therefore according to the documentation the limitation is 256, like the previous solution proposed.
Then I got a little bit confused, the newest versions (in this case IR2 and IR3) returns to the lack of capabilities (in path sizes) encountered on the 7.3 with no patches?
The comma in the name bothers me a lot, and also bothers me that this sort of naming is wrong and possibly giving problems and no one dare to change it... why??
Regards,

GWIA 8.0.2 HP2 BAD MESSAGEs

Hi all.
I receive BAD MESSAGE mails from my GWIA several times a week. Many are from users using Spanish accents in the subject of mails sent with Outlook 2010, some of them come from monitoring appliances, some from outside my company. It happened when we had Groupwise 7.0.3 and I had the hope it would be resolved in the latest Groupwise release. Now we have version 8.0.2 HP2 on OES2 SLES10 SP3 x64 machines, but GWIA continues refusing them.
As a continuation of the work I did in another post, I will report here the cases I find and I can resolve manually. If anyone reading this has any answer or suggestion to solve this (I don't want to continue processing manually every BAD MESSAGE we receive), I would be very thankful.
So, let's go with the first one. It comes from a monitoring camera and a "Invalid minimum string length (AA02)" is reported in the GWIA log. Headers are:
<IaHead>
<IaMsgTag>000b7bdc</IaMsgTag>
<IaMsgSender>
</IaMsgSender>
<IaReceivedTime>4e4b5048</IaReceivedTime>
</IaHead>
MAIL FROM:<botzware[at]netbotz[dot]com>
RCPT TO:<lbernaldez[at]tauli[dot]es>
RCPT TO:<admin[at]tauli[dot]es>
RCPT TO:<nagios[dot]tauli[at][externalprovider][dot]com>
Received: from TNCPDMON (tncpdmon[dot]tauli[dot]es [10.10.x.x])
by oescorreu11[dot]tauli[dot]es with ESMTP; Wed, 17 Aug 2011 07:23:20 +0200
Subject: Value Error - Information - Camera Motion - Camara de Techo
From: Camara de Techo <botzware[at]netbotz[dot]com>
To: lbernaldez[at]tauli[dot]es, admin[at]tauli[dot]es, nagios[dot]tauli[at][externalprovider][dot]com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="NetBotzBoundary12345"
Date: Wed, 17 Aug 2011 07:23:12 +0200
Message-Id: <1313558602.12256@TNCPDMON>
I've tested removing the externalprovider address both from RCPT TO: (the whole line) and from the To: line and GWIA accepted it. In another message, I removed the local destinations leaving only the externalprovider one and it also worked. I don't have any more messages to test with, right now, but I will do more testing just to see what happens.
Thanks in advance.
Diego

On 8/25/2011 8:56 AM, dtascon wrote:
>
> Another example (quite extrange): a mail with the following Subject:
>
> Subject: =?UTF-8?Q?Especial_Agosto:_Empleo_y_Formaci=F3n?=
>
> I just removed the question signs:
>
> Subject: =UTF-8QEspecial_Agosto:_Empleo_y_Formaci=F3n=
>
> And now GWIA processes it. Aren't question signs RFC compliant?
>
>
They are. In fact ANY ACCENTS in the headers are ILLEGAL (and the thread
I gave you is a kludge around it) without RFC 2047 encoding.
However, your example is NOT encoded properly and SHOULD be rejected.
Preferably by launching a denial of service attack on the sender, but
alternatively by bitbucketing it :)
The format of an RFC 2047 atom is simple
=?<charset>?<encoding type>?<encoded text>?=
which in broad strokes matches your input here. The Q means use quoted
printable, eg hex value encoding for "high bytes". (The other legal
value is B for base64 encoding).
However your example CLAIMS UTF-8 character set. Fine, a perfectly legal
character set, and in fact the one everyone should pretty much use in
modern days. BUT....
This Cannot be a legal UTF-8 encoded atom- all non US-ASCII characters
are at least two bytes long in UTF-8.(all US-ASCII < 127 is simply byte
for byte, beyond that you use a scheme that involves multiple bytes >
$80. Since this has only one byte > $80, it's illegal).
(In general with UTF-8 you can always recognize bad encoding if you see
only one single high byte. There should be two to four in a sequence
whenever it occurs)
This looks like it might be an ISO-8859-1 encoded subject (since
those are single byte code pages) but the generating mailer is claiming
UTF-8. GWIA is thus 100% correct in rejecting this mail, as best
security practices discard malformed UTF-8 items.
The sender must fix his encoding or his encoding declaration.

[SOLVED] Upgrade from SLES10 SP3 & OES2 SP2 to SP4/SP3 breaks NCS

Hi folks,
(This post was originally meant to be a rant and a request for help, but
while writing the final paragraph i found the solution. It's still a
rant, but i figured i'd post my solution here in case someone else runs
into the same issue.)
I've just spent several hours banging my head against a broken cluster
node. My system is a 32-bit SLES 10 VM running on VMware ESX 3.5.x.
I upgraded from SLES10 SP3 and OES2 SP2 to the next service packs for
each (using the move-to-oes-sp3 script in yast2 online_update).
Everything went well for the first few update/reboot sequences, then
after the final reboot on SLES10 SP4 & OES2 SP3, cluster services would
not load or join the cluster on restart.
I checked dmesg and found errors about "Loading module compiled for
kernel version 2.6.16.60-0.54.5-vmi" into a previous kernel version, so
i tried downgrading to that kernel version, only to find that it was
older than the one i had just upgraded from (it's the original SLES10
SP3 kernel). So i tried upgrading back to the same kernel which is
running on the other cluster node (2.6.16.60-0.77.1-vmi), but that did
not work any better.
<preaching>
I have to say that i'm not impressed that OES2 SP3 isn't even compiled
against the appropriate kernel, and because of SUSE's kernel RPM
overwrite policy there's no way i can select to boot from a previous
kernel to see if that fixes things. Note to SUSE and other distro
builders: if you're not doing kernel package upgrades like Red Hat or
Ubuntu (so that we can select to boot from the previous kernel from the
boot menu), you're doing it *WRONG*.
</preaching>
I then upgraded again to the latest recommended kernel for SLES10 SP4,
and still no joy. Dmesg shows this error before the rot starts:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
When searching for this error i stumbled across
http://ubuntuforums.org/showthread.php?t=1613132
which pointed me to
http://www.mythtv.org/wiki/Common_Pr...lloc_too_small
Adding vmalloc=192M to /boot/grub/menu.lst and rebooting solved the
problem for me.
Regards,
Paul

Originally Posted by Paul Gear
On 13/10/11 07:36, magic31 wrote:
> ...
> Not sure if it's related to the issue you've hit, but along the lines
> of what Kevin already mentioned, there are issues that can arries when
> using the VMI kernel (that I've seen) if having multiple flavors of the
> kernel installed along with it (as in having both kernel-vmi as also
> kernel-smp packages installed) ...
> Curious, is that also the case with your setup?
The system in question has kernel-bigsmp and kernel-vmi installed. We
only ever boot from kernel-vmi.
> I've moved to only using the smp kernel on VMware (along with the
> clock=pit boot option to avoid time drift issues, or pmtr I think in
> your case when also running NCS services in the vm).
When we installed the system (on OES2 SP1, i believe) it was a while
ago, and kernel-vmi with clocksource=acpi_pm on the kernel command line
was the only solution we could find to get reliable time. If there are
updated best-practice documents, i'd be happy to hear about them.
However, this is a production cluster and my boss is (rightly) rather
reticent to make major changes.
Paul
the official Vmware paper on time is that IF you're using SLES 10.x 32-bit you will use VMI and NO kernel params (ie, get rid of the clockpit and clocksource=blah).
But if 64-bit then you're okay.
The easiest, IMO (especially with vmware) is to use the miggui (migration utility). That's how I'm converting all my 32-bit servers in vmware to 64-bit. Works quite well.
--Kevin

Setting up FreeRadius on SLES10/OES2

Hello,
I'm fairly new to Novell and have been tasked with getting Radius Authentication up and running on our existing SLES10/OES2 servers for wireless clients connecting through a Cisco managed WLAN.
I have the radiusadmin PDF file and have installed FreeRadius from the SLES installation media OK but I'm stuck on "Creating the RADIUS Administrator Object" the doco just refers you to generic page for managing user accounts (http://www.novell.com/documentation/...a/afxkmdi.html).
Can anyone let me know what type of user/object I need to create and possibly an example as I'm fairly new to all of this, sorry for what is probably a silly question!
TIA

Originally Posted by warper2
kjhurni wrote:
>
> nson;2238312 Wrote:
>> Hello,
>>
>> I'm fairly new to Novell and have been tasked with getting Radius
>> Authentication up and running on our existing SLES10/OES2 servers for
>> wireless clients connecting through a Cisco managed WLAN.
>> I have the radiusadmin PDF file and have installed FreeRadius from the
>> SLES installation media OK but I'm stuck on "Creating the RADIUS
>> Administrator Object" the doco just refers you to generic page for
>> managing user accounts
>> (http://www.novell.com/documentation/...a/afxkmdi.html).
>> Can anyone let me know what type of user/object I need to create and
>> possibly an example as I'm fairly new to all of this, sorry for what is
>> probably a silly question!
>>
>> TIA
>
> Yeah, it's not the easiest.
>
> Send me a PM and I'll try to email you my docs that I did, if I can
> scrub the IP's in time.
>
> Note: We don't actually use the RADIUS quite the way the original docs
> did. We basically have an eDir group and if you're in that group, then
> you can auth via radius. If not, no soup for you. The original docs
> have you put an attribute on the individual users, which we found more
> tedious than just doing a group membership
>
>
I will say this though. It is easier to setup on sles10 than sles11.
Oh don't tell me that. I don't want to have to look forward to that when we migrate to OES11. Ack!

SLES10 SP4/OES2 SP3 32 bit Clean Install - Basic Questions

Hi everyone.
I am now an expert in installing the above software and ending up with a server which does not work as we require. Must be something I am doing wrong. Hope someone can spot it.
Have installed and supported Netware servers for 25 years without major problems. Decided now to move to SLES because Novell say we should and we need Groupwise 12 to replace GroupWise 8.
The operational environment we are targeting is an 80 user edirectory/NDS based single tree, single context containing two Netware 6.5 SP8 HP Proliant servers running uncomplicated file and print services , NSS volumes, Groupwise 8, DHCP, ifolder, Quickfinder and the like, spread across the two servers. It all works a treat. Client PCs are are all XP Pro with Novell client software.
The idea would be to replace one of the two Netware servers first with a SLES/OES server and then the second Netware server with a second SLES/OES server and move GroupWise functionality to one of the SLES/OES servers. Ideally users would continue to log on using their eDirectory accounts without noticing anything was going on in the background.
The test environment we have set up is a 5 user NDS/eDirectory single tree, single context already containing a single Netware 6.5 SP8 Proliant server running file and print, NSS volumes etc and Groupwise 8. Into this tree we are trying to install a 32 bit server with a empty 36 GB SCSI disc running SLES 10 SP4 with OES2 DP3 as an add in, with NSS data volumes.
Because it only takes a few hours to do we have repeatedly run the SLES 10/OES2 install (probably about 9 times!) with minor variations to see whether we can end up with a properly configured SLES/OES server but there is always one problem or another.
The major problem we have is how to configure NSS data volumes on the SLES server and how to allow users to be validated against their eDirectory entries and knowing whether the test server is 'good to go'.
The process we followed for each test install, after checking edirectory was clean and removing any entries placed in the tree by earlier attempts to install the SLES server in the same tree were:
1. Boot the SLES 10 SP4 32 DVD (downloaded ISO and burnt DVD) and selected Installation.
2. Followed the prompts on time zone and language etc and selected i386 OES CD (also downloaded ISO and burnt) as the Software Add-In.
3. Loaded SLES DVD and OES CD as and when requested
4. At the Partitioning stage we selected the EVMS proposal, and at the Software selection stage selected the base software, file server Role, Documentation, DHCP, eDirectory, iFolder, iPrint, Quickfinder, NSS and LDAP.
5. Miscellaneous errors would appear or not appear during the eDirectory stage (eg LUM error, or iFolder error) but the eDirectory stage would still seem to complete OK and get ticked.
6. The system would then reboot and appear to come up OK.
HOWEVER, we are not convinced we have created a fully working reliable server.
and
SPECIFICALLY we are unable to create NSS volumes and we cannot logon users via their eDirectory accounts.
NSSMU shows a single device sda (33.92 Gb) and three partitions sda1 (70Mb), sda2 (31.91GB), and sda3 (1.94GB). sda2 seems to contain all the 'spare' space on the disk (type Linux LVM) but says there is no spare space to create our NSS partitions.
iManager cannot see any devices to configure NSS data volumes on the SLES server but it connects OK
NSSCON status seems to show NSS to be running
EVMSGUI shows /dev/evms/lvm2/system/ro at 10 Gb, /dev/evms/lvm2/system/sw at 2GB and /dev/evms/sda1 at 70 Mb
So my questions are:
Does the above look right?
Why cannot we get at the spare disk space to set up NSS volumes? Did the EVMS proposal grab it all and if so how do we get it back?
Did not selecting the EVMS partitioning proposal do everything needed to run NSS?
[There seems to be some suggestion in the several hundred pages of SLES, OES and NSS Guides, Installation manuals, Configuration manuals etc that we have studied over several days, that we now have to edit a fstab file to make it work properly (Really? in this day and age where clicking on Setup.Exe will configure a fully working Windows server) Is that so? Is there anything else we need to do?]
How do we get the users to access their NDS accounts to log into SLES and Netware?
How do we know the server is OK for operaational use and 'works' ?
HELP!!!
ADB

alandbond wrote:
> I
> have already trawled the self help Forums believing that before SLES
> 11 came along everyone must have been setting up NSS volumes on SLES
> 10/OES2 as a matter of course as they moved from Netware and so me
> trying to do it now should not be akin to rocket science.
You are partially correct. Admins who used NSS on NetWare likely did
install NSS on OES Linux but I suspect they used a separate drive for
NSS either by installing an additional drive, by carving out a chunk of
space on their RAID array and assigning it to a separate LUN, or by
running OES in a VM where storage space on a single disk/array can
appear as separate drives.
> If Novell say in that guide as they do
> (just as do you and ab and Simon in responses to my post) that the
> IDEAL way to include NSS is to have a separate disk for Suse and NSS
> volumes, BUT as long as you use EVMS to manage the volumes it IS
> SUPPORTED, then I consider it should be possible without grief to do
> this and not considered as me putting round pegs in square holes.
Semantics!
IDEAL = Recommended; EVMS != IDEAL; EVMS != Recommended;
IMO, Novell recognised that they had to provide a way for customers to
install NSS on a system that only had a single disk and provided this
procedure as a workaround. By the way, they also support 2-node
clusters but they aren't recommended either. I have also seen cases
where a supported configuration was deemed no longer to be supported as
NTS became aware of additional complications.
My point (and Simon's and ab/Aaron's) is this: Just because it is
supported doesn't mean you should do it. If we can agree on this point,
I'll try to help you to get it working. The last thing I want to do is
give others the impression that by helping you find a solution we think
this is a good idea!!!
> This latest release of software even goes as far as including an EVMS
> Partitioning proposal which can be selected (as I did) within the
> clean install process.
>
> This is what it says:
Okay! I'm only looking at the information you provided. Let's analyse
it!
>
> A.2.1 Understanding the EVMSBased Partitioning Scheme
> Using EVMS to manage the system device allows you to later add NSS
> pools and volumes
Yes, NSS requires the volume manager to be EVMS and not LVM!
> on any *unpartitioned* free space on it.
But you have not left *any* unpartitioned free space!
> You must modify the partitioning scheme to use EVMS during the
> install. It is not possible to change the volume manager for the
> system device after the install.
True.
> Beginning in OES 2 SP3, the Partitioner in the YaST Install offers the
> Create EVMS Based Proposal option to automatically create an EVMS
> solution for the system device.
> For unpartitioned devices over 20 GB in size,
This is what you have...
> this option creates a boot partition
> and a container for the swap and / (root) volumes
> in up to the first 20 GB,
> and leaves the remainder of the space on the device
> as unpartitioned free space.
But it didn't (or you didn't)!
> Table A-1 shows the default proposed setup
> for a machine with 768 MB RAM.
> The default swap size is 1 GB or larger,
> depending on the size of the RAM on your machine.
> The remainder of the device is left as unpartitioned free space.
Let's look at the default proposal. This is *not* what you have.
> Table A-1 Default EVMS Proposal for Devices over 20 GB in Size
>
> Device Size Type Mount Point
> /dev/sda1 70.5 MB Ext2 /boot
> /dev/sda2 14.9 GB Linux LVM
> /dev/evms/lvm2/system 14.9 GB EVMS lvm2/system
> /dev/evms/lvm2/system/root 10.0 GB EVMS /
> /dev/evms/lvm2/system/swap 1.1 GB EVMS swap
A single (SATA/SAS/SCSI) drive will be known as sda (/dev/sda).
/dev/sda1 is the first partition. In the example and in your
configuration this is the /boot partition. In both cases it is 70.5 MB.
/dev/sda2 is the second partition. The partition uses LVM so logical
volumes of various sizes can be created within the partition. The total
size of all logical volumes cannot be larger than the size of the
partition.
In the above example:
/root is 10.0 GB and swap is 1.1 GB. This leaves: 14.9 - (10.0 + 1.1) =
3.8 GB of additional space within /sda2 which can be used to create
additional logical volumes. Furthermore sda1 + sda2 use only ~ 15 GB.
Only 15 GB of the disk has been allocated. The remainder of the disk is
*unallocated* and *unpartitioned*. Presumably, it was left that way so
that the space could be used for NSS.
In your case: sda2 is 31.91 GB
This does not follow the Default EVMS Proposal for Devices over 20 GB
in Size. Either YaST did not allocate space according to the default
proposal or you changed it. Either way, sda2 (+sda3) consume *all* of
the available disk space. It is no wonder that there is no space
available for NSS!
> What do you reckon???
I reckon that something went wrong along the way. If you did not
specifically change the default allocation yourself, then consider this
one example of kinds the things that can happen when one tries to
exploit seldom used, but supported, features!
It looks like it is time for yet another installation. This time, make
sure you leave enough unpartitioned space on the drive for NSS and let
me know how you make out.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Migedir Error going from NW6.5SP8 to OES2 SP2 on SLES10 SP3

I've searched the forums and was not able to find this particular problem so hopefully someone more knowledgeable than I can help. I have an issue with the Transfer ID utility erroring out at the DIB copy portion of a NetWare 6.5 SP8 migration to 64-bit OES2 SP2. The eDirectory Precheck and Preparation portion of the Transfer ID complete successfully with green check marks. When the Transfer ID gets to the DIB copy part I get a series of error messages.
This is the error from the mignds.log file:
05-05-2011:09:56:20:Information: The DS version on the source server is 10554.
05-05-2011:09:56:20:Fatal: Setting up the NetWare eDirectory migration environment...
05-05-2011:09:56:20:Information: Package 'ncpfs' has been installed.
05-05-2011:09:56:20:Information: Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
05-05-2011:09:56:20:Information: SYS mounted successfully.
05-05-2011:09:56:20:Information: 'novell-ncpserv' package is available.
05-05-2011:09:56:20:Information: Copied scp peer file (ncpmig.nlm) to source server successfully.
05-05-2011:09:56:20:Fatal: SERVER: load nlm ncpmig.nlm failed rc=158.
In the Transfer ID Migration Log this is what appears:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:*****************Command output start**********************************
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory migration utility for Linux
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Version: 2.0 for OES Linux 2.0
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Copyright (c) 2007, Novell Inc. All rights reserved.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Creating the eDirectory migration file locations...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Get the source server administrator credentials -
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir: Enter adminDN(e.g: cn=admin.o=administrators): Enter password:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Source server, xxx.xxx.xxx.xxx is reachable.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The source server, xxx.xxx.xxx.xxx is running on NetWare platform.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:OS Version: v5.70.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Product Version: v6.50.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Version: 1
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Platform: 0:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The NetWare source server is running on OES Platform
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory packages are installed.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Performing pre-migration checks on the source server, 'xxx.xxx.xxx.xxx'...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:ndscheck performed successfully.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Checking time synchronization between source and target servers.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Source and Target servers are in time synchronization
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Performing eDirectory migration...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:This may take time depending on the size of the data on the server that is being migrated.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:The DS version on the source server is 10554.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Setting up the NetWare eDirectory migration environment...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Package 'ncpfs' has been installed.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SYS mounted successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:'novell-ncpserv' package is available.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Copied scp peer file (ncpmig.nlm) to source server successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:ERROR: Could not load secure NCP NLM, ncpmig.nlm on the source server - SERVER: load nlm ncpmig.nlm failed rc=158..
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SERVER: load nlm ncpmig.nlm failed rc=158.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:*****************Command output end**********************************
It looks like the Mig utility can't run ncpmig.nlm on the source server for whatever reason. The previous steps completed successfully so I don't think it's an issue of login rights. The OES2 SP2 server is fully patched with all critical and optional patches. I'd like to add that I've done a couple migrations in my test lab prior to this and they both went through smoothly. I'm also following the exact same steps I used when I performed the lab migrations.
I've also tried the same migration using OES2 SP1 (fully patched and not), OES2 SP2 (non-patched) and OES2 SP3 (patched and not) with the exact same error message. This leads me to believe it's something in the source server causing the issue but I can't, for the life of me, figure out what.
Source server is running NW6.5 SP8 and eDir 8.7.3.10. Target server is OES2 SP2 and eDir 8.8.5 HP6. Does anyone have insight into why the Transfer ID is failing at the DIB copy? Thanks in advance.

Sorry for the late reply. Been extremely busy with our migrations and other issues. To answer the last question, our default administrator login to the tree is not called admin. We prefer not to use default names as they decrease security. I used my own login credentials, which also has full rights to the tree, to proceed with the migration. Determined, as a precaution, that the person performing the migration should add him or herself as a trustee to the source/destination servers AND the container the server objects live in. It's probably a redundant step but should decrease the likelihood of encountering the original issue.

How to update from SLES10.2 to 3 OES2.1 to 2?

Hello,
NOWS SBE 2.5 with SLES 10/SP2 and OES2 SP1 is running fine.
I'm not using simba.
System is licenced and registerd at novell with mainenence.
I did all online updates with the ZMD installer until a few weeks ago
I was told that there will be no more patches for SLES 10 SP2.
How can switch to SLES 10/SP3 and OES2/SP2 online,
to perform the necessary updates?
What went wrong?
Yours sincerely
OliverN

Originally Posted by revilo
Thanks for your reply.
Yes, we made a installation manually, because simba didn't work at the beginning of the year, and several other things like nss, ncp volume, gw migration had to be done manually.
I'm not familiar with novell licensing (Germany).
My customer center shows "Small Business Edition Maintenance".
Can I make a SR to Novell free of charge, or does this mean that I have only access to updates/patches in this period?
If I would update to sp3 via DVD are you sure that the according update channels for sp3 and oes2/sp2 will be added automatically?
yours OliverN
Hi Oliver,
If you have maintenance and it has not expired, you can open a Service Request from the Customer Center. There is no extra cost to open an SR. If you do not have maintenance, or if it has expired, you will not be able to open the SR.
The Customer Center will show the product keys for NOWS SBE, OES, and SLES. Those product keys allow you to register the product and obtain updates. Use those OES and SLES product keys to register OES2-SP2.
If OES2-SP1 is properly registered, you should be fine. There have been some issues with OES2-SP2 not having access to all the necessary catalogs after updating. It may be necessary to re-register using the same product keys that you are currently using.
If you have any concerns, you can call the Novell Customer Center. They can explain what you are entitled to.

IPrint on SLES10 OES2 with Macintosh clients

We have just setup a iprint server on OES2.. Are trying to get a handle on accountabililty of who is printing how much..If I turn on secure printing (which I assume I have to do to force authentication) With the windows clients they work just fine since we are using client32 and it reports to the iprint server who the user is. However with the macintosh computers (OSX) when I go to even install the printer from the servername.mtwp.net/ipp it asks for a username and password and it has our TREE name at the bottom of the dialog box..I have tried all variations I know of username/passwords with and without context and cannot get past this screen. AFP is running on the OES server and I can attach to the server from the macintosh computer.. Not sure what Im missing on the MAC side.. We have a lot of mac computers and would like to get a handle on who is the big print volume users..
Not sure if this matters or not, but this OES iPrint server does not have a replica on it.
If someone can point me in the direction I should be looking it would be apprecited
Doug

In article <[email protected]>, Roehmdo wrote:
> with and without context
>
I don't have any Macs to worry about, but lets be thorough.
have you tried both commas and periods? It might be an LDAP level login
also name,ou1,ou2,org vs cn=name,ou=ou1,ou=ou1,o=org
can the tree name be resolved by IP? A test would be to change the
tree name for the IP of an appropriate server with at least a R/W
replica to make sure there aren't any other eDir issues.
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

EDirectory 8.8.4 schema update failed on SLES10.2 OES2 SP1

We are unable to update schema with optional attributes using ldap
connection. We are using the API ldap_schema_add for updating the
schema.
It is returning 90.
Note: we are able to modify schema using the same in case of eDirectory
8.8.1 and 8.8.2 on SLES 10 sp2
soumyajit_roy
soumyajit_roy's Profile: http://forums.novell.com/member.php?userid=56993
View this thread: http://forums.novell.com/showthread.php?t=380675

Unfortunately, I do not do C.
If the 90 is the LDAP error code from the server, then it is indicative
of a memory error.
-jim
soumyajit roy wrote:
> Hi Jim,
>
> Here are the details:
>
> What programing language? C++
> What attributes? AgentPort and MonitorPort (Listening
> Ports)
> What Class? NCPServer Class in the schema
>
> I have given below the code snippet i am using for the schema
> modification.
>
> Code:
> // All the macros and other variables are defined. This same code is
> working fine in SLES 9 and SLES 10 without OES (both with eDir 8.7.3 and
> eDir 8.8.2).
> .......
> .......
> const int modslots = 5+COUNT(attrtbl);
> LDAPSchemaMod mod[modslots];
> LDAPSchemaMod *pmod[modslots+1]; // room for terminating NULL
> int idx = 0;
>
> // set up our new attribute
> char *oid [] = {pszOid, NULL};
> char *name[] = {pszName, NULL};
> char *desc[] = {pszDesc, NULL};
> char *syntax[] = {pszSyntaxOid, NULL};
> char *xset[] = { "1", NULL };
> char *xclear[] = { "0", NULL };
>
> // NOTE: the 'op' field of LDAP_SCHEMA_MOD is not used by
> ldap_schema_add.
> //
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = LDAP_SCHEMA_OID;
> mod[idx].values = oid;
> pmod[idx] = &mod[idx];
> ++idx;
>
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = LDAP_SCHEMA_NAMES;
> mod[idx].values = name;
> pmod[idx] = &mod[idx];
> ++idx;
>
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = LDAP_SCHEMA_DESCRIPTION;
> mod[idx].values = desc;
> pmod[idx] = &mod[idx];
> ++idx;
>
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = LDAP_SCHEMA_SYNTAX_OID;
> mod[idx].values = syntax;
> pmod[idx] = &mod[idx];
> ++idx;
>
> for (int i=0; i<COUNT(attrtbl) && idx<modslots; i++)
> {
> if (flags & attrtbl[i].attrFlag)
> {
> // set the desired attribute
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = attrtbl[i].attrXString;
> mod[idx].values = attrtbl[i].bSet?xset:xclear;
> pmod[idx] = &mod[idx];
> ++idx;
> }
> else
> {
> if (attrtbl[i].bIsClearable)
> {
> // attribute can be cleared, so do it.
> mod[idx].op = LDAP_MOD_ADD;
> mod[idx].fieldName = attrtbl[i].attrXString;
> mod[idx].values = attrtbl[i].bSet?xclear:xset;
> pmod[idx] = &mod[idx];
> ++idx;
> }
> }
> }
>
> pmod[idx] = NULL; // end of definition
>
> // make the change -- add schema attribute
> rc = ldap_schema_add (schema, LDAP_SCHEMA_ATTRIBUTE_TYPE, pmod);
> if (rc)
> {
> fprintf(stderr, "ldap_schema_add 1 failure (%d): %s\n", rc,
> ldap_err2string( rc ));
> fprintf(stderr, "Failed to add the attribute %s to the schema\n",
> pszName);
> }
> .........
> .........
> //////////////////// End of Code.
>
> Here ldap_schema_add is returning error 90.
>
> This same code is working fine in SLES 9 and SLES 10 (both with eDir
> 8.7.3 and 8.8.2) without OES.
>
>

Mac os 10.6.8 cannot login to OES2 sp3

i'm having issues logging into a clean install of OES2 SP3 Linux SLES10 sp4 server here's my log file:
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 10 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 10 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 11 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 11 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:41 Server-1 afptcpd[4407]: Created session: 12 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:41 Server-1 afptcpd[4407]: [debug] LDAP user name: cn=horchemg,ou=springfield,o=missouri
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:42 Server-1 afptcpd[4407]: Closing session: 12 <0x82afc38>, Socket: 60, Pending requests: 0

On 21/02/2012 23:16, ataubman wrote:
> Also, has OES been patched up? You need at least the November 2011
> patches to get AFP to work with 10.6.8 , IIRC.
I think you're getting your Mac OS X versions mixed up as Snow Leopard
(10.6.x) was supported from the beginning with AFP in OES2 SP2 and
later. See
http://www.novell.com/products/opene...owleopard.html
It's OS X Lion (10.7.x) that requires the November 2011 (and earlier)
patches for AFP in OES2 SP3 but it is supported from beginning with OES11.
HTH.
Simon
Novell/SUSE/NetIQ Knowledge Partner
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.

GW to OES2/SLES10

Similar Messages

Maybe you are looking for