Toshiba e351c and Server 2012

Collapse
X
Collapse
+ More Options
Posts
 
  • Time
  • Show
Clear All
new posts
  • vttech

    #1

    Toshiba e351c and Server 2012

    I'm trying to setup a Toshiba e-studio 351c to scan to a folder on Server 2012. I have tried everything listed below but still no luck

    - Created a user (called it ebridge) with admin rights
    - Assigning full access to Everyone for the shared folder for sharing and security settings
    - Moving the shared folder to the root of C drive on the server
    - Joining the 351c machine to the domain
    - Disabling Digitally Sign Communications in Group Policy (tried Always and then both Always and Client)
    - Disabling Domain member: Digitally encrypt or sign secure channel data (always)
    - Disabling SMB Signing of Server and Client on the 351c SMB settings


    Still get the following error and I don't think the machine is able to join the domain either; machine creates 3 PDF files of 0kb for each scanned page. Firmware is T410SY0U355
    DOC083013 Save as file 08/30/2013 12:27:09 ST333B Failed to create file
  • zapcruiser

    #2
    Re: Toshiba e351c and Server 2012

    I had the exact same problem on a Toshiba e-Studio 255SE yesterday. Scanning to Server 2012 resulted in "Failed to create file" and three 0kb files. The fix that finally worked for me was a firmware update. After that it immediately went through. Another suggestion that I read fixes that issue is using UPN for login name (e.g. username@domain.com) instead of domain\username.

    Comment

    • slimslob
      Retired

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

      #3
      Re: Toshiba e351c and Server 2012

      Originally posted by zapcruiser
      I had the exact same problem on a Toshiba e-Studio 255SE yesterday. Scanning to Server 2012 resulted in "Failed to create file" and three 0kb files. The fix that finally worked for me was a firmware update. After that it immediately went through. Another suggestion that I read fixes that issue is using UPN for login name (e.g. username@domain.com) instead of domain\username.
      Treat Server 2012 the same as Windows 8 when it comes to scan to SMB. What firmware update that is needed for Win 8 is also needed for Server 2012. Both use SMB 3 which is not fully backward with SMB 2. One of the many MS mistakes with Win 8 that they do not plan to correct.

      Comment

      Working...