WannabeMKII

Sorry for the lack of reply, very busy weekend and start to the week. My resolution was to update to 5.2, but it was far from straightforward. When I updated to 5.2, it appeared to work fine, but as soon as I restarted the NAS, the NAS dropped completely from the network, with no IP or anything. So I followed the following thread, in particular, this post - http://xpenology.com/forum/viewtopic.php?p=38545#p38545 It's now working, but I've not tried a reboot the NAS to see if the IP stays, as I don't have the time to tinker if it doesn't at the moment. So I'm going to keep checking in on that thread to see how things progress. Appreciate the help from everyone, especially 'Thecapri'! I also hope this helps others!

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!

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.

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

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?

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

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

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?

I'm on a workgroup and the machines and NAS are on the same workgroup. 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?

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

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?

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?

Well, I managed to resolve the issue and regain full access. Left it running a while, rebooted etc and everything is great. Updated to 5.1 and sticking with that for the time being, as 5.2 appears to drop the network connection. Thanks again to everyone for their help!

Thanks for the pointer, I've found the following; DiskStation> du -ks * 796 bin 0 core 96 dev 6184 etc 5768 etc.defaults 4 initrd 149480 lib 5276 lib64 4 lost+found 4 mnt 12 proc 8 root 8 run 5288 sbin 0 sys 376 tmp 338176 usr 1880304 var 156 var.defaults 4 volume1 4 volumeUSB1 4 volumeUSB2 Then; DiskStation> cd /var DiskStation> du -ks * 4 db 4 empty 76 lib 8 lock 1879636 log 12 net-snmp 308 packages 12 quarantine 188 run 12 services 24 spool 8 state 8 synobackup 0 tmp Then; DiskStation> cd /var/log/ DiskStation> du -ks * 45052 cloudsync 4 cluster 102932 cstn 4 disk_log.xml 4 disk_overview.xml 368 dmesg 48 dmesg.1.xz 28 dpkg.log 24 dpkg_upgrade.log 52 httpd 28 log.nmbd 24 log.smbd 4 lv_log_expand 4 lvm_lv_create_log 65164 messages 168 messages.1.xz 168 messages.2.xz 168 messages.3.xz 168 messages.4.xz 0 mount.log 4 nginx 0 partition 28 postgresql.log 1662744 router.log 0 rsync.error 120 scemd.log 4 smart_quick_log 1208 synolog 8 synopkg.log 4 synoupdate.log 520 syslog.log 4 timebkp.debug 576 upstart So if I'm reading that correctly, it's the "router.log" file that's causing the issue? Does that appear correct? I've search for info on that log file, with no luck. What's it's for and can I safely remove it? Or have I got it totally wrong? Thanks.

Apologies for the straightforward question, but how would I find them and how would I then delete them?