Unable to access shares after update 5.0 to 5.1

[WannabeMKII 0]

I've just updated from Nanoboot 5.0.3.2 running DSM 5.0-4528 to XPEnoboot 5.1-5055.1 and DSM 5.1-5055.

 

Everything appeared to go well, settings are all still present and correct, but when trying to access the shares or even the DiskStation through the network (via name or IP) through any of my Windows machines, Windows states "Windows cannot access \\DiskStation". I tried the diagnose through the prompts, which it advises "The remote device or resource won't accept the connection". I'm therefore thinking a setting has changed with the update?

 

Anyone any ideas what may be causing this?

[WannabeMKII 0]

Just wanted to add, I've been through various forums and tried changing the workgroup along with the netBIOS setting for ipv4, but still no luck.

 

Pinging the DNS name gives the correct IP and it does respond.

 

Also, using Synology Assistant, when mapping a network drive, I get an error, "The network path was not found.(53)".

 

I've turned off all security (AV and Firewalls), but still no success.

 

Apple products appear to connect fine, just Windows...

 

I'm guessing it's a setting somewhere, but can't see it anywhere, or something Windows is caching from 5.0?

[WannabeMKII 0]

Further update, I've also followed this guide - http://forum.synology.com/wiki/index.ph ... work_drive

 

Still no luck.

 

Grrrr....

[Thecapri 0]

Hello, first of all are you on a workgroup or a domain.

 

Are you able to login in the web page? If yes try to create a new folder and see if it working.

[WannabeMKII 0]

Hello, first of all are you on a workgroup or a domain.

I'm on a workgroup and the machines and NAS are on the same workgroup.

 

Are you able to login in the web page? If yes try to create a new folder and see if it working.

I can log into the web interface fine, but as I'm not able to navigate to the NAS through explorer, I'm unable to map or see any of the drives on the NAS. The connection fails at the first step, just connecting to the NAS.

 

Any ideas?

[MarsManden 0]

Did you check the shares? And the permissions on the shares?

Is Windows file service enabled?

[WannabeMKII 0]

Did you check the shares? And the permissions on the shares?

Is Windows file service enabled?

That was one of the first things I checked, as this was my concern. All shares are correct and the relevant tick boxes are ticked. I even tried disabling the Windows file service and restarting it, but no good.

 

It's so frustrating and I bet it's something simple that I've overlooked, but I've spent about 4 hours trying different things, but nothing appears to work...

 

Anything else I can try?

[Thecapri 0]

did you try to make a new share folder to see if the new one works

[WannabeMKII 0]

did you try to make a new share folder to see if the new one works

Sorry, yes I did, but same error "Network Error - Windows cannot access \\DiskStation" - Error code: 0x80070035 - The network path was not found.

[Thecapri 0]

try on the pc a ipconfig /flushdns

[WannabeMKII 0]

try on the pc a ipconfig /flushdns

Just tried that again, but still no luck, same error

[Thecapri 0]

Did you try to map whit the ip not whit the name \\123.123.123.123\share to see if it will work

[WannabeMKII 0]

Did you try to map whit the ip not whit the name \\123.123.123.123\share to see if it will work

I have, yes. Was one of the first things I tried, as thought it might be DNS relaxed. But that didn't work.

 

I'm wondering if it's worth resetting or similar, as long as the data stays intact.

 

Just as an additional note, another NAS backs up to this NAS through Backup and Restore and it's saying my server is offline?

[Thecapri 0]

Just a question dod you do a shutdown and restart not just a reboot

[WannabeMKII 0]

Just a question dod you do a shutdown and restart not just a reboot

Indeed I have, twice so far, along with reboots aswell. No stone had gone unturned, but no luck...

[Thecapri 0]

If you go in the web page and afther in the filestation do you see you stuff

[WannabeMKII 0]

If you go in the web page and afther in the filestation do you see you stuff

They are indeed, all listed, checked and double checked permissions, everything appears exactly as it should do. Even on the power off, I pulled the power cord out to ensure a totally fresh start.

[Thecapri 0]

did you try to rename the DSM to see if it will do the same thing

[WannabeMKII 0]

did you try to rename the DSM to see if it will do the same thing

Tried that one aswell. Even tried restoring an older backup of the settings.

 

It's very frustrating, as I'm sure you can imagine and greatly appreciate your continued help!

 

If only it were easier to post screenshots on this forum aswell!

[GatekeeperZA 0]

Im having the same issues with 4 xpeno baremetals.

[Dfds 35]

@WannabeMKII

 

Have you tried creating a new user account then trying to map a share on your PC using those credentials? Also just a thought, when you ran ipconfig /flushdns did you run it as administrator?

[Thecapri 0]

i did help him a bit the problem when he reboot is that there is no more Ip adress after rebooting

 

we try both thing stactic ip and DHCP IP

 

nothing

[GatekeeperZA 0]

Appologies. my issue is on the 5.2 but same issue. shares not showing up in windows.

I cannot map get an access denied error. even as admin

ive tried to flushdns, manual, static and dhcp leases workgroup is correct.

although it sometimes does allow me to use \\192.x.x.x to access the shares. sometimes via hostname \\server

any ideas would be helpful its good to know the issue persists from 5.1 - 5.2 though

[Thecapri 0]

Appologies. my issue is on the 5.2 but same issue. shares not showing up in windows.

I cannot map get an access denied error. even as admin

ive tried to flushdns, manual, static and dhcp leases workgroup is correct.

although it sometimes does allow me to use \\192.x.x.x to access the shares. sometimes via hostname \\server

any ideas would be helpful its good to know the issue persists from 5.1 - 5.2 though

 

 

can you ping your nas server

[Hyperbit 3]

Clear SMB Chache

Settings -> Fileservice -> Advanced Settings -> Clear SMB Cache