it can take a long time and end up ultimately unsuccessful other than to understand the problem. and a screenshot or copy and paste of a netstat scan from the network utility in the Mac. but I need a full overview of your network.Ī few screenshots of the summary page from each Airport. That is why finding by IP (ie not using DNS) is successful. you can find all sorts of issues in a network. Depending on your main router and what domain it has. this is caused by extremely poor DNS Apple introduced at Yosemite.ĭomain is one of the main issues. Apple OS has issues unless the computer you use is directly connected to the same AP as the QNAP is plugged into. I see from your first post this is a fairly complex setup. but not much in the way of solutions.īe aware of domain issues. I recommend you do a google search using a set of criteria like, I am having problems mapping my network drives in windows 10 file explorer.I use synology. #QNAP UNABLE TO FIND WITH QFINDER WINDOWS 10# It is shared folders from my Qnap TS-431P NAS that I am trying to map. This has worked for about 6 months now, but suddenly it does not work any more. I have tried two different computers with the same result. I have tried to fix this for some days now with no luck. I have a post at a official Qnap forum, but no luck there. I have also given remote access to an Qnap official but he has not been able to help me yet either. It seems like a windows issue, but I'm not sure. The funny thing is that I can access the NAS from its web-interface or with FTP. I can also access the nas from my smartphone. Local Security Policy -> Local Policies -> Security Options -> Network security: LAN Manager authentication level -> set it to Send LM & NTLM - use NTLMv2 session security if negotiated (this was done on my win 10 pro machine) In regedit Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing -> Delete the folders under MSLicensing Made sure the service TCP/IP NetBIOS Helper is set to automatic/running Turn OFF all network discovery, un-install my network adapters under 'Device Manager' (also hidden), scan for hardware changes to re-install them and then turning network discovery back ON Enable SMB 1.0/CIFS File Sharing Support under 'Turn Windows features on or off' Enable NetBIOS over TCP/IP on my network adapter TCP/IPv4 protocol Here are some things I have tried after reading about the issue. I can't remember what it was so dont laugh at me :P (pretty much just tried everything I can find) I have also been trying several commands in elevated powershell and CMD that I have found in different forums regarding the issue. Added t he DWORD (32bit) value AllowInsecureGuestAuth 1 under Computer\HKEY_LOCAL_MACHINE\SY STEM\CurrentControlSet\Service s\LanmanWorkstation\Parameters Enable insecure guest logons under Local Group Policy Editor -> Computer Config -> Admin Templates -> Network -> Lanman Workstation When trying to map/connect to the NAS from file explorer this is what pops up (after pressing diagnose). I removed my NAS name from the screendump. I have also tried with \\, same result.I can see the NAS in file-explorer under 'Network' but I can't connect to it. When trying to map the drive from Qnap Qfinder Pro this comes upĪfter all the googleing and reading on forums I have done this seems like a well known issue. The only problem is that it seems there are alot of different "fixes" that work for different people. As I said, I have pretty much tried everything I have come across, but no luck yet. I hope someone can help :) I dont know enough about networking and windows to do this on my own. It turned out to be some sort of problem with the NAS itself, not networking/windows. Glad you fixed it - but I agree QNAP Crapnap. I find something like those small micro cube HP ProLiant GEN8 / GEN 10 microservers with a decent standard Linux Distro (recommend CENTOS / SUSE / UBUNTU ) infinitely better and cheaper for running a NAS than proprietary (and usually more expensive boxes like QNAP). Those 3 distros will work straight out of the box - you don't need a mega powerful CPU for a NAS - Internet / LAN connection more important plus DECENT reliable disks. To insure that you never 'lose' the QNAP again - assign at least one of the QNAP ports to a static IP Address so if this happens again, you can always get back into it manually with static IP address on the other port. It is best to reach out to Qnap if you need more help. Here's 2 NAS boxes 1 HP gen 8 microserver and 1 HP gen 10 Microserver bog standard SAMBA and SATA HDD's Just start samba - and you've got access to your files -simple !!!!! You can use other distros like MINT as well but the 3 I've given are 100% stable and ideal for running things like servers. QFinder Pro is also unable to find the drive on the network. The Microservers are really cheap - especially if you have your own HDD's - these servers are quite small - could even be a box under your main remote TV - and not noisy - and have 4 Bays for HDD's.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |