Lion and DSM 3.2: Cannot connect

[LKD]

Seems everybody gets things working nicely once they upgrade to 3.2. Not me. Here's the deal:
1) Upgraded Mac to Lion when it came out -- uh-oh, no more access to my DS-411+
2) Read Synology forums, saw I needed DSM 3.2, Downloaded and installed, rebooted
3) Rebooted Mac
4) Still no access to DS-411+("There was a problem connecting to the server..."). Sad faces.

I'm doing all this on the LAN, so it shouldn't be a firewall problem.

I also tried accessing the server through the Finder using smb://<servername>, with no success.

What am I failing to do?

[Olivier C]

SMB no more supported in OS X Lion.
Try http://www.mucommander.com/

[kimk]

Lion won't support the destination share by smb:// protocol anymore.
Therefore, you might need to check the share settings.
I would suggest to use the default TM bonjour advertisement by DS.
Or maybe a workaround with afp:// to connect to tm share.

[megajustice]

I am seeing a similar issue. The network shares are fine after a reboot, then after one or two machines start backing up, the Mac shares disappear. I reboot and they reappear again. It seems a subsystem is crashing but I can successfully access the server with http://xxx:5000 and 7000.

Bonjour maybe crashing. Suggestions on how I discover the root cause of the issue?

Lion won't support the destination share by smb:// protocol anymore.
Therefore, you might need to check the share settings.
I would suggest to use the default TM bonjour advertisement by DS.
Or maybe a workaround with afp:// to connect to tm share.

[chadforeman]

I am seeing the same problem. I reboot the sinology server and the shares appear in Mac finder for a few minutes and then disappear. I can connect to the drive using DSM 3.2, but I can't maintain a connection in Mac finder. I do not understand how to change my settings as suggested by the previous post.

[nehalem]

Similar issues here - managed to get the drives to share, but it doesn't always recognise them on boot. Furthermore obviously the download redirector doesn't work either.

Surely an update must be released as the device isn't really mac compatible at the moment....

[megajustice]

This is still happening with the GA of 3.2. I'm going to call support today. Ugh.