nas issues help

MasterOC

MasterOC

MasterOC

Associate
Joined
29 Sep 2014
Posts
1,696
Location
Caithness , Wick
so I have a 2 tb Seagate nas attached to the network , every computer , phone and device sees the nas and has no problem accessing the public account straight off the bat and other accounts with valid login details .

my main rig see's it on the network but returns this message



where as the laptop for example get me straight in



ive tried reseting the adapter , releasing and renewing ip addresses , resetting the router .... I'm nae daft but I feel this is to simple a fix. help I'm going crazy
 
In command prompt flush the DNS resolver cache. ipconfig /flushdns might help if it is a dns related issue. If you have manually set the dns as google, cloudflare etc in the adapter settings you might think about setting up the secondary adapter as the local router so you can resolve on the local network.

Can you hit it by unc to the ip address? If you can you can set a static route in your host file, go to c:\windows\system32\drivers\etc and add an entry for the name against an ip address in the host file.
 
Last edited:
bledd said:
Can you ping it?

Start run
\\nasname

Start run
\\ipOfNas
Click to expand...

the system cannot find the file to run according to CMD … on both commands

Vince said:
In command prompt flush the DNS resolver cache. ipconfig /flushdns might help if it is a dns related issue. If you have manually set the dns as google, cloudflare etc in the adapter settings you might think about setting up the secondary adapter as the local router so you can resolve on the local network.

Can you hit it by unc to the ip address? If you can you can set a static route in your host file, go to c:\windows\system32\drivers\etc and add an entry for the name against an ip address in the host file.
Click to expand...

the nas is on 192.168.0.23 , can accses the control panel via the browser no problem , I can also use the DLNA portion to accsess and download public files , but doesn't stream on the fly , has to save the content befor I can accsses it .
 
MasterOC said:
the system cannot find the file to run according to CMD … on both commands



the nas is on 192.168.0.23 , can accses the control panel via the browser no problem , I can also use the DLNA portion to accsess and download public files , but doesn't stream on the fly , has to save the content befor I can accsses it .
Click to expand...

Have you got a firewall on the main machine or network sharing turned off? in windows 10 control panel > network and sharing center, on the left "change advanced sharing settings" file and printer sharing is it turned on?
 
Vince said:
Have you got a firewall on the main machine or network sharing turned off? in windows 10 control panel > network and sharing center, on the left "change advanced sharing settings" file and printer sharing is it turned on?
Click to expand...

Nope and network file sharing and printer is enabled , network set to private also , I can ping the nas via name and ip no issues , still can’t access .
 
When I've seen this in the past on a friends network I discovered the Windows Username and the Samba Username to access the NAS share were the same and Windows didn't like it at all, we changed the username for the share and Windows was happy again.
 
So here’s where I’m at , I’ve formatted several times - using different versions of 10 , each with different credentials ( both outlook and local accounts with vastly different user account names . I’ve completely dumped the nas and formatted all data including defaulting all settings , replaced old CAT 5 with New CAT 6 cabling , connected via wireless , changed the NAS server name , looked into login credentials and shares . Everything is PERFECT and yet still this issue , formatted the router , defaulted and updated with latest firmware , DLNA works perfect as is UpnP working . Am I loosing it ??
 
Update guys - so after all this , it was something simple but completely undocumented and hidden , this im sure will effect a lot of pre built nas users. to the point in which they bin theres. as it turns out the latest creator update disables SMB 1.0 , and therefor needs to be re enabled , how windows can decide that SMB 2.0 os priority over comparability when it has no legacy support . Completely ***** off with it . Thanks for your helps guys , only took me to loose all data before I solved it
 
Literally just came here to suggest the SMB issue, sorry I didnt see the thread sooner!
 
bremen1874 said:
I'd be asking why my NAS still needs SMB1?

No firmware updates available?
Click to expand...

Not one , last automatically pushed update was in 2016 , and no manual updates available . Not really anything data sensitive is stored on the nas but did have a lot of private dev work on there and obviously keep sakes like photos of my children so security wasn’t high priority. Just more of a dump drive . It’s not great granted the insecurities of SMB 1 but that should have been my choice not Microsoft’s .

PiKe said:
Literally just came here to suggest the SMB issue, sorry I didnt see the thread sooner!
Click to expand...

No worries , one of them things . Thanks though
 
You must log in or register to reply here.
Back
Top Bottom