Film-Tech Forum ARCHIVE: Dolby DSS200 and FTP servers

This is topic Dolby DSS200 and FTP servers in forum Digital Cinema Forum at Film-Tech Forum ARCHIVE.

To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=16;t=001735

Posted by Carsten Kurz (Member # 5396) on 12-17-2013, 05:31 AM:

A DSS200 user was trying to load content from a Synology NAS - which didn't work. Login and directory listing was possible from the DSS200, but actual content transfers gave an error.
He set up filezilla server on a windows machine and got the same result. The connection logs do not show specific issues.
The FTP client on the DSS200 GUI has very little configuration options.

He is sure that file access rights are set correctly - he can FTP into the synology with the same account from a windows client and transfer data this way.

Any idea what could be the reason?

Anyone using the Dolby FTP client successfully with Filezilla?

- Carsten

Posted by Scott Norwood (Member # 30) on 12-17-2013, 07:08 AM:

Is it an issue of active vs. passive mode? Do the servers support both? Is there a firewall/packet filter in the network somewhere?

Posted by Marco Giustini (Member # 4544) on 12-17-2013, 07:43 AM:

Make sure you are connecting through the Theatre Network port.

Posted by Francois Bouzigues (Member # 8030) on 12-18-2013, 10:49 AM:

Retro ingesting (from dolby to the nas) is tricky. Try get the contents from /generatedPackages/ and not /

Posted by Pete Naples (Member # 761) on 12-18-2013, 02:50 PM:

What's the OS on the Synology?

I had long discussions with Dolby support about NAS units that would work easily with Dolby servers.

The short version is that NAS units running LINUX or a manufacturer specific OS will be difficuly or nigh on impossible to get working properly. NAS units running Windows Server will be (and we've proven this) easy. The rationale was to do with security protocols.

Posted by Mattias Mattsson (Member # 4308) on 12-18-2013, 09:44 PM:

This is probably due to setting the default gateway of the DSS200 wrong. It should normally be set to an adress on the theatre network or be blank.

Posted by Scott Norwood (Member # 30) on 12-18-2013, 09:57 PM:

This still sounds like a firewall or active/passive mode issue to me, since the directory listing works, but data transfers do not. Does the server support both active and passive mode and is it on the same subnet as the server, with nothing between them? If they are on the same subnet, the gateway address will not matter. Is everything else on the network configured correctly (no duplicate IP addressees, correct netmasks for everything, etc.)?

Windows vs. Unix server shouldn't matter. The ftp daemon might, though, so tell us what it is. Pro-FTPD is probably the most commonly used server (and among the most highly configurable), but there are lots of others as well.

Posted by Brad Miller (Member # 2) on 12-19-2013, 12:00 AM:

quote: Marco Giustini
Make sure you are connecting through the Theatre Network port.

Wrong. It doesn't matter. Either will work.

quote:
Retro ingesting (from dolby to the nas) is tricky. Try get the contents from /generatedPackages/ and not /

No it isn't tricky...but you must get it from the /generatedpackages folder as noted above. Just grab the appropriate folder (named with the uuid) and pull via BINARY on your FTP client. Don't try with "auto" or "ascii".

quote: Mattias Mattsson
This is probably due to setting the default gateway of the DSS200 wrong. It should normally be set to an adress on the theatre network or be blank.

Wrong. The default gateway of the DSS200 is for reaching the outside world and will almost always be x.x.x.1 Assuming you are on the same physical network, your computer simply needs to be on an unused IP. For example, if the server is at 10.10.10.10 then set your computer pulling the package on an unused IP such as 10.10.10.11 or 10.10.10.12 or 10.10.10.13 (whatever isn't already being used). Definitely make sure all equipment in the projection network is on and fully booted, then try to ping the "unused IP" before you arbitrarily decide to use it or you might have all sorts of "not fun" headed your way.

I've never used a Synology NAS, so I can't help with the specifics of that.

Posted by Carsten Kurz (Member # 5396) on 12-19-2013, 06:29 AM:

But shouldn't Filezilla on a windows machine work as an ingest source? I'm talking about pulling content from the NAS, not from the Dolby.

Strange that both methods, get from NAS and get from Filezilla, do not work, although directory listing is possible.

I told them to look into the connection logs, but there are no specific error msgs visible.

- Carsten

Posted by Marcel Birgelen (Member # 6801) on 12-19-2013, 06:45 AM:

I agree with Scott, if file listings work, but data transfer isn't happening, it is most likely an active FTP issue and you should check if there is some firewall active on the FTP server or in between if both aren't in the same subnet.

Posted by Carsten Kurz (Member # 5396) on 12-19-2013, 07:25 AM:

Makes sense to me.

Edit: I asked them, they tried both active and passive mode. NAS and Dolby are connected through a simple Gigabit switch.

Filezilla <-> NAS works. Filezilla ftp client -> Dolby FTP server (put content) works.
The NAS has no FTP client, so putting content on the Dolby from the NAS is no option.

It's a Synology Diskstation, DSM 4.3

Opening the connection to the NAS from the Dolby works, content is displayed.
Starting a transfer with the arrow key, however, delivers a "failed: content not found" under 'copy progress'.

They will try another NAS now. I don't care about the NAS. I have trouble to understand why Dolby and Filezilla will not work together. Isn't there anyone here using that combo?

- Carsten

Posted by Pete Naples (Member # 761) on 12-19-2013, 09:34 AM:

I use Filezilla to push onto Dolby servers almost every day. I have tried Filezilla server briefly once and never got it to work.

I've tried various NAS units and oy got those running windows Server to work. A friend at Dolby told me he had got a Linux based NAS to work but had to hack the OS somehow.

Posted by Kris Verhanneman (Member # 5562) on 12-19-2013, 10:05 AM:

We have Filezilla Server running on a Xp pc. Shows up in the network page of the dolby soft (we just copy content from that drive to dolby not the other way around).

Posted by Carsten Kurz (Member # 5396) on 12-19-2013, 12:42 PM:

Kris - just to get that right - you connect TO the Filezilla Server FROM the Dolby? That is, you start the content transfer FROM the Dolby?

- Carsten

Posted by Marco Giustini (Member # 4544) on 12-19-2013, 01:20 PM:

quote: Brad Miller
Wrong. It doesn't matter. Either will work.

Almost correct.
The client you use will work. On other clients - i.e. Filezilla - you'll need an Active connection for the FTP to work through the Auditorium port. The "quickconnect" establishes a passive one.

Posted by Kris Verhanneman (Member # 5562) on 12-19-2013, 03:23 PM:

Carsten,

no the other way around. We copie from filezilla to dolby.
When we need content from dolby to a drive we use a the ftp client software.

Posted by Carsten Kurz (Member # 5396) on 12-20-2013, 05:52 AM:

quote: Marco Giustini
On other clients - i.e. Filezilla - you'll need an Active connection for the FTP to work through the Auditorium port. The "quickconnect" establishes a passive one.

Marco - can you explain this a bit more in depth, please?

- Carsten

Posted by Marco Giustini (Member # 4544) on 12-20-2013, 10:25 AM:

Sure.

I noticed that if I connect my Filezilla client to a Dolby Server through the Theatre Network I can do it simply using the quick connect tab. If I try via Auditorium Network it does not work (not sure I remember correctly now, I think it either connects and fails to list the content or it lists the content but refuses to transfer any files).

Other people using different FTP clients (WS is one of them) were happily connecting to the Auditorium port - as Brad pointed out - so I played with the options in Filezilla until I found out that to work on the Auditorium Network the FTP must be set to "active".
To be honest, I have no idea what the difference is, just know it works! [Smile]

Hope that helps

Posted by Marty Brenneis (Member # 6817) on 06-14-2014, 07:10 PM:

I wound up reading this post because I was having trouble ftp transferring media from the booth computer to our DSS200. I installed DCP-O-Matic and can now take in alternate content and make a DCP to transfer into the DSS200.

Filezilla is working great. I needed to open the Site Manager and create an entry for the DSS200. I gave it the address (in our case 192.168.1.130), set it to FTP and "Use plain FTP", login type Normal, username dolbyftp and password dolbyftp.
I then hit the "Advanced" tab and set the local directory to the transfer folder on the computer. Than on the "Transfer Settings" tab I set it to "Active".
When I clicked "connect" it linked right up and I am now transferring the folder with the DCP files in it to the server.

Here is an XML clip to import into Filezilla site manager:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <FileZilla3>
- <Servers>
- <Server>
<Host>192.168.1.130</Host>
<Port>21</Port>
<Protocol>0</Protocol>
<Type>1</Type>
<User>dolbyftp</User>
<Pass>dolbyftp</Pass>
<Logontype>1</Logontype>
<TimezoneOffset>0</TimezoneOffset>
<PasvMode>MODE_ACTIVE</PasvMode>
<MaximumMultipleConnections>0</MaximumMultipleConnections>
<EncodingType>Auto</EncodingType>
<BypassProxy>0</BypassProxy>
<Name>DSS200</Name>
<Comments />
<LocalDir>C:\Documents and Settings\All Users\Documents\My Videos</LocalDir>
<RemoteDir />
<SyncBrowsing>0</SyncBrowsing>
DSS200
</Server>
</Servers>
</FileZilla3>

Thanks for the tips here, I had many of the same issues listed here so I thought I would sum up the path to success.

Carry on!
Marty

Posted by Aleksey Butakov (Member # 8330) on 07-07-2014, 06:33 AM:

Hi.

I had the same problem - content transfers from synology to dss200 gave an error.

directory FTP NAS - /volume1
content - /volume1/storage/ROBOCOP_3D_RU_XX_NORMALNIY_VALLlE_FILM

Dolby server always tried to access to /volume1/storage/ROBOCOP_3D_RU_XX_NORMALNIY_VALLlE_FILM, but FTP-path is /storage/ROBOCOP_3D_RU_XX_NORMALNIY_VALLlE_FILM

1. I included anonymous access to FTP & gave to the anonymous author a home folder /volume1/storage.
2. I created the folder /volume1/storage/volume1.
3. I created the sym-link: "ln -s ../ /volume1/storage/volume1/storage" in the in folder /volume1/storage/volume1.

So when Dolby applies to address /volume1/storage/ROBOCOP_3D_RU_XX_NORMALNIY_VALLlE_FILM, it gets in /volume1/storage/volume1/../ROBOCOP_3D_RU_XX_NORMALNIY_VALLlE_FILM. This folder carries there where also the first. the content can being downloaded.

Hope, this instuction will help.

Posted by Ioannis Syrogiannis (Member # 3235) on 07-09-2014, 09:48 AM:

Hello Aleksey, and thank you for your solution/workaround.

So, you mean that you created a symbolic link in the initial FTP folder of the anonymous user (to bypass that would get you actually out of the subfolder you are.
I am in /volume1/storage/volume1/ folder and when I follow the symbolic link that seems like a subfolder by the name "storage", I actually give a command like "cd .." and I go one step lower on the file system tree (/volume1/storage/ instead of /volume1/storage/volume1/storage/). If I got it right, since I am not very familiar with sym-link syntax.

Another thing I wonder is if the problem resides on the synology or the dolby server side.
If I was to login from another FTP client to the synology NAS, would it be the same?
If I was to login to another NAS from the DSS200, would it be the same?

Posted by Aleksey Butakov (Member # 8330) on 07-09-2014, 10:08 AM:

Ioannis Syrogiannis

You're right.

All other ftp clients work correctly with this synology NAS.
Carsten Kurz in the first page says that the same problems were still with Filezilla ftp-server.

Posted by System Notices (Member # 2357) on 06-23-2019, 07:51 AM:

It has been 1809 days since the last post.

Posted by Hakan Bicer (Member # 7471) on 06-23-2019, 07:51 AM:

Hi all ;

I have 5 auditorium , 2 screen Dolby DSS200 3 screendolby IMS2000

I can use filezilla server for ingesting content for all screen there is no problem .

but I have some issues about retro ingest process.

IMS2000 screen can retro ingest from dolby DSS200
but Dolby DSS200 screen cant retro ingest from IMS2000

can I get help from friends who know about the subject?

Posted by Leo Enticknap (Member # 534) on 06-23-2019, 11:54 AM:

In relation to the "make sure you use the theatre network" issue on the previous page...

The following is what I have found out from personal experience: it is not a definitive statement based on Dolby documentation.

My experience has been that either of the two NICs will work for ingest and (from the GeneratedPackages folder) outgest. As others have pointed out, the connection type needs to be active, not passive, and the data transfer mode needs to be binary, not ASCII (FileZilla will use binary with a DSS200 if this is set to auto, but some other FTP clients may not).

The functionality difference between the auditorium and theatre NICs is determined by which is designated as the management network. Confusingly, Dolby DSS servers do not use the same management LAN / media LAN division of duties that most other servers do. They don't even use the industry standard terminology for naming the NICs: instead of management and media, it's auditorium and theatre (this is one of the few things I don't like about DSS servers). In a DSS200, the theatre network is designated as the management network by default, but you can change this in the configuration settings (ctrl + alt + F1, then log in as config).

Only the designated management network can be used to connect a TMS or the actual Show Manager client running on a PC on the LAN to, and, if you're running version 4.9 and are using this feature, to send automation commands over IP into the DSS.

Both networks can be used for VNC access, FTP content transfer, and to send outgoing automation commands from the server to a projector and/or a Dolby audio processor.

I guess that the intention is that the theatre LAN be used for content transfer and for a TMS to monitor what the server is doing, push playlists and schedules, etc.; and that the auditorium LAN be used for operator VNC access, secure key transfers, and automation functions between the DSS, the projector, and the audio processor.