![]() That's why some have the problem and others do not. Give it a try: One logical explanation for the problem is that it's on the network adapter itself. These two small interventions brought the result that the computer from the start does not now come up with the red crosses. In addition, I disabled only the quick start among the Windows power options. So I looked more closely at the settings of the adapter and found the setting "wait for connection". ![]() I thought about what's different about both systems and came up with the idea that it's probably the network adapter itself (since both computers are on the same switch, I dismissed the idea that it might be related to the switch). offline synchronization (do not do it, the red cross disappears, but depending on the network drive in the background, a large amount of data is used for synchronization). Had the "red cross" problem, the other with apparently the same configuration.įor hours I tried all solutions that I found on the net about Or better to say I had two computers in the same network environment with the same Windows builds but different hardware. ![]() The post is a bit older but there are still countless people with the problem described here. Thank you in advance, if you need any more information I will provide that! In and can not establish a connection then. To me it seems like the problem is Windows trying to establish all connections even when the user is not logged I tried syncing a test file on the network but on one machine, this made it even worse. We have to double click the drive to establish a connection and then it can locate the file. When this machine boots up and the network drives are shown as disconnected, Outlook can't find the *.pst file. One Windows machine has its Outlook *.pst file on the network. On the drives, the connection works fine (opens share normally). In 95% of boots (some reboots too) all mapped network drives are marked as not connected (red X) and when we double click In our office we are running 3 Windows 10 Machines daily and a Windows Server 2012 Standard Server. We have the problem of a red X (not connected) on the mapped network drives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |