![]() In both described occasions the manually assigned IP was before/less than 200. ![]() If youre still unable to see/access the NAS. Here some additional info on the network setup: Some Workarounds to Fix NAS drive not showing on network windows 10. The fact, that one time the problem is fixed by turning DHCP on, and the other by turning it off, confuses me. I'm going to leave the question open, because it's not a real answer. Again, just because of not having any other ideas. This did the trick.Īs the Mac-Mini (having the problems now) is/was configured to use DHCP, I manually assigned an IP. Back then I switched the iMac from manually assigned IP to DHCP - just because I was out of other options. Moreover, that is what you must do to start troubleshooting the issue. I remembered, that I once had the same problem with the iMac, although with a slightly different network-setup. check Best Answer Supaplex (Object First) Brand Representative for Object First mace Dec 22nd, 2022 at 5:24 AM Ed563 wrote: I dont think I can connect qnap directly to PC via ethernet Yes, you can. Home Router IP: 192.168.101.1 - ping 100 I did ad Qfinder to the whitelist on my Avast Firewall, but nothing. sudo dscacheutil -flushcache (in Terminal)ĭid anyone else experienced such behaviour? Does someone has ideas on what else to try, or even has a solution right away? Qfinder finds the qnap with NAS IP: 192.168.101.115 (DHCP, not static, QTS ver.4.) but also when I ping the IP I get 100 loss.removing Wifi-connections from Mac-Mini's preferences.In Finder the "Connect as." button, shown under "Network"->"(AFP)", does nothing (But this is something I noticed on the other Macs as well).Ĭonsole shows: 11.12.16 12:13:21,778 NetAuthSysAgent: AFP error -1 mapped to EIOġ1.12.16 12:13:21,778 NetAuthSysAgent: ERROR: AFP_GetServerInfo - connect failed 5ġ1.12.16 12:13:21,779 NetAuthSysAgent: AFP error -1 mapped to EIO ![]() There's just the small "Connecting to afp://192.168.1.3/" window which stays until the "There was a problem connecting to the server "192.168.1.3"" dialog is shown. On the Mac-Mini when I CMD+K "afp://192.168.1.3/" (which is the IP of the NAS), I don't get the typical user-name-and-password dialog. The iMac and MacBook Air have no problems connecting (via AFP or SMB) to the Shares on the NAS. Internet and Routing is done via a Fritzbox 7490 (with FRITZ!OS 06.60). We have three Macs at home (an iMac, the Mac-Mini and a MacBook Air, all with macOS 10.12.1). Firstly you should run the QNAP QFinder application which will scan your network for NASs and should find your NAS The QNAP TS-412 initially requires you. As well tried QFinder (from QNAP) and it doesn't find the NAS. It hangs on "Trying 192.168.1.3." whereas telnet against other (LA)network devices gives "Unable to connect to remote host". Ping, nslookup and traceroute give no hints on network problems (ping comes back and so on). As it's my wife's Mac and she doesn't care about backups or whatsoever, I don't know since when it actually doesn't work anymore. Hello community,To set the scene: We are attempting to inventory our Windows computers and store licenses in a database backup (risk management), but we've noticed something odd about the licensing.Our organization's IT infrastructure is a Windows home en.I have problems getting a Mac-Mini to connect to our QNAP NAS over Wifi. Every time I have to reboot my wifi router (which seems to be once a week at the moment) Im unable to log into my Qnap.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |