Issues connecting with a new W10 client

FTP Server, File Server, DDNS, SAMBA, AFP, NFS
Post Reply
flycast
Starting out
Posts: 14
Joined: Sat Apr 04, 2015 3:59 am

Issues connecting with a new W10 client

Post by flycast »

I have a new Windows 10 client with OS Version 1903 Build 18362.267. I have a Qnap TS-869L that has been in service a long time. The NAS was just updated and has Firmware version 4.3.4.1000 Build 20190701. I have 15 or so users that connect to the NAS on a regular basis using name resolution with no issues. The newest W10 machine cannot. The newest machine CAN connect using IP address.

I can ping the NAS from the client using both IP and name resolution.

If I try to connect to the NAS from the problem client using name resolution I get a log entry on the NAS that indicates a Samba login failed.

Not sure where to go from here? Any suggestions would be appreciated.
User avatar
Toxic17
Ask me anything
Posts: 6477
Joined: Tue Jan 25, 2011 11:41 pm
Location: Planet Earth
Contact:

Re: Issues connecting with a new W10 client

Post by Toxic17 »

There have been multiple users posting regarding this type of issue on these forums. I suggest you raise a ticket with QNAP Directly.

Roll back to a known working QTS version.
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
flycast
Starting out
Posts: 14
Joined: Sat Apr 04, 2015 3:59 am

Re: Issues connecting with a new W10 client

Post by flycast »

Well...weirdly, it seems to be working now. I did not change the NAS firmware. We did go through a bunch of attempts to fix that entailed rebooting. We think the rebooting many times seemed to fix the issue. Perhaps a Microsoft update slipped in on one of the reboots that we did catch that ended up fixing things???
Post Reply

Return to “File Sharing”