[split] Synology New firmware issue

[halfelite]

(08-02-2012 11:58 AM)JaHa Wrote:  

(08-01-2012 08:27 AM)accident Wrote:  why waste cpu power on both the nas and pch just to have cifs compatible file sharing? they are both linux, nfs or nfs-tcp doesn't use logins and you can secure the nfs server on your nas to only allow your pch to connect via it.. leave samba and your passwords for native windows.. although windows does have a really nice native nfs client also, you just need to install it.

still it should work with Samba and not have these problems.

We dont disagree it should work, But still a simple fix of switching the PCH to NFS, Until PCH fixes samba for real

[accident]

(08-02-2012 11:58 AM)JaHa Wrote:  

(08-01-2012 08:27 AM)accident Wrote:  why waste cpu power on both the nas and pch just to have cifs compatible file sharing? they are both linux, nfs or nfs-tcp doesn't use logins and you can secure the nfs server on your nas to only allow your pch to connect via it.. leave samba and your passwords for native windows.. although windows does have a really nice native nfs client also, you just need to install it.

still it should work with Samba and not have these problems.

It does for every other brand nas out there. So samba client received some improvements but something specific to synology's setup is buggy. To me that's improvement on syabas's part because previously, samba wouldn't work for anyone.

This issue has 2 ways to fix it so this isn't a blocking bug like a wireless user where their access point has a compatibility problem that doesn't work at all.

Either enable guest or switch to nfs/nfs-tcp which can be secured and improve the speed of the pch at the same time. It's probably 2-5 minutes of your time, paths can remain the same so no jukeboxes break. You can survive the wait for future fixes and improvements to samba.

[jctcom]

(08-03-2012 03:22 AM)accident Wrote:  

(08-02-2012 11:58 AM)JaHa Wrote:  

(08-01-2012 08:27 AM)accident Wrote:  why waste cpu power on both the nas and pch just to have cifs compatible file sharing? they are both linux, nfs or nfs-tcp doesn't use logins and you can secure the nfs server on your nas to only allow your pch to connect via it.. leave samba and your passwords for native windows.. although windows does have a really nice native nfs client also, you just need to install it.

still it should work with Samba and not have these problems.

It does for every other brand nas out there. So samba client received some improvements but something specific to synology's setup is buggy. To me that's improvement on syabas's part because previously, samba wouldn't work for anyone.

This issue has 2 ways to fix it so this isn't a blocking bug like a wireless user where their access point has a compatibility problem that doesn't work at all.

Either enable guest or switch to nfs/nfs-tcp which can be secured and improve the speed of the pch at the same time. It's probably 2-5 minutes of your time, paths can remain the same so no jukeboxes break. You can survive the wait for future fixes and improvements to samba.

First off. It doesn't work for "Every other brand out there". I am having issues with not only my CS407 but also HDD's connected to my Netgear WNDR4500 (EasyShare) as well as to my BoxeeBox both of which will either not connect at all or the same as the CS407 connect and then lose the connection after a short while.

Second I haven't had any problems connecting to SAMBA with any of the previous 4 or more firmware updates so I don't know what you mean by "Previously Samba wouldn't work for everyone"? Even when I can get it to connect it is not stable and disconnects often so I don't know where you get that this is "An improvement on Sybas's part".

Simply put they have broken it and they need to get it fixed. At the very least they should find an immediate way to get us back to the previous firmware which because of the way the written this last one is not possible even using the "Recovery Firmware" option.

Also I saw someone ask earlier if the new RC fixes this. Well it doesn't.

Carl.

[accident]

Then I might recommend in the future you chime in your additional brand findings sooner. When you only see synology synology synology all over the forum, how is anyone or syabas suppose to know it's a wider issue. All the things I have to try it with work and it's a rather substantial list of hardware and different brands.

I know they are working on an updated samba client so at some point it'll come together and it's pretty easy to work around the problem and stay secure if you want. They also appear to be finally merging the dev branches to bring the hardware together to allow easier and rapid updates across the product line so I suspect the 200s will not see this until the framework port update happens.

[thevoiceover]

(08-03-2012 04:44 AM)accident Wrote:  "They also appear to be finally merging the dev branches to bring the hardware together to allow easier and rapid updates across the product line so I suspect the 200s will not see this until the framework port update happens.

I really hope this happens sooner than later, pretty disappointed on all the bugs I have been encountering with the latest firmware I have. To be honest, its been hit or miss on every firmware I have had since release, this and my hardware issues make it hard for me to recommend this product at this point. I just feel after this long out, I pretty solid release should be out and it seems it has been more of a "waiting" game for me as I continue reading from people here "wait until next version" or "in the works.."

I'm starting to feel the C200 series has one developer (who is probably responsible for more than one product at that..) and as with any company who makes money off hardware - spends time on new products over the old...


Sorry if I seem burnt out and negative, its more just bummed out and waiting for a new spark in the x200 line.

[accident]

I can't really comment on the internal workings of the company since I don't know anything about them. But if they have been treating each unit as completely separate engineering I can understand why it's getting slower and slower as they get more and more units to support. And we're starting to see bugs fixed in 1 unit, not making it to all the other units.

If you really care on my thoughts I wouldn't mind typing them up. The short of it, if I was in charge I would be concentrating on the merging and streamlining of the engineering process and then add in the 2 additional hardware models. So to me, yes it's a pain they aren't out yet but I think in the end everything moving forward will get much better. Just growing pains.

[cpluse]

****FIXED******

http://www.networkedmediatank.com/showth...#pid570537

________________________________________________
Hello everyone,

I know I'm awaking a sleeping giant but I need help. I posted this in another thread but seems to be a better place to post.

Not sure if I can cont with this thread. I have followed everything to the T .
 
Here my setup. A-300, Synlogy 1511+(all file on the nas), Wired Cat 6, Imac computer.
I have three shared drive named Movies,WallPaper,Music
 
On all other computer in the house I can see. I'v install the apps for pch also.
 
I’v done the guess enable, turn off the firewall in the router.  With follow everyone advise in this thread.
I am able to see all the shares with Wallpaper & Music thru SMB. I can see the entire files inside the folder too.
But with the Movie folder, I’m only able to access it thru NFS only.  I get an ERR 911 error when I try to access thru SMB. Not sure what it means.  I am able to access thru NFS, but when it opens I’m getting the error “content cannot be found.  Inside the movie folder I have subjects like, Action, Drama, and Documentary.   I gave R/W right  to guest and A300 account. No firewalls turned off. Restarted Nas and PCH. With the NFS setup adding the 192.168.1.*, when I manual try to map, it ask for password. I use the a300 account. Still same issue.  Help!@ Please.   

[-=pUnIsHeR=-]

(07-01-2012 08:27 PM)JaHa Wrote:  Turning guest account on
view the base tree of the directory that are mapped
turn the guest off ..

yes that works.. until you turn of the PH or it needs a restart..
and i have 5 directories so i'm not amused doing this every time

yes it's works!
thnx

[docm3]

(05-24-2012 10:16 AM)cmbe Wrote:  

(05-24-2012 12:43 AM)chris57 Wrote:  Has the reset changed the name and login that you setup permissions for in your Synology Shared ~Folder. I had my device named C200, resetting it changed to PCH-C200. So unless you change the name it would not login correctly.

There were other changes in Network, using static ip and yet it changed to Auto Wired instead of Manual Wired. Chaing back my static ip , subnet, gateway, and DNS server addresses were all defaulted back to factory settings. So I have to reneter them all again. The subnet I missed for quite some time!
If you use DHCP rather than static then you'll need to reboot your router.

The NMT Apps on the player also lost the '/share aka which location is the Media Drive. I have to go into NMT Setup Wizard and reset the Media Drive correctly before any NMT Apps worked or I could change the device name etc. in Settings > NMT Apps.

Then all the Settings > Video/Audio and other menu options need to be checked and set accordingly.

Do a double check and also refer to the WIKI Synology NAS Guide as my settings and setup screens on both the player and Synology DSM are shown in detail.

As I am not at home (only in a few hours) I cannot try your suggestions, but I can say in advance:

1) Before the reset, I have taken snapshots of my old firmware setup.

2) As soon as I have updated the firmware, with no reset performed, the problem was exactly the same. It was working before.

3) Then I performed the reset (and even a second one with the same results) and have reproduced the previous config from the screenshots taken (so I have pretty sure they are identical):

3.1) The pch name was/is the default one (PCH-C200).
3.2) The IP was/is obtained by DHCP (dynamic) with no reservation on router side.
3.3) The subnet mask was/is correct: 255.255.255.0
3.4) The DNS was/is get dynamically and are correct (OpenDNS).
3.5) Using telnet on the PCH, I could ping Synology by IP and Name.

4) I already powerdown/reboot my two switches, two AV 500 powerlines and the router.

5) My NMT Apps (only use the standard ones) are working.

6) I have not changed a single setting on the Synology side, why should I as everything was working before? I already give a quick look on your Synology NAS Guide, and haven't seen anything different than my usual setup.

6.1) Every single device I have (5 PCs and 1 MacBook included) on the very same infrastructure is still working with the Synology.

As soon as I arrive home, I will double check on everything. And try your kind suggestions (chris57 and zombiehunter) and even try to use NFS instead of SAMBA/CIFS on the PCH.

Thanks.

had this problem and it worked with my DS410 as wel! After updating this october 2012 to the newer version of the NMT i had this weird problem. Even though i work with direct ip address instead of hostname. Thanks for the solution!

[canaan]

I'd just like to add that I also have the unable to connect to server error randomly last night. I hadnt changed anything.
after resetting everything I still couldnt see my Synology NAS from my PCH.

I enabled guest account, and the master server options. lastly I updated the NAS firmware. That fixed it, but I am unsure if the guest account, the master server or the NAS update fixed it at this point.

[funtomino]

I dont have any synologic NAS, but just pch-c200, with internal SATA 2TB HDD, and apps on USB stick.
till last FW it was the no1 best MediaPlayer and server for me.

Since the last FW update and reset to defaults settings, the PCH cannot even copy files (avi, divx, mpg....) to the internal SATA hdd, from any source. Nor USB or via LAN is working.

I cannot even create NEW FOLDER on the SATA HDD.
The error message is:

"Alert!!!
Invalid source"

WTF? Invalid Source, when creating own Folder? Doesnt matter if on root of the SATA drive, or in any particular folder...
Drive is OK, has still 500GB left.

How to solve the fu$king rights?
I am noob in telnet commands and linux.