NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Windows Access Rights Management
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

Since QTS 4.5.2 I’ve been having problems accessing my NAS through Windows File Explorer and can’t log in through web browser (by LAN) through Windows. Android browser / apps work fine. I’ll outline what does / doesn’t work below. Access has always been WiFi, NAS & router are Ethernet. Issues started after 4.5.2 a month ago. -- Also with 4.5.2 I started getting an error that it fixed some DNS settings (see attachment).

Setup:
• QNAP TVS-671 @ QTS 4.5.3 1652 (20210428) = updated today
• (previously was the QTS 4.5.2, updated in early April or late March)
• Has file sharing / folders shared, VPN & FTP, and the basic software. No funky virtual stuff or anything complex.
• Paid SSL certificate for over 2 yrs now. Everything is set for secure connection.
• Both modem / router LANs have always been static IP reserved by MAC & NAS is set to expect it.
• Cable modem (ISP provided but I can pretty fully configure) Arris
@ 192.168.0.1 with NAS at 0.14/15 (E ports #1/2), this is where I originally set everything up 3.5 yrs ago & where the VPN & FTP goes through (I’d not yet configured it to go through my home router)
• TP-Link router ArcherC9 V3 (latest firmware, 1.3.1 build 20171215)
@ 192.168.196.200 with nas at 210 (E port #3), added about a year ago because I was moving away from using the cable modem for my LAN.
• Testing on Dell laptop & Microsoft Surface Pro tablet, both running Windows 10 with all latest updates (including hardware / drivers). Browser is Chrome (latest), also running latest Qfinder.
• Windows (SMB) mapped network drives of folders on the NAS
• Testing on 2 mobile devices running Android 11, using Chrome & QNAP apps.
• NAS is set up for myqnapcloud access.

What stopped working (request timed out):
• Windows 10 can’t access folders through file explorer, by mapped or LAN IP on router's .196.210 & used to on modem's .0.14 but after today's firmware update it can't see either (& NAS doesn't show in network list).
• Windows can't access through Chrome using either LAN IP (swapping between modem/router networks of course).
• Qfinder can't find the NAS on either LAN / IP setting.
• mynas.myqnapcloud.com doesn't work (it's been weird for some time) even though my NAS says it's registered.
• Android stopped connecting with the NAS on the internal router (.196.200 /.210) by Chrome & apps.

What still works:
• myqnapcloud.com - login page does access my NAS from Windows (& Android) Chrome
• Access to the .0.14 Windows 10 mapped network drives from outside through VPN (At least prior to today, now don't)
• Also access to our Google Home Mini speakers by NAS VPN
• Windows can see other hardware devices on the networks (Netflix box, wife's work computer, itself) but of course never been set to access them.
• Windows can ping the NAS at normal speeds from either network. (0.1 pings 0.14/15 & 196.200 pings 196.210 & I believe .0.14/15 since the router is on that LAN).
• Android 11 apps & Chrome can connect to .0.14 on the .0.1 LAN only (I believe before today's update it could do the .196.210 through Chrome on the router's LAN. - I know it originally could.)

Troubleshooting:
• Checked windows 10 & laptop/surface pro hardware updates
• NAS is up to date.
• All systems (modem, router, NAS, mobile devices) rebooted multiple times including power down of all but modem.
• Pings consistently work as expected.
• Checked for IP bans (I'm set to not ban LAN).
• Changed NAS ethernet ports so #3/.196.210 is primary (it seemed to have helped fix "Cloudlink isn't installed or configured" or whatever error it is. I forgot if I had the error through myqnapcloud & fixed by Android LAN/.0.14 [probably] or other way around.)
• Enabled SMB 1 on Windows 10, though it used to work on .0.14 before today's update & on both prior to 4.5.2
• SMB 1 - 3 enabled on NAS.
• I searched for this problem or similar but couldn't find anything even on an older QTS version.

I've not done a QNAP ticket yet, but I wonder if it's a firmware bug or like the error says it screwed up something I had set / working before. (I wish it would tell exactly what it changed instead of just saying it did something.)
Screenshot_20210504-172412.png
You do not have the required permissions to view the files attached to this post.
gtao725
New here
Posts: 6
Joined: Thu May 06, 2021 11:50 am

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by gtao725 »

I have the exact same issue as you. After updating FW to 4.5.3, SMB stopped working for my Windows 10 devices. It works fine for my Windows 7 and Android devices. @QNAP Support Pls fix this ASAP!!!
gtao725
New here
Posts: 6
Joined: Thu May 06, 2021 11:50 am

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by gtao725 »

I just rolled back to 4.4.3 on my TS-453BT3 and SMB is now working. Sth definitely wrong with 4.5.X series of firmware and Windows 10. PS. my Windows 10 always has SMB1.0 support enabled although it shouldn't even be using that protocol since SMB3.0 and SMB2.0 are also enabled on the QNAP. It would be greatly appreciated if someone on 4.5.X FW could verify when SMB starts working with Windows 10 properly.
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

Can you try something for me? My son, a non-admin profile, it works pretty decently even if occasionally some lag, but not lag any worse than like using mobile data. My profiles are admin on Windows 10. I will later on try setting up a non-admin profile on my laptop. But the Windows Surface Pro tablet is what he is using his non-admin profile successfully on. I'm wondering if this has anything to do with it because I did remember reading at some other time a person having issues on admin profiles only, but they didn't make it clear whether it was admin Nas login or not. Considering that just seeing the nas in the network isn't impacted by your login credentials to the nas, then I am wondering if my issue is at least related to the windows privilege. If you can, please test and let me know. That would be very helpful to let qnap know about as well.

Also, how safe and easy is downgrading? I'm reasonably technically knowledge, having hacked consoles and run custom or beta firmware on devices. Of course, if it turns out that all I need to do is make myself a non-admin Windows 10 profile to work around this then I'm totally fine with that too.
User avatar
Toxic17
Ask me anything
Posts: 6468
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by Toxic17 »

SSH to your NAS and type

Code: Select all

smb2status
then in windows powershell type:

Code: Select all

Get-SmbServerConfiguration | select "*enablesmb*"|fl
copy and paste back the 2 results.
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
gtao725
New here
Posts: 6
Joined: Thu May 06, 2021 11:50 am

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by gtao725 »

@danielhw, I don't want to upgrade to 4.5.3 again unless I see a definitive fix somewhere, srry.

@Toxic17, my powershell outputs the following:
EnableSMB1Protocol : False
EnableSMB2Protocol : True

my 4.4.3 FW NAS on SSH outputs the following:
smbd (samba daemon) Version 4.7.12
smbd (samba daemon) is running.
max protocol SMB 3 enabled.

Srry I cannot try on 4.5.3 as I don't want to lose access to my SMB again.....
gtao725
New here
Posts: 6
Joined: Thu May 06, 2021 11:50 am

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by gtao725 »

@danielhw, I can confirm it is safe to downgrade firmware provided it is downloaded from the QNAP Download Center page. I guess it is safe provided the FW versions are not too far apart lol.
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

@Toxic17 how do I log in by SSH? There is that other program, (putty) that other troubleshooting attempts I found suggest using. But I don't know if I'm using it right or what. I fill in the nas IP address but then it says can't connect, never prompting for login username/password or anything else. Is there a different way I should be using SSH? Or is there a different way I should be using this program?

@gtao725 what is the best way to do the firmware downgrade if I need to?
User avatar
Toxic17
Ask me anything
Posts: 6468
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by Toxic17 »

danielhw wrote:@Toxic17 how do I log in by SSH? There is that other program, (putty) that other troubleshooting attempts I found suggest using. But I don't know if I'm using it right or what. I fill in the nas IP address but then it says can't connect, never prompting for login username/password or anything else. Is there a different way I should be using SSH? Or is there a different way I should be using this program?

@gtao725 what is the best way to do the firmware downgrade if I need to?
Have you SSH enabled on the NAS?

https://www.qnap.com/en/how-to/knowledg ... nas-by-ssh


Sent from my iPhone using Tapatalk
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
User avatar
Toxic17
Ask me anything
Posts: 6468
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by Toxic17 »

gtao725 wrote: Thu May 06, 2021 3:35 pm @Toxic17, my powershell outputs the following:
EnableSMB1Protocol : False
EnableSMB2Protocol : True

my 4.4.3 FW NAS on SSH outputs the following:
smbd (samba daemon) Version 4.7.12
smbd (samba daemon) is running.
max protocol SMB 3 enabled.

Srry I cannot try on 4.5.3 as I don't want to lose access to my SMB again.....

That looks pretty normal. EnableSMB2Protocol : True is Windows supporting both SMB2 and 3. there maybe other SMB settings within windows that can affect SMB shares also.
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
gtao725
New here
Posts: 6
Joined: Thu May 06, 2021 11:50 am

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by gtao725 »

@Toxic17 Well the problem is that I tested with 3x diff Windows 10 installations (build 1809, 1903, 20H2) and NONE of those SMBs worked after upgrading to 4.5.3 so I really do not think it's a Windows issue. Plus I also tested with a Synology on the latest FW and it never had ANY issues....

@daniel To downgrade, first obtain the version of FW you need from: https://www.qnap.com/en-us/download
Then after obtaining the firmware zip file, extract the img file from it. After that log into your NAS from a web browser, go to control panel, and do the manual firmware update from there. Just choose the extracted img file. You may get a warning saying there is risk downgrading but you can safely accept and proceed. Let it finish, it will reboot and then that should be it!
User avatar
Toxic17
Ask me anything
Posts: 6468
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by Toxic17 »

I also have three windows 10 machines 20H2 all connecting to my 3 Nas’s two of them running the 4.5.3 firmware. Pretty sure vast majority of users are not experiencing this symptom either.

So something is clearly up with your setup of windows and/or NAS settings.

You may need to get qnap involved - good luck with that.


Sent from my iPhone using Tapatalk
Regards Simon

Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following


NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

@ Toxic17 yes I have SSH enabled. Also, while the vast majority of users may not be experiencing the problem, that doesn't mean it isn't a problem with the firmware. I too highly doubt that it is anything to do with windows, as it was working immediately before the upgrade and without even rebooting the laptop it stopped working immediately after. Additionally, my son's profile logs in just fine at least through the IP address off of the modem instead of the internal home router. If it were anything to do with windows, then why would one profile have failures but another profile wouldn't? Also, logging in through the web browser in Windows doesn't use SMB. And if it were a problem with windows, then why can I see other devices on the network such as media players?

I'm going to try setting up a non-admin profile on my laptop to see if that fixes the problem. If so, then I will get qnap involved too. But if not, then while I will still get them involved I will end up needing to downgrade in the meantime. Which, again, if it is Windows itself then why does downgrading instantly fix it? I highly doubt that are broken machines were working due to a bug with qnap this whole time and now that they fixed that bug are broken machines suddenly stopped working but only on the parent / admin profiles.
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

@ gtao725 thank you for the instructions about the downgrade. I may end up doing that if my other fix of testing a non-admin Windows profile doesn't work. I'm glad it is basically as easy as a router firmware change. That just makes it so much quicker.
danielhw
Starting out
Posts: 15
Joined: Sun Sep 16, 2018 10:55 pm
Location: Earth
Contact:

Re: NAS stopped communicating with Windows after 4.5.2 & 4.5.3

Post by danielhw »

I've run through the troubleshooting here ["How to Fix the Windows 10 File Sharing not Working Problem? - Appuals.com" https://appuals.com/how-to-fix-the-wind ... g-problem/ ] and it didn't work.

I've also created a non-admin adult user & child user (my son's account) on my laptop, but neither worked like my son's preexisting profile on the Surface Pro.

I'm going to try and get QNAP involved, but then I may downgrade.
Post Reply

Return to “Windows”