AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() Sorry all i get when i run that command is this Think you misunderstand i do have access to SSH and always have done. If Port Trunking is present please specify (choose correct one): none Your Operating System you are using to access your NAS. Sorry please see the information that you requested below.sorry about the delay getting back to you Please provide answers to these questions, and please provide the internal IP address of your NAS. Please review article: When you're asking a question, please include the following. I'm be happy to help, but you have provided no information for me to work with. It is nearly impossible to troubleshoot this without SSH. ![]() After installing transmission and getting it to listen on 9091 I was able to get on transmission but then I got err_connection_refused on twonky port 9000 and quite a few other ports to ie 3269 itunes/firefly and the actual administration page, where I set transmission up port 8081 if my memory serves me correctly. Please do not say use Plex I have Plex on a server but I think the quality of plain old DLNA is much better and I want to get to the root of the problem.Ĭraigkew wrote:I know how to ssh on to the box but I don't really know linux. My next step is to do a back up of the NAS and reset the whole thing, but I think it is something fairly simple to someone who knows there way round linux and am hoping while I am in the process of backing up my data someone comes up with an answer and saves me putting all my data back on it re-adding it to the domain and basically spending a week getting it back to where it was before I installed transmission. Since this I have uninstalled all apps and I was again to access the built in firefly on 3269 but have uninstalled reinstalled twonky on several occasions enabled re-enabled DLNA and still just get err connection refused. I know how to ssh on to the box but I don't really know linux. Create the Playlist within the MediaMonkey app, then save as a. Local files relative, (I'm guessing relative to Playlist location.). Global root for UNC paths, fully qualified drive and path for local files, "export" functionality in sub menu, "linking" application playlist with on disk playlist, "Use Relative Paths" OFF by default, "Use Extended M3u" Global root for UNC paths, automatic export to "my documents/my music/my playlists" not settable All items fully qualified drive and path for local files, "export" functionality in sub menu The playlist file will have to be scanned by the UPnP server software (such as Twonky), before it is displayed on the GUIĬreates playlists at global root for UNC paths. M3Ufile and is saved in the same root folder as the Music. The following table lists the behaviours of common playlist creation toolsĮnsure that the Playlist is saved as a. Out of the ones listed here, only Media Monkey defaults to relative paths. Those playlist tools that do allow relative paths, default to absolute paths. ![]() Most playlist creating tools default to producing playlists with absolute links to items. This will affect playlists where absolute paths are used The Samba view is where the Playlist creation tool will run, but Twonky must use the "Linux view". The same files will also be available over a SAMBA view (on Windows clients). For example a media library on a NAS with Twonky installed will have a "Linux view" that is used directly by Twonky. Twonky is agnostic to "\" or "/" dir separators, however it cannot "fix" mappings between diffferent views of the same file system. ![]() This makes Twonky sensitive to where you upload any playlists with relative references. ![]()
0 Comments
Read More
Leave a Reply. |