File sharing with user level access

When trying to share files on a W95 computer with user level access, and adding the domain administrator, i will have a message stating that "the provider for the address book can't be found".
Most of our W95 computers on the network doesn't have this problem, only a few of them, and i can't figure out why.
The account "Domain Administrator" is the default account on the english version, but on the swedish version the name is spelled in a swedish way, therefore i have to remove it first and then add the name from the domain account address list. It's when it all goes wrong. But on some other computers, running the english version, i have the same problem.
I have reinstalled the OS on one of them and then it all works fine. But i'm looking for an easier way out of this problem. I have also tried the "a"-version with no success, reinstalled the network... and so on, nothing have helped so far.
My network is an MS Windows Network with one PDC and one BDC and TCP/IP as transport protocol on the same subnet. I beleave that all my computers is configured in the same way, still something differs.
I hope that someone can give me an explanation which i haven't found elsewhere.

Sten Einar Edlund
Boliden AB
seedlundAsked:
Who is Participating?
 
dew_associatesConnect With a Mentor Commented:
Sten, do you want to work through this issue or is it resolved?
0
 
dew_associatesCommented:
Sten:

Are you using the Exchange client?

If so, and the address book is on the server, double check your workstation to make sure that it is search at the correct address and make sure that the user has appropriate rights enabled before hand.
Dennis
0
 
seedlundAuthor Commented:
Hmm, yes. Some users run the Exchange client and some of them Outlook. Our server is MS Mail. But i can't understand what those mail clients have to do with this problem. The error message "provider for the address book" seem to have nothing to do with mail, the "address book" in this case is the domains user accounts data base.

Sten Einar
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
dew_associatesCommented:
Sten: Let me explain a little more then. Outlook, when server installed, relies on the exchange client (not necessarily exchange itself) as to location of common or network files such as a common address book, calendar etc. On the other hand, if each workstation has it's own independent installation of Outlook, then we have another problem.

On the presumption that you are using a Network install of Outlook, there should be either a common address book on the server accessible to all users, or an address specific to each user which is usually on the users server location, and in their own directory.

Based upon how your network is setup, the *provider* is normally the service providing the shared Outlook address book on the network.

Try backing into the problem. First, check the location of the address book on the server. Next, check one of the workstations with the problem and check where it is looking for the shared address book. If it's not looking in the correct location, then correct it. Next, make sure that the user has rights to that location.

Dennis
0
 
dew_associatesCommented:
Sten: I've research my posted comments on our own servers and they work fine, therefore I've posted it as an answer so that we can work through it.
0
 
dew_associatesCommented:
Sten, some feedback from you would have been nice!
0
 
seedlundAuthor Commented:
The problem still persists. Haven't had any time to work on the case.
I will take a look at the location of the address book, but, does this really have anything to do with shared access to the computer? I can't see the connection between those two functions.  Our MS-Mail server uses its own address book, entirely separated from the Windows NT domain accounts.
Forgive me if I'm stupid but I can't help it...

Sten
0
 
dew_associatesCommented:
Sten, believe me, your not stupid. I've been doing this since well before Dos and I learn something new every day. Presuming that the installation is typical and everything has been installed correctly, the issue falls into one of two categories, either it's a user level share issue or the system is looking in the wrong place for the data. That's why I suggested backing into the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.