Permissions issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wseyller
    Service Manager

    1,000+ Posts
    • Sep 2012
    • 1129

    #16
    Originally posted by TheOwl
    Give IIS a try instead of the KM FTP Utility as IIS is native to Windows and should play nice with your permissions.

    NTLM is short for NT Login Manager and the different version are for the different version of the login manager:

    v1. For Windows XP and down
    v2. For Windows 2003 AD and higher, including Windows7
    v1 and v2. Allows authentication between both version of NTLM

    Now typically I would setup scan to FTP unless there was a specific need for it. In this case, I would definately be moving to Scan to SMB, creating a user on the local PC for the copier to use and pushing files that way. Don't forget to set the account to never expire.

    As stated before, Everyone is a Security Group and not a user and you should be able to see that you can remove the Everyone security principal from indvidual files manually anyway.

    Don't forget that FTP running on anonymous is extremely dangerous as it opens up the computer to give up information with no challenge to a potential threat at all. Stick with SMB as it is a lot more secure and doesn't require extra software to run.
    Smb is how it was setup previously but something changed and I now could not get it to work. I created another admin account for this but did not help. Kept getting Forward TX error which is rare to see with smb issue. Knowledge base has an explanation saying not to use a blank password. My laptop works with only ntml v2 on this particular copier but 99% percent of time the km copiers work with smb on ntml v1 with win7 or 8. In fact with this same model it works on my laptop fine set to ntml v1 when I do setups. Only time I had to set to ntml v1/v2 in the field was with one windows 7 PC and some macs and some server OS.

    I requested an assist from our IT engineer.

    Sent from my DROID BIONIC using Tapatalk

    Comment

    • aiam
      Technician
      • Oct 2013
      • 15

      #17
      Re: Permissions issue

      this thread brings me back memories, and that's why, if you can, try the same configuration you have for that pc, in another one, with the same operative system, and check if it all works out. try even the smb scanning in other pc.

      im sayin' this because i had setup smb scan in a windows xp and it worked great until the customer's antivirus expired, and something change, malware, virus, even the antivirus that expired ? until today i dont know what happened, what i know is, after format the hard drive and installed windows once again, problem solved..

      Comment

      • wseyller
        Service Manager

        1,000+ Posts
        • Sep 2012
        • 1129

        #18
        Originally posted by aiam
        this thread brings me back memories, and that's why, if you can, try the same configuration you have for that pc, in another one, with the same operative system, and check if it all works out. try even the smb scanning in other pc.

        im sayin' this because i had setup smb scan in a windows xp and it worked great until the customer's antivirus expired, and something change, malware, virus, even the antivirus that expired ? until today i dont know what happened, what i know is, after format the hard drive and installed windows once again, problem solved..
        I don't doubt it. I know something is weird on this PC. I can scan to another PC but the customer requires this particular PC to work. Only software firewall i found was windows which I disabled. They had av software which I disabled temp. Formatting the PC is beyond the scope of all this unless the customer wants to pay to have it done.

        Sent from my DROID BIONIC using Tapatalk

        Comment

        • aiam
          Technician
          • Oct 2013
          • 15

          #19
          Re: Permissions issue

          Originally posted by wseyller
          I don't doubt it. I know something is weird on this PC. I can scan to another PC but the customer requires this particular PC to work. Only software firewall i found was windows which I disabled. They had av software which I disabled temp. Formatting the PC is beyond the scope of all this unless the customer wants to pay to have it done.

          Sent from my DROID BIONIC using Tapatalk
          of course, i was saying for you to try just to confirm or not if another pc works with the same configuration, if so, show it to the customer and leave the decision with him, because trying to understand a buged pc and get it right with network malfunctions it's like trying to stop a train without breaks coming towards you at full speed, you will get hurt and brain damaged

          Comment

          • slimslob
            Retired

            Site Contributor
            25,000+ Posts
            • May 2013
            • 37240

            #20
            Re: Permissions issue

            Originally posted by wseyller
            Smb is how it was setup previously but something changed and I now could not get it to work. I created another admin account for this but did not help. Kept getting Forward TX error which is rare to see with smb issue. Knowledge base has an explanation saying not to use a blank password. My laptop works with only ntml v2 on this particular copier but 99% percent of time the km copiers work with smb on ntml v1 with win7 or 8. In fact with this same model it works on my laptop fine set to ntml v1 when I do setups. Only time I had to set to ntml v1/v2 in the field was with one windows 7 PC and some macs and some server OS.

            I requested an assist from our IT engineer.

            Sent from my DROID BIONIC using Tapatalk
            I believe that Windows 7 SMB requires the use of both a login name and password. I usually setup a user called scanner with a password of scanning and give it permission to the scans folder only.

            Comment

            • TheOwl
              Service Manager

              Site Contributor
              1,000+ Posts
              • Nov 2008
              • 1732

              #21
              Re: Permissions issue

              Check to make sure that the network is set to "Home" or "Work". If it is set to "Public", then the file sharing services are shut down right down.

              While I understand that another computer is currently connected and able to use a share from your problem computer, I reckon that the network site on the computer has changed.

              If you go in to the Network and Sharing Center, you will find most of the sharing settings on the left and you will also be able to verify the connected network type.
              Please don't ask me for firmware or service manuals as refusal often offends.

              Comment

              • peter42
                Trusted Tech

                100+ Posts
                • Jan 2012
                • 110

                #22
                Re: Permissions issue

                Be shure, that the scan-folder is not on desktop or own files.
                Create a scanfolder on root, f.ex. "c:\scan"
                With ftp you can reach any folder on the pc.
                But with windows sharing, there are some restrictions on user-folders, specially since W7 and W2003.

                Comment

                • wseyller
                  Service Manager

                  1,000+ Posts
                  • Sep 2012
                  • 1129

                  #23
                  It seems with this same ftp setup it creates the lock on other PCs. I spent some time in our demo room at the office and it does the same thing. Seems ftp utility is the culprit. Its fine if scanning a workstation that isn't sharing this resource. I uses a different ftp server utility and it does not create the lock and it still retains everyone permission. I am going to deploy this on my customers PC.

                  Sent from my DROID BIONIC using Tapatalk

                  Comment

                  • Hansoon
                    Field Supervisor

                    Site Contributor
                    2,500+ Posts
                    • Sep 2007
                    • 3367

                    #24

                    (download link at the bottom of the page)

                    Hans
                    “ Sent from my Intel 80286 using MS-DOS 2.0
                    https://www.copytechnet.com/images/smilies/biggrin.png

                    Comment

                    • TheOwl
                      Service Manager

                      Site Contributor
                      1,000+ Posts
                      • Nov 2008
                      • 1732

                      #25
                      Re: Permissions issue

                      If you must use FTP, then I wouldn't go past IIS which is an in built service that can be run on a Windows XP Pro computer and all versions of Vista onwards (Including the server systems).

                      Then you can get Windows to set the permissions correctly and avoid using anonymous accounts.
                      Please don't ask me for firmware or service manuals as refusal often offends.

                      Comment

                      • RollingROARANDA
                        Technician
                        • Nov 2012
                        • 72

                        #26
                        Re: Permissions issue

                        There are 2 sets of permissions for SMB with Windows.

                        Sharing

                        NTFS


                        Sharing just covers Read,Write, And Full , I compare it to "network visibility" basically they can create and open files on the share if these are set correctly, Full should grant Delete.

                        However..
                        NTFS is Security and Ownership, which is in the Security tab in the folder properties.

                        It can get difficult troubleshooting ACL's (access control lists),
                        but to shed some light, "Everyone" is a group best meant for Sharing, not NTFS permissions.
                        Also, "modify" ntfs setting should allow the account or group the right to rename a scan file. In most cases, this is very sufficient.

                        Try applying NTFS acl's in the broadest most manageable sense possible; and use the Effective Permissions tab in the Advanced menu in the Security Tab in Properties to view how restrictions and rights are currently applied.

                        If this is not a server, but a workstation pc, create a user account on that PC, and on the client workstation browse the share, and enter serverPC\useraccount and save the credentials. In that kind of environment, Everyone in NTFS with modify set is the way to go.

                        Comment

                        Working...