I've been working on a trouble ticket here, and frequent errors of various types prompted me to look to see if files had owners. From my view of the relevant directory, most of the files had no owner, so I directed the ticket to the netware administration group to make sure owners were assigned to all files.

I got a call back stating they had owners, so I double checked and still didn't see any ownership. Both flag and ndir commands from a DOS prompt show N/A for the owner. The Netware properties in the Windows tool shows gobblygook.

I was asked to check my connection type, and it is Bindery (for that server anyway) and was told that was probably why I was not seeing the extant ownership information.

I changed the default protocol from IP to IPX to see what difference there was (I think I had to change it from a default of IPX in order to help out a hospital site where IPX is screened – for that site, I helped them by copying files locally in order to do the maintenance, then copying them back). That made no difference.

So I guess my question is, does having a bindery connection make a difference? What does that even mean? If it does make a difference and I need to not have a bindery connection, how can I change that? Is there away I can detect this situation from within Arev? If there really is appropriate ownership of the files yet for some reason I can's see the ownership, does that imply a likelihood of ownership-related problems?

We are using Arev 2.12 with the NLM.

Hi Victor

I'm pretty rusty on my Novell, hopefully someone else will post too.

I recall that null ownership used to cause problems with Revelation files. The issue used to occur when the account of the person who created the files was deleted. Novell would erase the unowned files next time you tired to access them. The solution was assign ownership to an account that is never deleted, for example administrator.

I believe Bindery mode means use the file properties table maintained on the Novell server itself, versus the file properties maintained by the Novell 'domain controller'. Bindery mode is not the usal setting.

The local file properties table can get out of synch with the domain. That might be happening to you.

HTH

Bob

What version of Novell is the network running on. I believe Novell phased out the bindery in version 6 so your Netware client should be installed with NDS (Netware Directory Services) enabled. This could explain why you're just getting garbage when you check ownership through the Netware utilities.

I seem to recall you can restrict users who can view ownership too.

There should be migration tools when going from bindery to NDS to fix ownership problems and I also seem to recall there is an option on whatever the vrepair replacement (I can't remmember the process) to fix this stuff too.

View this thread on the forum...