Error 2116

Posted on 1997-09-25
Last Modified: 2013-12-23
In a Win95 peer to peer network I try to share a drive. In Windows Explorer I try to make the drive shared but get errorcode 2116 (with not explaining text!).

Can anyone tell me what that means ?
Question by:janm
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
  • +1

Expert Comment

ID: 1549294
In windows 3.11 Error code 2116 means "The Device or Directory Does Not Exist", according to Technet. Technet says this error message occurs when you are trying to share a hidden directory. I do not know if this goes for Windows 95 too. But its a place to start, isnt it?


Expert Comment

ID: 1549295
I just shared a hidden folder and didn't get any problems.  Are you successful in sharing any other directories or devices??  The answer here can narrow down certain things it could or couldn't be so I'll wait for your reply before posting an answer...also, I know this is a stupid question, but I'll ask anyway, are you getting the same problem if you try re-installing windows??
LVL 25

Expert Comment

ID: 1549296

Go to control panel and click the network icon. Click the file and print sharing button and make sure the box for "I want to give others access to my files" is checked. After checking it, close the boxes, and restart windows if necessary.

Go into "My Computer" and right click on the drive having the files and folders you want to share, and click "sharing".

Using Windows Explorer, find the folder or file you wish to share and right click on it, then click on "sharing".

You should be good to go!

Post your results please!
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.


Author Comment

ID: 1549297
I still have the problem !

Author Comment

ID: 1549298
To Chapie

I have not tried to re-install windows ! - I believe it is something else that cause the problem.
There is no problem in sharing other drives / directories but I have to say that the drive giving problems is a special drive:
I am working with a multiuser Paradox database and that means that all computers have to point at the same directory using the same drive letter. Otherwise the locking do not work.
Therefore I have tried to use the drive "J" for all machines (including the machine containing the data). I place the data on the first machine in directory C:\Data. To change this to drive "J" I use "Subst J: C:\Data" in autoexec.bat. It works OK. I can see and use drive "J" on the local machine but I cannot share it.


Accepted Solution

chapie earned 20 total points
ID: 1549299
First off, stop using Paradox (just kidding I'm a devoted Access'r)

But seriously, I've never tried using Subst for a shared resource, and I assume you're using Win95 otherwise you wouldn't have posted this question here.  Try adding the following to the startup sequence on the client machines.

net use j: \\PCname\Data

where pcname is the computer name on the network that you are trying to share from.  This should add the drive letter j: to the clients trying to access the host data.  But before you do that, don't bother using the subst command and simply share the directory normally
LVL 25

Expert Comment

ID: 1549300
JanM: Windows 95 will not allow you share the drive as long as you are using the SUBST command, however there is a way around that problem. Here's the info and the solution.
PSS ID Number: Q170462
Article last modified on 06-20-1997
PSS database name: WIN95X

The information in this article applies to:
 - Microsoft Windows 95
When you try to share a folder or drive in Windows 95, you may receive
the following error message:
   Sharing: An error occurred while trying to share <share name>. Error
   2116. Shared resource was not created at this time.
You may be able to create the share, but it is inaccessible as a network
You are attempting to share a drive, or a folder on a drive, created using
the SUBST command.
Share the folder from the original drive instead of from the drive created
using the SUBST command.
You can use the SUBST command to associate a path with a drive letter.
This creates a "virtual drive" that can be accessed as an additional local
drive. For example, the following sample command creates a virtual drive F
that refers to the C:\MyFolder folder:
   subst f: c:\myfolder
The virtual drive you create using the SUBST command (drive F) cannot be
shared as a network resource. You must share the folder on the local drive


Expert Comment

ID: 1549301

Share the folder from the origional drive instead of from the drive created using the SUBST command

Thanks for the re-enforcement, that's basically what I meant when I stated.

...don't bother using the SUBST command.....

using the Net Use command on the other PC's trying to reach the shared resouce will ensure they always get the J drive letter
LVL 25

Expert Comment

ID: 1549302
Chapie: While in a way, somewhat reinforced your comment regarding the use if the SUBST command, your answer is still wrong. Read the Resolution and More Information above and you will see why.

Expert Comment

ID: 1549303
while my proposed answer does not answer the initial question, yoou will note that I initially posted a comment trying to get more info from the questioner, and found out the true nature of the problem, trying to access a shared folder from a client workstation.  So, I told the questioner to put the Net Use command on the client side machines.  How is that wrong??  Of course I don't expect much of a reply seeing is how all you bother to do is post KB articles without offering any further bit of help besides what anyone could find out if they put forth the their own effort.
LVL 25

Expert Comment

ID: 1549304
Chapie, as a professional, I will withhold my opinion as to both of your answers, suffice it to say they are both all wet! Rather than answer the mans question, and instead of suggesting that it be rejected if incorrect, you move on with the maybe's. Now, as for your comments about the knowledge base, if you did a little more research, you learn why your last answer is, indeed, wrong!
As a certified professional in both Windows 95 and NT, I have learned to use all the resources available to me, and with that readily teach others how to find answers for themselves.

As for sharing this drive as drive letter "J" by other computers, so they all use the same naming convention, you need not use the net use command.

Once JanM *shares* the resource, thus making it available to others, the others only need to click on the network icon, find JanM's computer in the network neighborhood and click on it, then find the shared drive and highlight it, then click file, then click "map network drive". A box will come up and offer a drive letter, just click the down arrow to the right and select any drive letter you desire. Click the "reconnect at Logon" box if desire, then click "ok". What's all the fuss about!


Expert Comment

ID: 1549305
Of course you don't have to use the Net Use command but placing that in the startup sequence you ensure that the if the user decides to go into the network neighborhood settings and click 'quick logon' they will still be able to use the assigned drive.

Yes, one should use all the resources available to them, but simply posting a KB article without expanding doesn't show much knowledge, just the ability to research, and if you had to go get research on this it only shows that just because someone was able to pass a certification exam doesn't mean they are completely qualified.  Now I understand why MS wanted to change their certification names and remove the 'Professional' from their title, you are shining example of the reasoning behind that.

I don't have to do any more research to find out why my answer is wrong, just because it is not the way you found, doesn't make it wrong, it just provides another *safer* way of reserving that drive letter on a client side machine.  Besides I didn't expect you to expand too much on why you think I'm wrong, 'cause there's not much to say on someone thing that's not true.

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Internet Speed Test 5 137
sync conflicts 1 85
What are the Scan to network folder ports? 7 159
Simultaneous work of Wi-Fi and LAN on Win10 laptop 4 69
FIPS stands for the Federal Information Processing Standardisation and FIPS 140-2 is a collection of standards that are generically associated with hardware and software cryptography. In most cases, people can refer to this as the method of encrypti…
Greetings, Experts! First let me state that this website is top notch. I thoroughly enjoy the community that is shared here; those seeking help and those willing to sacrifice their time to help. It is fantastic. I am writing this article at th…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below.…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question