![]() ![]() I had to set up brand new shares all over again, and user accounts, and still the NAS can't communicate with these clients.Īs mentioned before, I have no problems accessing it over NFS and AFP, or SSH or ping. I've reset my NAS twice now (3-second and 10-second hold down) and neither reset helped fix the SMB issue. This is why I've been saying earlier that it's almost like SMB itself is broken. The Dialect response is from the IP of the NAS, exactly. for the _smb._tcp service) You should check this with Wireshark when you first connect to your LAN and try to connect to the QNAP NAS using just \\NAS\.Įxactly, 0x02ff isn't a valid dialect, so my NAS's SMB must be "broken" in some way. Windows does not use Bonjour, so I don't know if their service discovery finds the QNAP smb service. domain portion ("\\NAS\" instead of "\\NAS.lan\"), I don't know if your Windows pc correctly queries your router for the IP of the NAS on your LAN. When you use just a hostname without the. I also recommend giving your LAN a domain name. I would check the MS Networking settings on your NAS. Is this Dialect response from the IP of your QNAP NAS? I don't know what this could be, but if your NAS does not return a dialect that is in the Request from your client, they cannot communicate. 3944f52fc5 - scroll down to Dialects at the bottom. Symlink is good, and the contents are the same.Īs far as I know, 0x02ff is not a legitimate SMB dialect. I get the same results as Mousetick when I check my smb.conf files. I'll dig a little deeper into why one share would cause some issues but now everything is working after a reboot too! I removed it from the smb.conf file and now IP and DNS/etc. After some fiddling around with that I found that one of the shares for some reason was causing an issue. So it looks like the symlink was busted when I checked so that's good to know. If it's busted again, take a closer look at /etc/smb.conf: is it a symbolic link? If yes, to what? If not, what are its contents? What happens if you reboot the NAS? Does SMB still work or is it busted again? The contents of /etc are reset at startup. # cp /mnt/HDA_ROOT/.config/smb.conf /etc/smb.confĬp: `/mnt/HDA_ROOT/.config/smb.conf' and `/etc/smb.conf' are the same file $ cmp /etc/smb.conf /mnt/HDA_ROOT/.config/smb.conf Lrwxrwxrwx 1 admin administrators 21 Jul 5 11:16 /etc/config -> /mnt/HDA_ROOT/.config Lrwxrwxrwx 1 admin administrators 15 Jul 5 13:14 /etc/smb.conf -> config/smb.conf ![]()
0 Comments
Leave a Reply. |