Utax DC 6240 SMB error 1105

[numarkDM1050]

Hello. I have the following problem with the Utax 6240.

I bought a used Utax 6240 for an accounting firm because their work is increasing and they need a second Utax 6240.
The new one has a touchscreen display. The old 6240 has a smaller display without a touchscreen.
The problem I have is with scanning via SMB.
Both machines are on the same local network with static addresses and settings to scan to Synology with username and password.
The old machine has no problem with scanning, but the new one gives error 1102. I tried with several users, but it gives the same error for all. The SMB settings are identical on both machines. I decided to change the port from 139 to 445. It still gives an error and I returned port 139. I decided to create a shared folder on Windows 11 and check if a scanned document will be sent there (maybe the problem is in the NAS...). I added a user to the address book on both machines to scan to a shared folder on Windows 11. The old machine scans and sends a document to Windows 11, but the new one gives an error again. After a while, I decided that it would be better to do a factory reset on the machine and then do everything from scratch. I did that and I still couldn't scan over the network. I decided to try scanning over the computer. I downloaded the Naps2 software and TWAIN drivers from the Utax website. After installing them and adjusting the settings, I could scan through the ADF or the glass without any problems and the document would go to the Naps2. I came across a person on the internet with a similar problem and his solution was to limit the network card to 100MB/S half duplex. I tried all possible options 10, 100, 1000 full or half duplex, but it didn't work. The only thing I haven't tried is installing a newer firmware. I decided to give it a try, but there is no firmware download section on the Utax website.
MODEL: CD 5240_DC 6240
VERSION: 2MD_2F00.E08.051
If anyone has anything else in mind, please share it because I can't think of anything else.

[PrintWhisperer]

Title says 1105 but post says 1102 so which is it? 1105 says SMB not enabled so did ya do that? Enable SMB

1102 failure to connect to host can be several reasons, but nothing to do with MAC speed.
1) Disable NetBIOS (SMB1 PORT 139) - Host will not connect to a system with lower level of protocol where session can be renegotiated to insecure version.
2) Always use port 445. Port 139 not supported in Windows due to above.
3) Port 445 requires DNS to negotiate resource connection even when DHCP is not in use - set Primary DNS source to match a working device.
4) In the Address book entry, set the PATH to the sharename of the folder you are connecting to (SHARE ROOT - NOT sub-folder). Use no slashes just the exact case-matched sharename.
Some firmware versions on old machines had a path problem using subfolders - IDK what that model is in America.

[numarkDM1050]

I messed up the title. It should be 1102.

Thanks for the suggestion and I tried but it still doesn't work.
I tried setting the DNS to google 8.8.8.8, to the router 172.18.4.1, to the shared device 172.18.4.4 still error 1102


Screenshot 2025-05-28 090801.png

[KYO_OEM]

no newer FW available
SMB v2/3 problem fixed with the current installed version.
But this is not your problem...
Take care for the kyo service manual explanation regarding 1102
SMB.jpg

[numarkDM1050]

After several hours of trying to scan, I decided to do the following:
I created a new user Ivo with password 1. I created shared folders named Scan and 1. This user, password, and shared folders are on Windows 11, Windows 7 x86, and Synology NAS. On all three devices, the old machine scans, but the new one gives an error.
I know that the error it gives is for an incorrect username, password or directory but it seems to be something else. It strikes me that immediately after scanning it gives the error. On other such machines it tries for 5 - 10 seconds to connect and then gives an error.

[ATM]

Is backslash required in share name? I know it's not required in Kyocera devices. At least not in the newer devices.

[numarkDM1050]

On the older machine it requires it. However, I tried it and the result is
error 1103 with backslash
error 1102 without backslash or with normal slash.

[PrintWhisperer]

I tried setting the DNS to google 8.8.8.8, to the router 172.18.4.1, to the shared device 172.18.4.4 still error 1102

No you cannot use public DNS to resolve internal hosts and shares.
Your router @172.18.4.1 should be used, or the DC if you have one. Place Domain name in general settings so authentication occurs against domain as Domain/User.

If no Domain, use NAS for DNS (if enabled) and NAS host as domain to auth against.
I cannot see that NetBIOS is disabled.

[numarkDM1050]

They don't have DC. Net BIOS is disabled and keeps giving the same error 1102. Thanks for the suggestion, I tried it but it didn't work.
Domain Name: Synology_Nas
Domain Name: Synology_Nas\Ivo
Domain Name: Synology_Nas/Ivo
I also tried with a shared folder on a Windows 7 computer,
Domain Name: Ivo-PC\Ivo
Domain Name: Ivo-PC/Ivo
I also tried with Workgroup it doesn't work either.

[PrintWhisperer]

If you have no domain then you are authenticating against the local user list in the Synology NAS where the share is located. So the NAS hostname would be used as the 'domain name' in a 'workgroup' scenario.
However it is hard to predict how the NAS handles authentication.

1102 will occur from : No logon servers, Domain not found, Account lockout or other authentication/connection failure

Ultimately only a network trace will show the exact SMB failure. That requires a device to tap the connection such as a SharkTap or Port mirroring switch.(`$200)

This is an old failure which occurred AFTER logon in the PATH construction, the one which was fixed with firmware. It shows how the logon information is used:
SMB_Session.png

[numarkDM1050]

I agree that traffic monitoring will help us understand the exact cause of the error. Two days ago, a colleague and I discussed this option, but we came to the conclusion that even if we find out exactly where the packet is broken, it will not solve the problem. We both agree that the problem is in the firmware, and there are neither new nor old firmware on the UTAX website.
I will analyze the traffic with Wireshark, but it will take me more time because I have to take the printer from the accounting office and put another one in its place. At the same time, I have other urgent tasks.
Today I was considering a slightly more radical approach. I was considering taking a board from another working printer and using a TL866II programmer to download the software from the chip. The bad thing is that I have a vague memory that the chip is nand, not eeprom. If it turns out to be NAND, I'm screwed. I don't feel ready to reball the nand chip.
In any case, I will keep you updated.

[PrintWhisperer]

Your Domain Name field has an IP address in it (BAD) and you have no DNS entry.
The system will prepend what's is the User field with what's in the Domain field.
So you are auth'ing as 172.18.4.1\USERNAME

With no Domain, leave it blank.

Since the NAS has the share and is apparently not sync'd to AD you must authenticate with User/PWD created on the NAS.

PATH is case sensitive, browse for the NAS share from a PC to verify the sharename which is broadcast and use the Username and Password to connect a PC to the share to verify.
Only use SHARENAME in PATH field for testing, no sub-folders.
Do not use spaces in sharenames.

Your machine US equivalent appears to be an FS-1135, the 'other machine is likely FS-1128 or FS-1035 (NOT the same)

Wireshark will show you errors like this. It's not a broken packet, but incorrect usage of the protocol due to settings.

Mess with PWB's and trying to program the device on your own will likely brick it. Reload proper firmware with the correct method if that's your intent. The FW version shown is a bit irregular with the 'E' designation, that usually means 'experimental' special purpose FW.

[numarkDM1050]

I'm uploading a dump file from Wireshark. I noticed that it gives the following error: STATUS_FS_DRIVER_REQUIRED
I'm still reading what this error is and what causes it.

Link: https://limewire.com/d/MDguE#IbmS5F2cBg

[PrintWhisperer]

Its DFS driver (distributed file system). A standard SMB response code for not having dfs enabled. It should be built-in on the Kyocera, but may be optional on the Synology.

• Article
• 04/07/2025

When the server receives a request with an SMB2 header with a Command value equal to SMB2 IOCTL, and a CtlCode of FSCTL_DFS_GET_REFERRALS or FSCTL_DFS_GET_REFERRALS_EX, message handling proceeds as follows:

If IsDfsCapable is set to FALSE, (check Server Hello and Client Hello) the server MUST return STATUS_FS_DRIVER_REQUIRED to the client.

[PrintWhisperer]

I finally got a chance to look over your Wireshark, and it looks like a Test Connection and not an actual file transfer attempt. Packet 61 has the Server response of Status_Success for the listed UNC path to the share.

Everything in it is typical and you are successfully locating the share, authenticating and gaining Read-Write Access in the Capture. At the point when a File transfer would occur, the machine issues a Tree Disconnect request as if it never intended to transfer a file.


The DFS thing is actually not supported on the Kyocera but SMB works without it. Attached is a side by side comparison with a similar successful SMB2 scan process.

If you are trying to send a file in that capture, no error is shown. The only conflict at this point would be file name duplication but there is no indication of that. Just to be sure, set the default filename to append a date-time stamp.