[tas60]

Hi all

I've been attempting to connect to a Netware server at work via OSX
10.2 (Finder: Go: Connect to Server: 132.234.208.1)

This results in the following error:

Connecting to afp://132.234.208.1. An error has occurred (error=-5002).

The closest I've gotten to a resolution is creating a new osx user.

This new user account allows me to connect to the Netware server. However this is not an ideal solution given that I'd have to transfer all my user settings and files from the old account. This then
creates a new set of (bigger) problems with ownership and file permissions.

Given that I can connect to the server using the new account, I'm guessing that a network preference has been corrupted in the old one.

How can I identify which preference this might be, if indeed it is a preference problem?

I've spent countless hours going around in circles with this one.

Thanks

Tas

[Nobody]

For whatever its worth: MacOS error -5002 means "bad UAM".

A UAM (User Authentication Mechanism) is a software plug-in found in the Authentication folder inside the AppleShare folder. The AppleShare folder is located in the Filesystems folder inside the Library folder on your Mac OS X disk.

I have no idea what to do with this knowledge. Anyone else?

[tas60]

Come on guys. There must be someone out there that can help with this. images/icons/confused.gif

[Nobody]

You've essentially got three options to allow you to connect your OS X computer to a Novell Netware server, and it depends on which version of Netware is running on the Novell box.

1) If you're running Novell 5.x or 6.x, you can purchase and install blank>ProSoft Engineering's Novell client for Mac OS X. This will allow you to gain access to a Novell Server without having to ask the administrator to make any changes to the server (i.e. install something).

2) If you've a Novell 5 or 6 Server, you can have your Administrator purchase blank>Novell Native File Access NLM. This will allow clients to connect to a Novell server without any "client software." Mac OS 9.x users get to use the Chooser. OS X users get to connect via "Go to Server." Windows clients use the built-in networking. The Native FIle Access NLM passes TCP/IP, CIFS and, NFS protocols.

3) If you've a Novell 4.x (and now 5.x) server, you can have the Admin purchase and install the blank>ProSoft AppleTalk NLM. This gives Mac OS 9.x and OS X clients the ability to connect via the AppleTalk protocol without the need of a client install on each workstation. This is the least desirable option because AppleTalk is a slower network protocol than TCP/IP and many network admins don't like AppleTalk on their network.

More info: blank>http://www.macwindows.com/netware.html

By far the easiest solution for you is going to be number 1. I don't know of any way to make OS X connect without this additional software.

Damien Barrett

[Nobody]

Damien - my interpretation of the original message posted by "tas60" was that he is indeed able to connect successfully to his Netware server under what he is calling a "new OS X user" account. His problem is that this Netware server is rejecting attempts at login while he is logged into OS X under a previously existing user name.

[ 11-21-2002: Message edited by: HMB ]

[tas60]

Yes HMB - I can connect to the Netware server Damien

Have you read my original post? As HMB notes, I can connect to the Netware server (via native file access) using any other OSX user account that I create on my computer.
My problem is that I can't connect using my original account. This happens to be the account with the all-important file permissions and preference files.

If I swap preference folder from my original account with a pref folder from a new account, then the problem disappears. But this "breaks" other programs and permissions.

Surely it shouldn't be this difficult to fix this problem using the "world's most advanced operating system". Do Apple engineers read this forum?

Hope you guys can help.

[Nobody]

Apologies for not reading your first post closely enough. Perhaps someone else will stumble across this post and the info will be useful to him/her.

As to Tas' problem. It's interesting. I've been doing some research on Novell's site, but am not finding much.

Just out of curiosity, what happens if you boot into OS 9.x and connect to the Novell server via the Chooser using your original user login. Perhaps this might help narrow down whether the problem is with OS X or with the Netware server.

[tas60]

Hi Damien

The problem is not OSX specific as I can connect to the server using ANY OTHER OSX account that I create.

There is no problem with OS9.

As I mentioned in my previous reply, I can also access the server via OSX if I swap the entire preference file from my original account with one from any other account.

[Nobody]

When you say "swap the entire preference file" you mean you're swapping the entire preferences folder for that user. Yes?

And that's why some of the other programs aren't working...because the original prefs files (.plist files) aren't there anymore...? Yes?

If so, then it's likely a single preference file in original preferences folder that's causing your problem. We just have to figure out which one it is. You've already identified this as the problem, I think.

So have you tried paring down using educated guesses the preference files in your original user folder? I'd start with the com.apple .plist files that are related to your network settings.

com.apple.systempreferences.plist
com.apple.internetconfig.plist

Of course, work only with backups so you can put back the original .plist files. You might also do a side by side comparison of the preferences folder sorted by date (brand new user vs. original) to determine which prefs files are generated/modified when you log into the Novell server.

[tas60]

Damien

My apologies - I should have said "entire preference folder".

I've already tried what you've suggested but can't find exactly which preference file is causing the problem.

I wonder whether anyone on this list has a "hotline" to Apple. I would imagine that an Apple engineer could tell us straight away which pref file needs to be deleted or replaced.

[Nobody]

You could try the "halving" method. Move half of the preference files to a different folder. Log out/back in. See if you can connect to the Novell server. If so, then the culprit file is in the first half you moved. If not, it's in the remaining half.

Repeat process by halving again (quartering) the preference files until you identify which preference file is causing the problem.

This method is age-old and used by many. Conflict Catcher uses this method to identify extension conflicts in Mac OS 9.x. It's tedious as hell, but it works.