Share From Synology Stopped Working
-
I have Synology NAS we use for Archiving and all of a sudden it no longer let's you get to it from the DNS name in file explorer... it has a simple address: \archives\ ... but it just stopped working...you can still ping the DNS name (archives) and go to the web GUI at http://archives . But the file share ONLY works via the IP Address.
If you try to go to \archives\ you are met with this...
And you can't authenticate...but if you use the IP Address (\\IPADDRESS), it works fine and can get to the share...
Our DNS/DHCP is Windows Server 2012 R2 based...
It has been driving me batty but I'm sure it is an easy fix but can't seem to find it.
-
I hate to asked. Have you already restart synology and your 2012 R2 server?
-
Just wanted to point out that archives isnt a DNS name but a NetBios name. If you can get to it by IP it points to some sort of issue with the resolution. NetBios was historical done with WINS. However in modern systems you typically are pushing out a search domain to your clients via DHCP and GPO so when you look up 'archives' it appends it to be 'archives.domain.com' to do a dns lookup rather than NetBIOS. We always use FQDN on drive mapps even with search domains setup. Try using the FQDN of the archives server and see if it works and this will show if there is an issue.
-
Is your Synology joined to the domain? If so, do the users trying to access have proper permissions? Also, if joined to the domain, confirm that it is still connected. Occasionally the domain connection can become disrupted for various reasons.
If you go to a command prompt and type "net use" do you already have an existing connection established with the Synology using a different user account?
I don't think this would be it since you can access from the ip address but what version of SMB do you have set for your minimum and maximum on the Synology?
-
Check the time with the Synology and the server are the same and if you had it joined to the domain that the domain relationship is not broken. Then if all that is correct, check the share permissions.
-
I wonder if something got messed up in Windows Credential Manager - try clearing out the connection for this username/password combo and see if that clears things up.
-
Thanks for the tips over the weekend...I am about to tackle this now...
-
Yes, both the NAS and Server 2012 R2 have been rebooted.
-
I just tried the FQDN of \archives.server.local and it takes me to the same login prompt that doesn't authenticate:
-
This only happens with the fileshare as the WebGui for the synology works fine.
-
It is on the domain. And users have rights to view it (only myself and a few others have write access)...those rights and permissions work fine if we get to the fileshare via \ipaddress
-
SMB Is enabled. Here are the Min/Max settings:
I save this for for last because it is resolved now...there were time discrepancies on both file server and Synology NAS that didn't seem to affect any other system here at work...I fixed them borth and file share is working now...
Always the simplest right?
-
-
Good to see that you were able to resolve this. From a security perspective I'd suggest disabling that SMBv1 access that we're seeing in your screenshot.
-- Cheers!
-
@garak0410 said in Share From Synology Stopped Working:
were time discrepancies on both file server an
So that was the issue then
-
@dbeato Crazy huh but thankful for the suggestion.
-
@garak0410 said in Share From Synology Stopped Working:
@dbeato Crazy huh but thankful for the suggestion.
If the Synology supports NTP you may want to enable it and point it to your Domain Controllers.
-
@garak0410 said in Share From Synology Stopped Working:
@dbeato Crazy huh but thankful for the suggestion.
Well, Time differences greater than 5 minutes with the Domain Controller causes problems all the time
-
On a side note, why on Earth are you using SMB1 protocol? Turn it off everywhere, It's insanely insecure. Ransomware loves SMB1. Also, turn on SMB support on the Synology all the way up to SMB3.
-
@taurex said in Share From Synology Stopped Working:
On a side note, why on Earth are you using SMB1 protocol? Turn it off everywhere, It's insanely insecure. Ransomware loves SMB1. Also, turn on SMB support on the Synology all the way up to SMB3.
Probably because it was on by default when things were set up. You do not normally even see that screen when setting things up.
