![]() Unfortunately making a string of unnecessary changes when you don't understand Of course there are many other possible reasons for network problems but the advice is usually drowned out by other posters suggesting every possible change to network settings. I frequently post that solution on these and other forums as something simple to try first, e.g. The shared files and folders popped right up after this! It sounds too simple but it worked for me. Under Windows Credentials, type in the name of each machine, username and password ![]() Go to Credential Manager on each Windows 7 machine on the network ![]() I tried ALL the above suggestions to no avail but in my case the following worked for If you have feedback for TechNet Subscriber Support, solution!įor what it's worth department. Please remember to mark the replies as answers if they help and unmark them if they provide no help. Please check whether it can solve your issue. Click Close to close the Local Area Connection Properties dialog box. Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK two times.ĩ. Click the General tab, and then click Advanced.Ĩ. Click Internet Protocol (TCP/IP), and then click Properties.Ħ. Right-click Local Area Connection, and then click Properties.ĥ. Click Start, click Control Panel, and then clickĤ. What a mess! I will pass all this to TechNet forums.Ĭheck whether File and Printer Sharing for Microsoft Networks has been turned on.ġ. Nor can it find the system \\PHILIP at all. It sees the QNAP TS-251 NAS device but if i want to look at its folders i still get the "Windows cannot access The new system (NORMA) can now see itself and EAGLE-3 and work with both. Well i followed your instructions exactly. I had posted this to Microsoft Answers on Dec 9 and had a reply from Roohi Taj S which I followed to no avail:. All folders to be shared in each system have been so shared. The Network Discovery and Share settings are set as described. UPnP Device Host have all been set to go. Likewise Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery and I have followed several papers on the web so Windows features Simple TCIP, SMB (all), SMB Direct have been set to automatic and started. as above I use Windows 10 Pro version 1809 updated fully at all times. The systems are all Intel NUC6i7KYK or NUC8I7HVK, the NAS is a QNAP TS-251. This is essential that I be able to connect properly. Since I use the NAS device for file backups (using Beyond Compare software), I can access the NAS unit using it's IP address in Edge, I can see it using the QNAP software QFinder Pro (latest version). The NAS device is listed in File Explorer under Network but I cannot open it to view it's contents - I get the message "WindowsĬannot access \\NAS" and error code 0x80070035. The first two units see it and can move files to it, but it cannot see the other two units in File Explorer. On a second unit (Unit_2) the sharing works but within File Explorer I do not see Unit 1 listed under networks unless I enter \\Unit_1 to make it viewable. On one unit (Unit_1) everything works fine - I see the other two systems and the QNAP NAS in File Explorer as I wouldĮxpect and the necessary sharing's work. Microsoft once again challenges my LAN arrangement and "sharing" between all three Windows 10 Pro v1809 units.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |