The drive to which the shortcut refers is unavailable. Shortcuts do not work, what should I do if the shortcuts do not open? No access to network folder

Question: The network drive is marked as inaccessible

On a computer running Windows 7 Professional, the network drive Z: is mapped, which points to the \\comp\obmen folder on a computer running Windows Server 2003 on the local network.
Sometimes this network drive is marked with a red cross, and when you try to access it from any program, you receive an error:

"...refers to an inaccessible location. This could be a drive on this computer or a network share. Make sure the drive is inserted and connected correctly, or that you are connected to the Internet or local network and try again. If it fails again, you may that the data has been moved to another location"

Although in fact there is a local network connection to this network folder too.
Just click on the Z: drive in Explorer - the red cross disappears and everything works fine.

It turns out that Win7 somehow incorrectly displays the state of this network drive?
Is there any way to fix this?
So that the operating system correctly displays the state?

Answer:

Quote ES:

Command Script + Task Scheduler

Question: Installing the program on a mapped network drive

Good afternoon

We have Windows 8. A network drive is connected. You must install the program to a folder on a network drive. When the installation wizard comes to selecting the installation folder, I click “browse” and see neither the computers in the network environment nor the mapped network drive.

How can I get the network to be displayed when selecting the program installation folder?

Added after 1 hour 53 minutes
Thanks for the answer.

I will try to describe my situation in more detail.
There are 40 machines on the network with different operating systems from WinXP to 8. On one of the machines with Win 8 OS (assigned by the server for some program X), shared access is provided to the folder in which program X is installed. This folder on the other machines is mapped as a network drive and X program client seats are installed on this network drive. There are no problems on computers with XP: the X program is being installed, when the wizard comes to choosing the installation location, “browse” and select a network drive.

When I try to install client places on computers with WIN 8 OS, after clicking the “browse” button in Explorer, there is no mapped network drive and no computers in the network environment at all. Although "My Computer" contains a mapped network drive, it allows you to access it, change, save and view its contents.

What could be the problem?

Answer: It looks like something terrible - install a program on a network drive to use from client machines.
If the program is already installed on a network drive, what prevents you from installing the program locally on your computer and then changing the paths?
Or try installing the program on a machine where a network drive is connected, and then display a shortcut from the network drive to the win8 client.

Question: Network drive

Hi all.
Gentlemen, please tell me what the question is:
We connect a new network drive,
After a reboot, it requires you to re-enter your connection credentials.

Details:
Servers: Windows Server 2008 and 2012
Account: Student with user rights.
for network folders - this account has full access.

We connect the network drive Z: (from a server with Windows Server 2008) - everything is fine.
We connect the network drive X: (from a server with Windows Server 2012) - after a reboot it requires entering credentials to connect.

And this is not on all computers, but only on campuses in classrooms.

In the accounting department, Consultant+ works from a server with Windows Server 2012 - everything is fine.

Could there be a problem with the system?

Tell me who has encountered this.

Added after 21 hours 55 minutes
The question remains open, but the situation was resolved as follows:
bat file into startup with the following content:
net use x: \\pdct\progs /persistent:no /user:Student 11qqaaZZ
x: - drive letter of the connected drive
pdct - server name
progs - name of the folder to be connected, like a network drive
Student - login
11qqaaZZ - password

After loading, it displays a message that it was not possible to connect all network drives, then the system itself boots completely and the startup files are executed. Therefore, it is our file.

It is necessary to increase the waiting time for connecting network drives.

Answer: connect via Explorer (service) -> (connect network drive).
or
via command line (net use x: \\pdct\progs /persistent:no /user:Student 11qqaaZZ)
the result is the same

Server1
name - pdc
working group - netadm

Server2
name - pdct
working group - mkts

Passwords are different
Initially, the Student user's password is 123.
and if Windows server 2008 allows such a password, then Windows server 2012 swears, requiring a complex password.

Computer:
name - k-301
working group - mkts

If you connect from an admin account, using another account to connect (respectively Student 11qqaaZZ), then everything is fine. After reboot the disk connects itself.
and when connecting from a Student account, after a reboot there is drive X in Explorer:
when accessing this disk it asks for login and password,
and in the line the user name is k-301/Student, and not just Student???

The computer logs say that it is impossible to connect a network drive, the login or password is incorrect.

Question: Problem with mapping a network drive for users

Given:
Elevated domain running Windows Server 2003 r2 with AD configured.
There are a bunch of users and a SHARED network drive “Z” on a separate file-sharing server running windows server 2008 r2.
Network drive Z is connected automatically by some script when domain users boot into the OS.
Recently, the network drive “Z” in a full state (the scale under the drive in “My Computer”) began to show that less than 10% of free space remained and turned red (which annoys users). BUT the volume that is shown to users on the “Z” drive DOES NOT BELONG TO THE NETWORK DRIVE, BUT BELONGES TO THE “C” DRIVE with the FILE SHARING SERVER OS. Perhaps the former admin is joking...
Task:
1. Find out where the common script for domain users is, indicating the network drive.
2. Fix display of network drive fullness.

Answer: Looks like I've got it halfway figured out.
Apparently, this mapping of a network drive occurs due to the fact that the “DFS Namespace” is located in a folder at the root of the “C” drive.
The next question is how to move this “namespace” to another “native” disk, where the file-sharing folder is located?
I could be wrong and this won't help...

Question: Windows7 disconnect network drive

How to disable a network drive with a red cross in Explorer? those. the disk of which no longer physically exists with the computer. When you try to disable it using standard means, the system writes “error not found network path” and does not disable it. The problem is that it’s an eyesore and when loading it reminds you that it couldn’t connect to all network drives. Thank you.

Answer: check out what I found:

Disconnect network drive network connection does not exist

If you need to disconnect a network drive, but instead of disconnecting it throws the error “The network connection does not exist,” then you should simply temporarily “replace” this network drive with a link to a live share, for example, linking it to \\localhost\c$ and reboot the machine, after which it can be easily removed. Example via command line:

Net use i: \\localhost\c$ /persistent:yes
reboot (I just killed the explorer.exe process)
net use i: /delete (I then had to manually disable C$, which appeared in place of the former network drive)
found it here

Question: The Map network drive button does not respond

Good afternoon
Win Server 2008 standart SP2
Not in the domain.

As an administrator, I go to the terminal - Computer - click connect a network drive. - Doesn't respond to presses at all.
What could it be?
p.s. User account control is turned on.. maybe because of it?
And where is the executable for launching the Network Drive Wizard, you can launch it with the right button - run as administrator..

I also didn’t find such an item in group policy from the manuals on the Internet.
"Next, let's create a group policy and go to the User Configuration > Preferences > Windows Settings > Drive Maps section"

Answer:

Quote local:

The wizard starts like this:

Rundll32.exe shell32.dll,SHHelpShortcuts_RunDLL Connect

Will it work?

You can also connect a network drive using the Net use command.

Question: Network drive for another user

There are two users on the computer: User and Administrator.

Is it possible to do this:
1) go under User"a
2) using the command line (namely NET USE) create a network drive for the Administrator.

And so that when a User tries to log into a network drive, a message something like: Access is denied.

We immediately make a user transition, go under Administrator and see the network drive and calmly log into it.

Is this possible?

Answer: Well, if so, then it won’t work since they are mapped for a specific user
You can use a script, shtask or GPO so that when you log in, the network drive is connected.
my opinion: if the user does not have access, then there is no need to arouse his curiosity and leave him in the dark
out of curiosity he starts picking, and picks... then you won’t be able to figure it out without a bottle

Question: [solved] Failed to connect to network drives

When you start the computer (Windows xp sp2, Celedon D 3 GHz, 512 MB, Epox i915, built-in network card), a Windows alert pops up stating that it was unable to connect to network drives; naturally, programs that work with this drive do not start. If you immediately go to My Computer and try to go to the network drive, it opens normally and quickly, after which everything works without problems until the next reboot. I changed switches (Surecom, ancient 3-com, D-Link) - the problem remains. I did not check the network card and wires.
What could be the problem?

Answer: Murder7
You have some kind of tricky problem.

You can try in policies (gpedit.msc):
Computer Configuration -> Administrative Templates -> System -> Login
Enable "Always wait for network initialization at boot and login."

If it doesn’t work, in the script (your Logon.cmd) you can do something like this:

@Echo Off SetLocal EnableExtensions EnableDelayedExpansion Rem Loop until the server becomes available:Loop Ping -n 1 -l 1 -w 750 Server_name_or_IP_If Not "!ErrorLevel!"=="0" GoTo:Loop Rem Mapping network drives here NET USE Y: \\Name_or_IP_server\Name_shares /PERSISTENT:NO Exit

Although this is a perversion (not a solution to the problem, but a workaround :))

Question: Mapping a network drive to a group of users in a domain

When a user successfully registers in a Windows Server 2003 R2 domain, a network drive is mapped by executing a script file that is executed upon logon. If there are a large number of users, this script must be prescribed for each user. Tell me, is it possible in Windows Server 2003 R2 Service Pack 2 to map a network drive to a group of users?

Answer: If each user has their own network drive, then in the user properties in the profile tab you can connect the home folder.
If all users from a group need to map one network drive, then this must be done through GPO. User configuration, windows configuration, login and logout scripts.

Question: Create a network drive on the server

Guys, I need help, I need to make a network drive on the server, there is 1 router, a lan cable goes from it to the server and it distributes the Internet to other companies, the drive is required without any privileges, purely for back-up, what do I need to do for this, I tried to set up a file server and shared it, but it’s odd... Maybe there are articles, etc.

Answer: RMB on my computer "connect a network drive" and select the shared folder, or via cmd

net use W:\\address on the share\

While working with a computer running Windows, the following problem may occur: when you click on a shortcut to a disk or network resource, the system displays a warning that drive or inaccessible referenced by the Ink shortcut. In most cases, solving this problem is not difficult.

If you open a disk or resource through a shortcut, which, for example, is placed on the desktop, then the error “The disk or network resource referred to is unavailable” occurs as a result of the fact that the address written in the shortcut does not correspond to the actual path.

To make it clearer, let's give a specific example. The user inserted the flash drive into the USB port of the computer and since he often uses this drive, he decided to move its shortcut from “Computer” to the desktop. After that, he inserted a flash drive into the same port many times and everything worked. However, at some point, the usual USB, for example, turned out to be busy, which is why I had to connect the drive to another port, and this time the flash drive did not open through a shortcut on the desktop, but instead an error window popped up.

The reason for the error that a disk or network resource is unavailable to which the lnk shortcut refers is that when the user connected a flash drive to the same port, the system always assigned it a name, for example, “Disk G,” but since it is now inserted into different USB, it was given a different name.

but when I try to log in, the system displays the following message:

Windows cannot access \\computer\network_resource. Permission to access \\computer\network_resource absent. Contact your network administrator to gain access.

In the Windows XP operating system, a similar message sounds like this:

No access to \\computer\network_resource. You may not have permission to use this network resource. Contact the administrator of this server to obtain the appropriate access rights. Access denied

Why can't I access the network resource?

The reason may be due to the following factors:

• The user does not have permission to access the share.
  These rights are configured on the tab Access and are relevant only for setting up network access.
• The user does not have permission to access the folder at the NTFS permission level
  Configured on the tab Safety. This setting regulates access rights both over the network and locally.
• The user does not have network access permissions or NTFS rights.

How to share a network folder with all users

Settings must be performed on the computer where the network resource is located.

Go to Computer Management:

Open the section Shared folders. Select a subsection Shared Resources and find out the local path to the folder that is open to the network.
In our example, we see that the network resource temp matches local path C:\temp :

Find the local folder, right-click on it and call Properties:

1 The first thing to check is network access permissions. Open the tab Access and press the button Advanced setup:

Press the button Permissions:

We check for whom network access is open, and also check the rights.
In order for all users to be able to access the network resource, the list Share Permissions need to add a group All.
In our case, full access is open to the group All. This means everything is fine with network permissions:

2 The second thing you need to check is NTFS rights. Go to the tab Safety and check the global permissions to access the folder.
In our example, we see that only users and administrators of the local computer can see and enter this folder. This means that if we try to log into a network resource under a user who does not have an account on the local computer, we will be denied access.

In order to allow access to the folder to all users, even those who do not have an account on the local computer, you need to add the same group to the list All. To do this, press the button Change:

Adding a group All and press OK.

Attention! It is NOT necessary to search for a group in the list of groups and users. You can simply write the word “Everything” with your hands - always with a capital letter.

Now we indicate which operations are allowed for the Everyone group. To access and download files over the network, just allow:

• Reading;
• Read and execute;
• List of folder contents.

After setting permissions, click OK to save your permission settings.

They are a generally accepted norm and their presence will not surprise anyone. Due to the availability of Internet connections, various online services are becoming increasingly popular. Some of the most popular are network folders and remote resources, organized both on your home network and provided by your Internet provider. Most often, everything works as expected, but from time to time there may be errors that prevent full operation, which the average user does not know how to solve. One of the most popular errors is the “No access to network folder” errors. Some of them may be designated by a numeric or alphanumeric code, such as 1231 or 0x800704cf. These problems can be caused by various factors. In this article, we invite you to understand all the reasons and also suggest ways to solve them.

No access to network folder

Let's imagine that you have several computers between which you want to set up a home network so as not to constantly copy the necessary files. In this case, you need to create a folder on one of the computers and make it publicly accessible so that it can be accessed from any other device with Internet access. It could even be a smartphone or tablet.

One of the most common errors when working with remote folders is that there is no access to a network folder, which may result in error code 0x800704cf. You see a public network folder in Explorer, but when you try to open it, you get the message “No access to resource.” The exact text of the message may vary depending on the operating system version. What are the possible causes of this problem? There may be several of them:

• An individual user was not granted access rights to a folder located on the network.
• The user does not have permission to access the network resource at the operating system security level.
• The user generally does not have any permissions to access the resource.

Every problem can be solved. Let's take a closer look.

Configuring access to a network folder for each user

All settings must be performed on the computer or resource on which the contents of the folder are stored. To configure user access to a folder, you must:

1. Go to computer management (depending on the version of the operating system, right-click on the My Computer icon on the Windows desktop or the Start button, then select Management or Computer Management) and select Shared Folders - Shared Resources.
2. Find a folder in the list of resources that you cannot access and look at its location on your hard drive.
3. Open Explorer and find the desired folder (Windows 10 users can perform further actions without going to Explorer by simply right-clicking directly on the Computer Management utility menu).
4. Right-click on it, select Properties - Access - Advanced settings - Permissions (or Properties - Permissions for the shared resource).
5. You will see at least two items - Administrators and Everyone. Hover the cursor over the All item and make sure that all items in the Allow column are checked (full access, change, read). If there is a checkmark in the Deny column opposite some item, you should remove it from here and put it in the Allow column.
6. Confirm the changes by clicking Apply - OK, and then try again to use the network resource.

Right-click on “Computer” and select “Manage” from the context menu

Configuring access to a resource at the system security level

Sometimes it happens that the operating system security level prohibits third-party users from accessing a network resource. To fix the problem:

1. In the Properties menu, open the Security tab and click on the Edit button and then Add.
2. In the “Enter the names of the selected objects” line, capitalize All and click OK.
3. Once you are taken back to the list of groups and users, hover over the newly created Everyone group and check the actions you want to allow. The checked items by default are quite sufficient for reading data from a remote network resource.
4. Click Apply - OK - OK and try to access the network folder again.

Error 1231 occurs when trying to connect to the Internet

Error 1231 occurs when a Windows computer cannot access resources located on a remote server. Most often it occurs when an Internet provider provides access to an international network using VPN technology. In addition, it can occur when trying to access a local resource of a network access service provider. If you had access and suddenly lost it, this problem may occur for one of the following reasons:

• problems from the provider;
• loss of connection between the subscriber and the server;
• computer network card failure;
• network card driver failure;
• The operating system security system blocks the VPN connection;
• incorrectly established or disabled local network connection;
• actions of virus programs.

First of all, you should check whether error 1231 is caused by your Internet provider. To do this, you need to launch the command line (Win + R - cmd, or right-click on the Start button - Command Prompt) and enter the following command:

net view \\domain:domain name,

Where domain name means the server address that the provider provided to you to connect to the World Wide Web. If “System error 53. Network path not found” is displayed, then the problem is on the part of the service provider. In this case, you should contact technical support.

If you don’t get this error, you’ll have to look for the reason in your Windows computer or laptop. What can I do to fix error 1231?

Conclusion

We hope that we have helped you with solving the problem of accessing network resources with codes 1231 and 0x800704cf. We are confident that if you follow our instructions exactly, you will be able to solve everything on your own. Please indicate in the comments whether you were able to resolve the issue without the help of specialists.