No announcement yet.

Album art download for networked files

  • Filter
  • Time
  • Show
Clear All
new posts

  • Album art download for networked files

    media pc is networked to the server
    try to "get album art" from media pc to load onto server but will not work
    i opened up all permissions to all users on the directory with music
    i go to the server and try the same thing locally and it works as normal
    the problem is you cannot get album art for network files
    Why? How to fix? any help with much thanx

  • #2
    winamp really isn't good for art imo anyway. try a utility like album art aggregator.
    PENN STATE Radio or
    BUG #1 = Winamp skips short tracks
    Wish #1 = Multiple Column Sorting
    Wish #2 = Add TCMP/Compilation editing


    • #3
      I am guessing you have a network file rights issue.

      What happens if you try and update the MP3 tags to those files? Does that also fail?

      Can you "drag and drop" new files into that network folder from the client PC?

      If the answers to the above is "no", I need to know a little more about the OS on the server. What OS is it?

      Basically - you need to make sure that not only is there WRITE access to the network share for the username on the Media PC. But you must also make sure that the username of the Media PC also has WRITE access to the folder itself (Right click the folder, and check the Security tab)

      I can walk you through this if needed. Just let me know the OS of the PC acting as the server and the username that you have on the Media PC.


      • #4
        It could also be a filename issue. Some programs don't like the \\mycomputer\myshare type of filename. The solution is to map the share on the other computer to a drive letter. Like \\mycomputer\myshare becomes Z:


        • #5
          hey thanx for the replies. it was a permissions thing. but it was really tricky because i set the permissions under the sharing tab but not the security tab... this was a big mistake... make sure to go to the security tab and add "Everyone" and give that full control but be sure only to do this in a fully secure network


          • #6
            oh and one more thing... this will only do this for the current directory so make sure to apply it to the child directories as well


            • #7
              FREAKING HEADACHE! but its awesome when its working


              • #8
                If you think about it, your actions make sense. You have given rights to users on the local PC to access the files via the Security Tab.

                And you give rights to network users via the Sharing tab. Those then work together.

                This way it allows you to allow a locally logged in user more rights when they are sitting on the PC, and less rights when they are logging in remotely.


                Notice you don't need to set it to "everyone", as long as you know the usernames of the PCs logging into your network.

                For example: I have a user "Mark" and a user "Debs" in the house. When Debs connects from her laptop, it uses the laptop User of "Debs" to connect. As long as I have a user called "Debs" setup on the server, with the SAME password as the laptop, then I can set different rights for "Debs". (I do this to allow READ-ONLY access for Debs, but WRITE access for Mark)

                You should be able to get the rights to propagate down the permissions tree automatically.


                And for bonus points... when I set up the "Mark" and "Debs" user accounts on the server, I use the User Manager to change the user groups they are in. I remove them from the group called "USERS" or "ADMINISTRATORS" so they are actually in NO local groups. This stops accounts from being created on the server, and avoids the username appearing on the login screen of the server.

                I then go to my Music Folder on the server and add "Debs" and "Mark" into the music folder's Sharing and Security tabs. I set "Mark" to have full WRITE access, and leave "Debs" on "READ" access.

                This solution now means I have direct control over what each user can do without letting those users login to my server.

                (In this case the "server" can be a simple XP Pro PC. In reality I use Server 2003, soon to upgrade to Server 2008. Principle is the same though)