SMB Scan to Desktop Question Ricoh/Savin on a Domain

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Vulkor
    Senior Tech

    500+ Posts
    • Jun 2009
    • 946
    #1

    SMB Scan to Desktop Question Ricoh/Savin on a Domain

    Have a customer with a Savin C3535 that was scanning to many desktop PC's Windows XP etc. They were using a domain account just called maproom2
    In the address book I had all scan destinations using maproom2, not maproom2@domain.local

    Today I had to go out there because suddenly scanning to desktop was failing randomly. Turns out it had been a problem for a while and their "new IT" guy claimed he didn't change anything. He did, I am sure, still can't figure it out.
    Old config
    C:\Scan
    shared as Scan, user access to Everyone, Full Access
    NTFS Persmissions were Everyone, Full Access along with Administators etc.

    This worked fine.

    Today I had to make new user accounts on the LOCAL PC's and the Everyone Permission on the Share and the NTFS still wouldn't allow scans through. I had to add the new account to the NTFS permissions for the scanning to work.

    Any reason why that may be??

    Any if I were to use the domain login credentials for each PC how would that look on the MFP
    Example:

    Customer Login screen
    Shelly.Long
    Password
    Domain=chicken

    would the user login name be entered as chicken\Shelly.Long or Shelly.Long@chicken.local ??
    Tags: access, account, accounts, address, address book, book, c35, c353, change, credentials, customer, desktop, email, fine, full, group policy, local, login, permission, ricoh, savin, scan, scan destinations, scan to desktop, scanning, scans, smb, user, windows
    • Paper_path
      Technician

      50+ Posts
      • Jul 2009
      • 55
      #2
      It would be chicken\shelly.long, though the other one might actually work too. I have seen group permissions act a little flaky on shares, normally I try to be as specific as possible, i.e set up a user specifically for the share and the copier. It could be that a group policy change caused the problem, or even an Server update (like a newly installed service pack.) New IT people generally tend to set up things the way they like them to be, to make it easier on themselves (it's a difficult situation to be in at times), and they will never admit that it broke anything.

        Comment

        • Vulkor
          Senior Tech

          500+ Posts
          • Jun 2009
          • 946
          #3
          Very true, Thanks Paper_Path for taking the time to reply.

          I eventually made a account just for Scanning, on each PC while they were logged into the Domain. Guessing that won't be effected by IT since it isn't part of the Active Directory. Little insecure setup to be allowing a user to create an account on their machine though. But since most of them have no clue how to find out what accounts are on their pc or changing a login at the login prompt it should be safe.

            Comment

            Previous template Next
            Working...