Windows 10: In the whole environment included servers and client machines mapped drive is showing RED X...

In the whole environment included servers and client machines mapped drive is showing RES X however the drive is accessible. It is happening just from two weeks ago, Is this is related to patch issue? I want to know the root cause of this issue as well as the fix for this issue. Also I just want to know If we ignore this issue what will happen next?


Thanks

Satendra

:)

 

Red X on mapped network drives.

Hello!

We have the problem of a red X (not connected) on the mapped network drives.

In our office we are running 3 Windows 10 Machines daily and a Windows Server 2012 Standard Server.

In 95% of boots (not reboots) all mapped network drives are marked as not connected (red X) and when we double click

on the drives, the connection works fine (opens share normally).

One Windows machine has its Outlook *.pst file on the network.

When this machine boots up and the network drives are shown as disconnected, Outlook can't find the *.pst file.

We have to double click the drive to establish a connection and then it can locate the file.

My question now is:

How do we finally fix the red X issue?

I tried syncing a test file on the network but on one machine, this made it even worse.

To me it seems like the problem is Windows trying to establish all connections even when the user is not logged

in and can not establish a connection then.

A screenshot of the drives: https://i.imgur.com/lKheko9.png

Thank you in advance, if you need any more information I will provide that!

Best regards

Thomas

 

Mapped drives show disconnected red x on most boots

I have three NAS drives and have them mapped as X Y and Z on both our machines. On one machine two of these mapped drives often show as red x disconnected on every boot. I just have to click on them to make them connected. But I wonder how to get around this slight annoyance. I don’t have the same problem on our other slower machine. I tried unmapping and remapping but seems to make no difference. It is an SSD and boots in seconds. Is it possibly that it such a fast boot that it causes grief with initialisation. I don’t recall it being such an issue pre creators update in the fall

 

windows 10 1809 mapped drives with red X at startup

Thank you for your suggestions, but it is not DNS, TCP/IP, or the network, as SMB1.0 drives are reconnecting without the red x. Only 2003 servers need SMB 1.0 enabled
manually in windows features and only mapped shares on 2012 servers have the red x issue (yes, they are set persistent). Double-clicking on them clears the x and we get in, so it is not permissions either.

No drive mapping changes were made before or after the 1809 update. Most likely The update broke something with SMB 2.0 or 3.0 or something else needed to reconnect
these drives pointing to 2012 servers at logon.

If you search the community and other Microsoft forums for this issue you will see tons of people have this issue after the 1809 update and we all have tried everything
we can think of, so it is an issue the developers should be looking into.