Estudio "Login" SMTP authentication and Server 2008 R2 Enterprise

[mikecom128]

Hi,

We have many multifunction devices on our network setup for Scan to Email. Two days ago we upgraded our secondary DC to 2K8 R2 from 2003 R2. Since then all clients are failing authentication at the stage of logging on to the device. The touch panel will just prompt for password again and we get the error D001 in the Message Log in the web interface.

This effects our Toshiba Estudio copiers, but works fine for our Konica MFDs that are setup using the exact same server details.

We have authentication method for Scan to Email setup as SMTP with "Login" authentication set for our SMTP server. On this server the System Event Log is filled with SMTPSVC warnings stating "The server was unable to logon the Windows NT account 'username' due to the following error: The stub received bad data. The data is the error code."

Can anyone confirm that these devices using the "Login" type authentication would fail to pass the 2K8 Group Policy of preventing 3rd party devices using weak cryptography algorithms as per Symptom 4 in this MSKB Article: The Net Logon service on Windows Server 2008 and on Windows Server 2008 R2 domain controllers does not allow the use of older cryptography algorithms that are compatible with Windows NT 4.0 by default

Any help would be much appreciated.

[mikecom128]

I have just tested logging in with DOMAIN\username and I am authenticated and can scan to email. Is there an option to prompt for Domain in SMTP method authentication for scan to email?

Hi,

We have many multifunction devices on our network setup for Scan to Email. Two days ago we upgraded our secondary DC to 2K8 R2 from 2003 R2. Since then all clients are failing authentication at the stage of logging on to the device. The touch panel will just prompt for password again and we get the error D001 in the Message Log in the web interface.

This effects our Toshiba Estudio copiers, but works fine for our Konica MFDs that are setup using the exact same server details.

We have authentication method for Scan to Email setup as SMTP with "Login" authentication set for our SMTP server. On this server the System Event Log is filled with SMTPSVC warnings stating "The server was unable to logon the Windows NT account 'username' due to the following error: The stub received bad data. The data is the error code."

Can anyone confirm that these devices using the "Login" type authentication would fail to pass the 2K8 Group Policy of preventing 3rd party devices using weak cryptography algorithms as per Symptom 4 in this MSKB Article: The Net Logon service on Windows Server 2008 and on Windows Server 2008 R2 domain controllers does not allow the use of older cryptography algorithms that are compatible with Windows NT 4.0 by default

Any help would be much appreciated.

[windowtech]

We have a Buffalo Terra Station in place, and have the eStudio 3510c set to send scans to folders in the station. We recently changed the buffalo drive to have usernames and passwords; now the eStudio cannot scan to the folders. Where would one supply these credentials to the eStudio?

[ToshibaTech]

If you are using templates to scan then it will be in the copiers web interface inside of the template settings. If you are using scan to file and then remote 1 or remote 2 then the settings will be in the Web ui under save as file.

[tstahlfsu]

You will more than likely just need to supply the "DOMAIN\username" format in the authentication box when you setup the SMTP client in TopAccess. Since you appear to run the domain, why not just create a "dummy" mailbox that you can use for the copier and supply those credentials in the DOMAIN\username format?

[windowtech]

i am using the templates - where in the Web UI do I get to the configuration?

[tstahlfsu]

Click the "Administration" tab at the top, login with the password (usually 123456), click "Network" and configure the "SMTP Client"

[Drmavrick]

If it is eB2 or eB3 you can join the domain by using the SMB session settings. After that you will not need the Domain\user.