Discussion Locked

Authenticating to multiple trees

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a situation where we need to run an application on a differant server, in a differant tree. Our main server is NW4.11, the other server is NW 6.0. We are forcing this authentication by mapping a drive on boot up and then entering a user name, password, etc. We are experiencing some corruption on DS on the NW 6.0 server and are not sure if it is caused by this authentication process. Can't find anything at Novell to say we shouldn't be doing this. Any thoughts, ideas, etc.?

14 replies

by andrew.mizzi

Sounds very difficult. I have never had to do it in another tree, if only it was just another context.

First of all, just make sure that the corruption is just, by checking when the corruption first started, in relation to when you first used one computer accessing two trees, because we wouldn't want to corrupt it even more.

Now, I'm not sure how the netware client handles two trees, but I suspect not very well. With the revolution of NW6 on this 'other' server, you could look at using the new technologies of iFolder or any other authentication like this, even VPN over the TCPIP network I would think you are running.

Other than that, its a very interesting issue.

Please let me know how you go at andrew.mizzi@backbonetech.com.au

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. Thanks for your input.

by pierrejamme

You didn't explain how you came to have two trees, but you would normally have one tree with two Organizational Units. Why not merge into one tree, see: DSMerge - Merging two trees together - TID10011011 at www.support.Novell.com

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. Thanks for your input.

by deroode

It is not quite the same, but on our site we're running 2 different trees now for over a year, and it hasn't caused any trouble / corruption. On is a 4.11 tree, the other a 5.1.

Merging the two trees isn't an option mostly because you cannot merge a pure 4.11 and a pure 5.1 tree. And you cannot merge a 4.11 tree with a 6 tree. You can make it work if you make the servers that hold the master replica of the root partition the same server version (both 6 or both 4.11), and that would probablyimply adding a new server to your tree. Now with having tree corruption allready that isn't an option.

Also don't forget most often it is not the technical limitations that make you put up another tree, but merely political...:-)

Make sure you have SP2 on the novell 6 server installed. Further more try to run Dsrepair daily.

Without knowing further the nature of the corruption it's hard to advise you more about this.

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. Thanks for your input.

by bchesmer

Everything I have looked into says this should be a no-problem/brainer. The follwing TID & link describe the best method for accessing 2 trees at the same time.

TID: 10022073

http://support.novell.com/servlet/tidfinder/10022073

Also, make note of what/when/where sort of DS coruption that you are experienceing & post that. That would help all who have posted nail down your problem.

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. Thanks for your input.

by weluvm$?

Multiple trees?

This should not be an issue. For various reasons we have 5 or 6 different trees with NetWare versions 4.11 through to 6 and we can authenticate to ALL tres at the same time successfully. The 4 most important ingredients are: -
DS versions
Timesync
Patch levels
Client versions

If you could supply more details, we may be able to assist further...

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. Thanks for your input.

by nicholasyonko

Using the TREE command in your login script is the best way to authenticate to another tree. It is fully documented in the NWADMIN help files. The one downer about it is that you need to put the user name and password into the login script in plain text to eliminate user intervention in the login process.

by jmartin

Turns out that the corruption we were seeing in DS was not related to the mapping issue. Official word from Novell is mapping to another tree is just fine and is supportable. We thought about the "TREE" command desided against it. It poses some security issues that we could not easily get around. We are a hospital and have some pretty severe regulations regarding security that we have to deal with. Thanks for your input.

This discussion is closed to new replies.