Konica Minolta BizHub C3350 - Scan to Folder Stopped Working

[Distorted Vision]

Good morning ChatGPT.

Following the in-line repair of Windows 11 the scan to folder has stopped working on the Konica Minolta BizHub C3350.
The scan to folder on the Canon I-Sensys MF752CDW also stopped working. But I got it working by re-creating the folder share and permissions etc. Also the password had expired for user account: Scanner. So I changed it using net user.

It has stopped working on the C3350 before a few times. Last time I resolved it by creating a new folder. But it hasn't worked this time.
The shared folder is:

C:\Scans-Konica

In Properties->Sharing->Advanced Sharing->Permisions

 

[ChatGPT]

Good morning — thanks for the screenshots and details. This looks like a classic SMB/credentials mismatch between the Konica and your Windows share. Below are targeted checks and quick fixes (in order) so we can pinpoint why the C3350 won’t write to C:\Scans-Konica while your Canon could be coaxed back to life.
Short checklist (what I’ll have you try)
1) From a PC on the same LAN, test access to the share with the same credentials the printer uses (quickest single test).
2) If that fails, look at the Windows Security log for Event ID 4625 at the failure time and paste the Status/SubStatus.
3) If mapping succeeds, try three Konica settings tweaks (username format, file-path format, default domain) and retest.
Step‑by‑step (with exact commands and what to expect)
1) Test the share from a PC (use the exact username/password the Konica has)

• Open an elevated Command Prompt or PowerShell on any PC and run:
  net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner YourPasswordHere
  (replace IP, share name, machine name and password)
• Expected results:
  • If it maps and you can create a test file, the Windows share and credentials are OK (problem is Konica settings).
  • If it fails, note the error and check Event Viewer → Windows Logs → Security for Event ID 4625 at that time. Paste the 4625 Failure Reason and Status/SubStatus here — that tells us exactly why Windows rejected the login. (Common codes: 0xC000006A/0xC000006D = bad password, 0xC0000064 = wrong username, 0xC000015B = not allowed over network).

2) Confirm NTFS + share permissions on the PC

• Run these in an Administrator PowerShell and paste the outputs:
  Get-SmbShare -Name 'Scans-Konica'
  Get-SmbShareAccess -Name 'Scans-Konica'
  icacls 'C:\Scans-Konica'
• For the Scanner account you must see a Share permission allowing Change/Full and an NTFS entry granting Modify (or at least Modify) to PATRE‑DESKTOP\Scanner. The screenshots show the Scanner account in Share Permissions — but Share + NTFS both must allow write.

3) Konica address book fields — try these exact changes

• On the Konica Remote UI (Address Book entry) try each of these one at a time, test a scan after each change:
  A) Username format
  • Currently you have User ID = Scanner. Try instead:
    PATRE-DESKTOP\Scanner
  • If that fails, try just Scanner (if you change Default Domain below it may be redundant).
  B) File Path format
  • Change File Path from \Scans-Konica to Scans-Konica (no leading backslash). Some MFPs want the share name only, others accept a leading backslash — try both. Also try leaving File Path blank and put \192.168.0.26\Scans-Konica in Host Address (some firmwares prefer a full UNC in Host). Canon/other devices often accept either Host=IP + Folder=Scans or Host=\IP\Scans and Folder blank. The Konica behaves similarly. fileciteturn0file12turn0file8
  C) Default Domain Name / Authentication mode
  • In Network → SMB Client Settings set Default Domain Name = PATRE-DESKTOP (so username "Scanner" maps to the local machine).
  • Authentication: your screenshot shows NTLMv1/v2 — try NTLMv2 first. If the device fails with NTLMv2, switch to NTLMv1/v2 (some older firmware needs the mixed setting).
  • Make sure SMB Client is Enabled. Save & Apply, then retry.
  D) Ensure the Konica has the updated password saved
  • In the address book entry check “Change Password” and re-enter the current password for Scanner.

4) Windows firewall / SMB server checks

• Ensure the PC network profile is Private and that File and Printer Sharing inbound rules for Private are enabled.
  Get-NetConnectionProfile | Format-Table Name,NetworkCategory
  (If it’s Public, set it to Private.)
• Make sure the Windows “Server” service is running (so the machine accepts SMB):
  sc query lanmanserver
• If you changed the Windows account password recently, the Konica must have the new password — otherwise you’ll see repeated 4625 events.

5) If the map test from step 1 fails, share the 4625 details

• Post the exact Event 4625 lines (Account Name, Failure Reason, Status and SubStatus) that occur when you try to scan. That tells us whether it’s “expired password”, “bad password”, “unknown user”, or “not allowed to log on over the network” and points to the single setting to change.

Quick likely fixes based on what you’ve shown

• Set Default Domain Name = PATRE-DESKTOP on the Konica and keep User ID = Scanner (so the printer sends the username to Windows as the local account). If that doesn’t work, set User ID to PATRE-DESKTOP\Scanner instead. Try both File Path formats (Scans-Konica and \Scans-Konica) or put the entire UNC in Host Address. Then be sure the password field on the device has the current password.

Security note

• If this Scanner account is local and you don’t want it to expire again, you can set PasswordNeverExpires, but that has security implications. A safer enterprise option is a managed service account (gMSA) if you’re on a domain. Otherwise document the shared password in a password manager.

If you want, do this now and paste results

• The results of:
  net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner YourPassword
  Get-SmbShareAccess -Name 'Scans-Konica'
  icacls 'C:\Scans-Konica'
• Or paste the 4625 event details after a failed Konica attempt.

I’ll read those and tell you exactly which single field to change on the C3350 (username/domain/file path/auth setting) to make it stop failing.

 

[Distorted Vision]

From PATRE-Laptop:

PS C:\WINDOWS\system32> net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner ********
System error 67 has occurred.

The network name cannot be found.

PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — that System error 67 is the clue. In your net use line you used a single backslash instead of a double backslash, so Windows never saw a UNC path. System error 67 = "The network name cannot be found" (usually wrong UNC, wrong IP, or the Server/SMB service or firewall blocking).
Do this (fast checks, in order)
1) Re‑run the correct mapping command (don’t paste your real password here)

• In PowerShell / CMD run exactly (replace the password text with your actual one):
  net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner YourPasswordHere
  OR (PowerShell, quote the UNC)
  net use "\192.168.0.26\Scans-Konica" /user:"PATRE-DESKTOP\Scanner" YourPasswordHere
• Expected:
  • Success → you can create a file and the share/credentials are OK (problem is Konica settings).
  • Same error 67 → continue to step 2.

2) Quick reachability tests

• Ping the host:
  ping 192.168.0.26
• Test SMB port (PowerShell):
  Test-NetConnection -ComputerName 192.168.0.26 -Port 445
• If ping fails: the PC at .26 is unreachable (wrong IP or host offline).
• If ping works but port 445 is Closed: SMB server or firewall is blocking.

3) Check the share actually exists and server is listening (run on PATRE‑Laptop)

• Confirm the share exists:
  Get-SmbShare -Name 'Scans-Konica'
• Confirm the Server service:
  sc query lanmanserver
• Confirm Server is advertising and you can see shares from Explorer:
  In File Explorer, press Win+R and type \192.168.0.26\ and press Enter — do you see Scans-Konica listed?
• If Get-SmbShare fails or the share is not listed, recreate the share and permissions.

4) If port 445 is closed or UNC browse fails — check firewall & network profile

• Confirm network profile is Private:
  Get-NetConnectionProfile | Format-Table Name,NetworkCategory
  If it shows Public, set it to Private (replace interface name):
  Set-NetConnectionProfile -InterfaceAlias "Wi‑Fi" -NetworkCategory Private
• Ensure File and Printer Sharing rules are enabled for Private:
  Get-NetFirewallRule -DisplayGroup "File and Printer Sharing" | Format-Table Name,Enabled,Profile
  (If rules are disabled, enable them for Private.)

5) If mapping from the laptop works but Konica still fails

• On Konica try the variations I suggested earlier:
  • In Address Book: User ID = PATRE-DESKTOP\Scanner (or set Default Domain = PATRE-DESKTOP and User ID = Scanner).
  • Try File Path = Scans-Konica (no leading backslash) and also try Host = \192.168.0.26\Scans-Konica with File Path blank.
  • Authentication: NTLMv2 preferred; if that fails use NTLMv1/v2. Ensure SMB Client = Enable and the password saved on the device is current. fileciteturn0file12turn0file8

What to paste back here

• Result of the corrected net use command (success or exact error text).
• Outputs (or copy/paste) of:
  ping 192.168.0.26
  Test-NetConnection -ComputerName 192.168.0.26 -Port 445
  Get-SmbShare -Name 'Scans-Konica'
  sc query lanmanserver
  Get-NetConnectionProfile

I’ll tell you the single next change to make on the C3350 as soon as you post those outputs.

 

[Distorted Vision]

Test-NetConnection -ComputerName 192.168.0.26 -Port 445

Powershell seems to hang. There was a message in blue that appeared but it disappeared and I didn't get a note of it.

 

[ChatGPT]

Thanks — the screenshots and outputs are very helpful. You can reach the laptop (ping replies), but UNC access and mapping fail (error 67) and Get-SmbShare returned “no object found” for Scans‑Konica — that tells me Windows either isn’t advertising that share or the Server (lanmanserver) service isn’t running, or the firewall/SMB listener is blocked. Let’s verify the exact cause and fix it.
Do these steps on PATRE‑Laptop in an elevated PowerShell (Run as Administrator). Don’t paste any passwords here.
1) List current shares (quick)

• Run:
  net share
• Expected:
  • You should see Scans-Konica listed. If it’s NOT listed, the share does not exist and we need to recreate it.

2) Check SMB shares via PowerShell

• Run:
  Get-SmbShare
• Expected:
  • A list of shares. If Get‑SmbShare returns nothing or an error for all shares, the Server service may be stopped.

3) Check Server service (SMB / file sharing)

• Run:
  sc query lanmanserver
• Expected:
  • You should see STATE: RUNNING. If it’s STOPPED or the command returns nothing useful, start it:
    sc.exe start lanmanserver
  • If starting fails, note the error text (paste it).

4) Check whether Windows is listening on SMB port 445

• Run:
  netstat -an | findstr 445
• Expected:
  • You should see a line with LISTENING on 0.0.0.0:445 or [::]:445. If you don’t, Server service is not listening.

5) If the share is missing — recreate it (safe, 1 command)

• From Admin PowerShell run either:
  net share Scans-Konica="C:\Scans-Konica" /GRANT:Scanner,CHANGE
  OR (PowerShell New-SmbShare):
  New-SmbShare -Name "Scans-Konica" -Path "C:\Scans-Konica" -ChangeAccess "PATRE-DESKTOP\Scanner","Administrators"
• Then verify with net share and Get-SmbShare.

6) Verify NTFS and share permissions

• Run:
  icacls "C:\Scans-Konica"
  Get-SmbShareAccess -Name 'Scans-Konica'
• Expected:
  • icacls shows PATRE-DESKTOP\Scanner has Modify (or at least Modify+Write).
  • Get‑SmbShareAccess shows Scanner allowed (Change/Full).

7) Check firewall rules if Server is running and share exists but UNC still fails

• Check network profile:
  Get-NetConnectionProfile | ft Name,NetworkCategory
  If it’s Public, change to Private (replace the InterfaceAlias if needed):
  Set-NetConnectionProfile -InterfaceAlias "Wi‑Fi" -NetworkCategory Private
• Then check the sharing rules:
  Get-NetFirewallRule -DisplayGroup "File and Printer Sharing" | ft Name,Enabled,Profile
• Enable them for Private if disabled:
  Set-NetFirewallRule -DisplayGroup "File and Printer Sharing" -Profile Private -Enabled True

8) After fixes: test mapping from PATRE‑Laptop (no GUI)

• Run:
  net use \192.168.0.26\Scans-Konica /user:"PATRE-DESKTOP\Scanner" *
  (it will prompt for the password)

What to paste back here

• Output of:
  net share
  Get-SmbShare
  sc query lanmanserver
  netstat -an | findstr 445
  icacls "C:\Scans-Konica"
  Get-SmbShareAccess -Name 'Scans-Konica'
  Get-NetConnectionProfile

If you prefer, do steps 1–3 first and paste those three outputs and I’ll tell you the exact next command. Based on what you’ve shown so far my strong suspicion is the share has been removed (or the Server service stopped) after your in‑line Windows repair — recreate the share and confirm lanmanserver is running and the Konica should be able to reach it again.

 

[Distorted Vision]

PS C:\WINDOWS\system32> net share Share name Resource Remark ------------------------------------------------------------------------------- C$ C:\ Default share IPC$ Remote IPC ADMIN$ C:\WINDOWS Remote Admin Scans C:\Users\Rupesh Patre\Desktop\Scans Users C:\Users The command completed successfully. PS C:\WINDOWS\system32> Get-SmbShareGet-SmbShare Get-SmbShareGet-SmbShare : The term 'Get-SmbShareGet-SmbShare' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + Get-SmbShareGet-SmbShare + ~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-SmbShareGet-SmbShare:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException PS C:\WINDOWS\system32> sc query lanmanserver PS C:\WINDOWS\system32> sc.exe start lanmanserver [SC] StartService FAILED 1056: An instance of the service is already running. PS C:\WINDOWS\system32> netstat -an | findstr 445 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP [::]:445 [::]:0 LISTENING UDP 0.0.0.0:53445 142.250.129.104:443

 

[ChatGPT]

Good output — that explains it.
What happened (short): your laptop currently does NOT have a share named Scans‑Konica, so the MFP’s UNC \192.168.0.26\Scans‑Konica cannot be reached. Your net share list shows a different share named Scans (on your Desktop) but no Scans‑Konica. lanmanserver is running and Windows is listening on TCP/445 (so SMB itself is fine). Create the missing share (and ensure NTFS + share permissions for PATRE‑DESKTOP\Scanner) and the Konica should be able to write to it. Also try the small Konica address‑book tweaks I list below. fileciteturn0file8turn0file12
Do this now (copy/paste as Admin PowerShell / elevated CMD)
1) Create the folder (if it doesn’t already exist)

• If you already have C:\Scans-Konica skip the mkdir; otherwise:
  mkdir "C:\Scans-Konica"

2) Create the SMB share and grant the Scanner account Change rights

• Simple command (works in Command Prompt or PowerShell):
  net share Scans-Konica="C:\Scans-Konica" /GRANT:"PATRE-DESKTOP\Scanner",CHANGE
• OR the PowerShell way:
  New-SmbShare -Name "Scans-Konica" -Path "C:\Scans-Konica" -ChangeAccess "PATRE-DESKTOP\Scanner","Administrators"

3) Ensure NTFS permissions allow writes

• Run:
  icacls "C:\Scans-Konica" /grant "PATRE-DESKTOP\ScannerOI)(CI)M"
• Then verify:
  icacls "C:\Scans-Konica"
  net share

Expect to see Scans-Konica in the net share output and icacls showing PATRE-DESKTOP\Scanner with Modify.
4) Quick test from the laptop (will prompt for password)

• Run:
  net use \192.168.0.26\Scans-Konica /user:"PATRE-DESKTOP\Scanner" *
• Enter the Scanner account password when prompted. If successful you can create a file at the UNC.

5) Konica address‑book settings to use (try one combination at a time)

• Host Address: 192.168.0.26
• File Path: Scans-Konica (try without the leading backslash first)
• User ID: Scanner AND set Default Domain Name on the Konica to PATRE‑DESKTOP
  — OR set User ID: PATRE‑DESKTOP\Scanner (if you prefer domain\user format)
• Authentication: NTLMv2 (if NTLMv2 fails, try NTLMv1/v2)
• Make sure SMB Client = Enable and re‑enter the password (check “Change Password” box on the device entry if required). If one format fails, try the other formats described above — some firmware is picky about the leading backslash or domain formatting. fileciteturn0file8turn0file12

If it still fails

• Run net use again and paste the exact error text.
• Check Event Viewer → Windows Logs → Security for Event ID 4625 at the time of the scan and paste Account Name / Failure Reason / Status and SubStatus — that will tell us whether it’s bad password, wrong user, or “not allowed over the network.”

One small extra note

• You already have a share named Scans pointing to your Desktop. That’s fine, but having multiple similar share names can cause confusion. If you don’t need the Desktop share, you can remove it with:
  net share Scans /delete

Let me know the output of net share after you create Scans‑Konica and the result of the net use test — I’ll confirm the Konica fields you should use and, if necessary, the 4625 decoding.

 

[Distorted Vision]

From PATRE-Desktop:

 

[ChatGPT]

Hi Distorted Vision — thanks for the screenshot. From what I can see the Windows share (Scans-Konica) exists and has ACLs for Everyone / Guest / PATRE‑DESKTOP\Scanner with Full control, so the share side looks mostly correct. That said, common causes when an MFP (Konica Minolta Bizhub C3350) stops scanning to a Windows share are: authentication mismatch, SMB protocol/version mismatch, firewall/port blocking, or name resolution problems. Below is a focused troubleshooting/checklist you can follow (with safe tests and how to fix each issue).
Quick checklist (try in this order)
1) Test basic network + port reachability from the MFP (or from another PC)

• From a PC on same network run:
  • Test if port 445 is open to the PC hosting the share:
  • PowerShell: Test-NetConnection -ComputerName 192.168.x.y -Port 445
  • If port 445 fails, check firewall on the PC and the network.

2) Test the share with the exact credentials the MFP should use

• On a PC, run (replace IP, username, password):
  • net use \192.168.x.y\Scans-Konica /userATRE-DESKTOP\Scanner YourPassword
• If that works, the PC is accepting the credentials and the share/NTFS permissions are correct.
• If it fails, note the exact error (access denied vs network path not found).

3) Configure the scanner to use the same credentials and use IP not hostname

• On the Bizhub SMB destination settings:
  • Server: use the PC’s IP (example: \192.168.x.y)
  • Share: Scans-Konica (or full path \192.168.x.y\Scans-Konica)
  • Authentication: specify username PATRE-DESKTOP\Scanner (or sometimes just Scanner) and the password you tested above
  • Use SMB port 445
  • For “Workgroup/Domain” try leaving blank or using the PC computer name if the device asks
• Important: use the IP address for the server when troubleshooting — this eliminates name resolution or NetBIOS issues.

4) Firewall / Windows settings to check on the PC

• Ensure File and Printer Sharing (SMB-In) inbound rules are allowed for the network profile the PC is using (Private / Domain).
  • Control Panel > Windows Defender Firewall > Allow an app or feature > File and Printer Sharing OR
  • Inbound rules → File and Printer Sharing (SMB-In) must be Enabled for TCP 445.
• If you’re on a corporate network with additional network segmentation, ensure there is no switch/router ACL blocking 445 between MFP and PC.

5) SMB version / authentication compatibility

• Many MFPs vary in supported SMB versions or authentication methods (NTLMv1 vs NTLMv2).
• Konica typically supports SMB2/3 on modern firmware, but older firmware or specific settings may fall back to NTLMv1 or require SMB1.
• Recommended approach:
  • On the MFP, in SMB settings choose SMB2/SMB3 if there is an option (or “Auto”).
  • If the MFP only supports SMB1 (rare, but possible on very old configs), DO NOT enable SMB1 on Windows unless you must — SMB1 is insecure. Instead, check Konica firmware for an update that adds SMB2/3 support.
• If the MFP uses anonymous (guest) access: Windows by default blocks insecure guest access. Prefer configuring an authenticated user (Scanner) and password. If you must use guest/anonymous, you need to enable insecure guest logons on Windows (not recommended — see step 8 below for how and the security warning).

6) Check Windows Security/Event logs to see auth failures

• Event Viewer → Windows Logs → Security and System — look for failed logon / network share access denied events at the time you try to scan. The event will often say whether the MFP attempted a connection and which account it used.

7) Confirm NTFS permissions match the share permissions

• You already ran icacls — ensure the account used by the MFP appears and has Full control at both the Share and NTFS level.
• Best practice: remove Everyone/Guest from the share (if not required) and only allow the specific Scanner account on both Share and NTFS.

Useful commands (run as Administrator on the PC)

• Show the smb share config:
  • Get-SmbShare -Name "Scans-Konica"
• Show effective share ACLs:
  • Get-SmbShareAccess -Name "Scans-Konica"
• Quick network/test command:
  • Test-NetConnection -ComputerName 192.168.x.y -Port 445
• Quick test mount from another PC:
  • net use \192.168.x.y\Scans-Konica /userATRE-DESKTOP\Scanner YourPassword

If the MFP used to work and recently stopped after a Windows update

• Windows updates may change SMB/NTLM behavior or firewall rules. If everything above passes, check:
  • Whether SMB signing or group policy requiring NTLMv2 was enabled. If the device only negotiates NTLMv1, you either need to update the MFP firmware or temporarily relax the PC policy (not ideal). The policy is:
  • Local Security Policy → Security Settings → Local Policies → Security Options → Network security: LAN Manager authentication level.
  • Lowering this reduces security; better to update MFP.

If you absolutely must allow anonymous (guest) scans (not recommended)

• Windows 10/11 blocks insecure guest logons by default. To enable temporarily:
  • Local Group Policy: Computer Configuration → Administrative Templates → Network → Lanman Workstation → Enable insecure guest logons = Enabled
  • OR registry (as admin): set HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth = 1 (DWORD)
• Security warning: this opens the host to unauthenticated SMB connections. Undo when finished.

Firmware note

• If the MFP firmware is old it may not support modern SMB/NTLM defaults. Check Konica Minolta support for a firmware update for the Bizhub C3350 which explicitly lists SMB2/3 / NTLMv2 support.

If you'd like I can:

• Walk you through the exact net use and Test-NetConnection commands if you paste the PC IP and an example username (don’t paste real passwords here).
• Suggest the exact SMB settings/menu names on the Bizhub (tell me whether you access the device web UI and what menu options you see).
• Help interpret any Event Viewer logs if you paste relevant event IDs/messages.

Next thing to try now (quick & high value)

1. From any PC on same network run: Test-NetConnection -ComputerName <PC-IP> -Port 445
2. From that same PC run: net use \<PC-IP>\Scans-Konica /userATRE-DESKTOP\Scanner <password>
3. If step 2 succeeds, configure the MFP SMB destination using Server = <PC-IP>, share = Scans-Konica, username = PATRE-DESKTOP\Scanner and same password. Try a test scan.

Tell me the results of steps 1–3 (copy any error text) and what the MFP reports when the scan attempt fails (authentication error vs cannot connect). I’ll help with the next concrete step.

 

[Distorted Vision]

From PATRE-Laptop:

 

[ChatGPT]

Good info — thanks. From your screenshots I can see a few helpful clues:

• On PATRE-Desktop the share Scans‑Konica exists and Get‑SmbShare showed the share and access for PATRE‑DESKTOP\Scanner (so that host looks OK).
• On PATRE‑Laptop your net share output shows a different share (Scans at C:\Users\Rupesh Patre\Desktop\Scans) and the attempts to create Scans‑Konica failed with “invalid value for the /GRANT option” and later “System error 2” (file not found). Also I noticed a typo when you tried Get‑SmbShareGet‑SmbShare (that cmdlet error was just the typo).

Likely root causes here are: the folder you tried to share doesn’t exist on the laptop (System error 2), incorrect /GRANT syntax when using net share, or mismatched credentials/host used by the MFP. Below are exact, safe steps to fix and test from PATRE‑Laptop — follow in order and report back any errors/output you get.
1) Make sure the target folder actually exists

• Run in an elevated PowerShell/CMD:
  • mkdir "C:\Scans-Konica"
  • dir "C:\Scans-Konica"
    (If the folder already exists you’ll see it; if not this creates it.)

2) (Optional) Create a dedicated local account the MFP will use (recommended)

• Create user (example password replace with a strong one):
  • net user Scanner "P@ssw0rd!" /add
• (You do not need to add it to Administrators)

3) Give NTFS (file-system) permissions to the Scanner account

• Grant Modify (allow subfolders/files) to the account:
  • icacls "C:\Scans-Konica" /grant "PATRE-LAPTOP\ScannerOI)(CI)M"
  • icacls "C:\Scans-Konica"
    This ensures the account can write files.

4) Create the SMB share (use correct syntax)

• PowerShell (preferred):
  • New-SmbShare -Name "Scans-Konica" -Path "C:\Scans-Konica" -ChangeAccess "PATRE-LAPTOP\Scanner" -FullAccess "Administrators"
• OR the equivalent net command (note use of computer name\user):
  • net share Scans-Konica="C:\Scans-Konica" /GRANT:"PATRE-LAPTOP\Scanner",CHANGE
    Common mistakes: omitting the host prefix (PATRE-LAPTOP), forgetting quotes when needed, or the folder not existing (System error 2).

5) Enable Windows Firewall file/printer sharing (if blocked)

• Quick command to enable File and Printer Sharing for Private:
  • netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes profile=private
• Or use Windows Security → Firewall & network protection → Allow an app → File and Printer Sharing.

6) Confirm SMB is listening (port 445)

• Test from the laptop itself and from another machine on the same network (or run below on any PC):
  • Test-NetConnection -ComputerName <Laptop-IP> -Port 445
    Expected: TcpTestSucceeded : True
    If False, firewall or SMB service blocking.

7) Test mounting the share from another PC (this simulates the MFP auth)

• From another PC run (use the IP of the laptop to avoid name resolution issues):
  • net use \<Laptop-IP>\Scans-Konica /userATRE-LAPTOP\Scanner P@ssw0rd!
  • If it connects, try creating a file in that share to verify write.

8) Configure the MFP using the laptop IP and the Scanner account

• On Bizhub use:
  • Server: <Laptop-IP> (use IP, not hostname while troubleshooting)
  • Share name: Scans-Konica
  • Username: PATRE-LAPTOP\Scanner (or the MFP may ask for computer name + username fields separately)
  • Password: the account password
  • SMB port: 445
  • SMB protocol: SMB2/3 or Auto if available
    Important: use IP to avoid NetBIOS/workgroup resolution issues.

9) If authentication still fails — check Event Viewer on the laptop

• Open Event Viewer → Windows Logs → Security and System. Look for:
  • 4625 (failed logon) — note account and failure reason
  • SMB or Server service errors in System log
    Paste the event ID/message if you want help interpreting it.

Why you saw the errors in your screenshot

• “You entered an invalid value for the /GRANT option.” — because the net share /GRANT requires the account as ComputerName\Username (and proper quoting). Example I gave above is the correct syntax.
• “System error 2 has occurred.” — usually means the path you specified doesn’t exist (so creating the folder first fixes it).
• The Get‑SmbShareGet‑SmbShare error was a typo (Get‑SmbShare is the correct cmdlet).

If you want, try these three quick tests now and paste the exact outputs:

1. From a PC (PowerShell): Test-NetConnection -ComputerName <Laptop-IP> -Port 445
2. From any PC: net use \<Laptop-IP>\Scans-Konica /userATRE-LAPTOP\Scanner <password> (don’t paste password here — just tell me success/fail and any error text)
3. On the laptop: icacls "C:\Scans-Konica"

If any step fails, copy the exact error text (or paste a screenshot) and I’ll tell you the next command to run. If you’d like, I can also give the exact menu navigation for the Bizhub web UI SMB destination setup if you tell me which firmware/UI options it displays.

 

[Distorted Vision]

I tried:

I tried turning Windows firewall off

 

[ChatGPT]

Nice — the screenshots help. I can see the Bizhub Web UI is set to Host Address = 192.168.0.26 and File Path = \192.168.0.26\Scans-Konica, and you turned the Windows firewall off (that’s fine while testing). Two likely issues jump out: the File Path format the MFP expects, and the exact username format the MFP accepts. Do the short checks below and tell me the results / any error text the MFP shows when you attempt a test scan.
Quick sanity checks to run now (copy/paste into an elevated PowerShell on a PC on the same network):
1) Verify the Windows host is listening on SMB ports

• Replace 192.168.0.26 with the IP shown in your Bizhub UI if different:
  Test-NetConnection -ComputerName 192.168.0.26 -Port 445
  Test-NetConnection -ComputerName 192.168.0.26 -Port 139
  Expected: TcpTestSucceeded : True for at least port 445.

2) From a PC, try mounting the share exactly like the MFP will:

• net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner
  If it prompts for a password, enter it. Tell me whether it connects and whether you can create a file in the share.

If the above fails, copy the exact error text and paste it here.
Adjust the Bizhub SMB entry (most common fix)

• In the Bizhub Web UI change the fields like this and Apply:
  • Host Address: 192.168.0.26
  • File Path: Scans-Konica <-- IMPORTANT: do NOT put the full UNC path here; put only the share name
  • User ID: Scanner <-- try just the username first (not PATRE-DESKTOP\Scanner)
  • If that fails, try User ID: PATRE-DESKTOP\Scanner
  • Password: (enter the Scanner account password)
  • SMB options: SMB2/SMB3 or Auto (if there is an option)
  • Save / Apply and then try a Test / Send from the panel.

Why this matters: many MFPs expect Host Address = server IP and File Path = share name (or path relative to the server). Using the full UNC in File Path duplicates the server info and causes failures.
If authentication still fails, run these on the Windows host and paste results:

• icacls "C:\Scans-Konica"
• Get-SmbShareAccess -Name "Scans-Konica" (PowerShell)
• Event Viewer: check Security log for event 4625 around the time of your test scan (this will show the username the MFP tried and the failure reason). Paste the event message here (do NOT paste passwords).

If you used a Microsoft account on the Windows host (e.g., sign-in with an email), the MFP often cannot authenticate against that account — create a local account instead:

• net user Scanner "P@ssw0rd!" /add
• icacls "C:\Scans-Konica" /grant "ScannerOI)(CI)M"
• New-SmbShare -Name "Scans-Konica" -Path "C:\Scans-Konica" -ChangeAccess "Scanner"

Other troubleshooting notes (if still failing)

• Try the alternate File Path formats if needed: Scans-Konica OR \Scans-Konica (but not \192.168.0.26\Scans-Konica when Host Address is filled).
• Try Username variations: Scanner, PATRE-DESKTOP\Scanner, or COMPUTERNAME\Scanner.
• If the MFP offers an SMB version setting, force SMB2/3 (avoid SMB1).
• Re-enable firewall after testing and open File and Printer Sharing if you need the firewall on.

Tell me:

• Result of Test-NetConnection to 192.168.0.26 (port 445)
• Result of net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner
• What the Bizhub shows as the error when you attempt a test scan (authentication failed / cannot connect / path not found / timeout)

With those outputs I’ll tell you the exact next action.

 

[Distorted Vision]

FYI

 

[ChatGPT]

Good — thanks, that Test‑NetConnection confirms SMB ports are reachable (TcpTestSucceeded : True), so network+firewall are not blocking SMB. That narrows this to an authentication/path/SMB compatibility issue. Next steps — do these checks and paste the outputs or error text you get.
1) Fix the Bizhub entry (try this first)

• In the Bizhub Web UI set:
  • Host Address: 192.168.0.26
  • File Path: Scans-Konica <-- only the share name (NOT the full \192.168.0.26... UNC)
  • User ID: Scanner <-- try just the local username first
  • Password: (Scanner account password)
  • SMB version: SMB2/SMB3 or Auto (if selectable)
• Save/apply and run a test scan. If it fails, note the exact error message shown on the MFP (auth failed / cannot connect / path not found / timeout).

2) Verify the share exists and permissions on 192.168.0.26 (run in an elevated PowerShell on that machine)

• Run these and paste results:
  • Get-SmbShare -Name "Scans-Konica"
  • Get-SmbShareAccess -Name "Scans-Konica"
  • icacls "C:\Scans-Konica"
    Expected: share present, account Scanner appears with Change/Full, and the NTFS ACL shows Scanner with Modify (or Full).

(If Get-SmbShare errors because the SMB module isn’t available, run net share and paste that output.)
3) Simulate the MFP from another PC (this is the most useful test)

• From any OTHER PC on the same network (not the host) run:
  • net use \192.168.0.26\Scans-Konica /user:Scanner
  • If prompted, enter the password.
  • If it connects, try: echo test > \192.168.0.26\Scans-Konica\test.txt
    Tell me whether net use succeeds or the exact error text returned.
• If the above fails, try alternate username formats:
  • /userATRE-DESKTOP\Scanner
  • /userATRE-DESKTOP\Scanner (only if first fails — MFP sometimes wants DOMAIN\user)

4) Check Event Viewer for failed auth entries

• On 192.168.0.26 open Event Viewer → Windows Logs → Security. Filter for Event ID 4625 around the time you test the scan. Copy the “Account Name”, “Account Domain” and “Failure Information: Status” and “Sub Status” fields (you can paste the whole event message except any password).
• 4625 will show exactly which username the MFP tried and why it was rejected (bad password, unknown account, logon type, etc.).

5) SMB version / authentication compatibility

• If the MFP is older it might only support SMB1 or NTLMv1. Check the MFP firmware / manual for SMB version support.
• On the Windows host you can check whether SMB1 is enabled (not recommended to enable unless necessary):
  • Get-SmbServerConfiguration | Select EnableSMB1Protocol
• If MFP only does SMB1, either update MFP firmware or (temporary/testing only) enable SMB1 on the host — but be aware SMB1 is insecure.

6) Other common pitfalls (quick checklist)

• Make sure Scanner is a local account (not a Microsoft account). If you used an email sign‑in, create a local user:
  • net user Scanner "P@ssw0rd!" /add
  • icacls "C:\Scans-Konica" /grant "ScannerOI)(CI)M"
  • New-SmbShare -Name "Scans-Konica" -Path "C:\Scans-Konica" -ChangeAccess "Scanner"
• Ensure the share path on the host actually exists (C:\Scans-Konica). If it doesn’t: mkdir "C:\Scans-Konica"
• If you had Everyone/Guest allowed earlier, remove them and rely on the Scanner account to reduce confusion.

What I need from you next

• Outcome of changing the Bizhub File Path to just Scans-Konica and which User ID variation you tested (Scanner vs PATRE-DESKTOP\Scanner) and the exact MFP error.
• Output of these commands on the host (or screenshots):
  • Get-SmbShare -Name "Scans-Konica"
  • Get-SmbShareAccess -Name "Scans-Konica"
  • icacls "C:\Scans-Konica"
• Result (success/error text) of net use \\192.168.0.26\Scans-Konica /user:Scanner when run from another PC.
• If net use fails, paste the Event Viewer 4625 details for that attempt.

With those results I can pinpoint whether it’s the username format, a missing local account, an NTLM/SMB mismatch, or something else.

 

[Distorted Vision]

Tested with:

No SMB2/SMB3 option in MFP settings:

 

[ChatGPT]

Thanks — those screenshots are helpful. From what I can see:

• The MFP address entry is using the IP and the shared name (Host Address = 192.168.0.26, File Path = Scans-Konica) and the Scanner account exists and has full rights on the share (your PowerShell/icacls output confirms the share and ACLs).
• The PageScope SMB menu shows only authentication choices (NTLM v1 / v2 / Kerberos) and not an explicit SMB2/SMB3 protocol selector — which is common on older Konica units: they either speak SMB1 only, or negotiate SMB2/3 implicitly only after a firmware update.

That combination strongly points to a protocol mismatch: the MFP is likely attempting SMB1 (or an SMB dialect Windows is refusing), and the Windows machine has SMB1 disabled (or the Windows SMB server is refusing the authentication dialect the MFP is offering). Before changing Windows, let’s confirm and try a few safe tests.
What to check / try (ordered, short and safe)
1) Capture the MFP error message

• On the MFP control panel or in PageScope job logs, what exact error appears when the scan-to-folder job fails? (e.g. "Authentication failed", "Cannot connect to host", "Protocol error", or an error code). That tells us whether it’s network, auth or protocol.

2) Verify SMB1 availability on the Windows host

• On the Windows machine (as Admin) run:
  • Get-SmbServerConfiguration | Select EnableSMB1Protocol
  • (This will show whether the SMB1 server protocol is enabled.)
• Also test connecting using the same Scanner credentials from another PC:
  • From a cmd prompt on another Windows PC: net use \192.168.0.26\Scans-Konica /user:Scanner <password>
  • If that fails with a protocol error but succeeds if you force SMB1 from a legacy client, that confirms the protocol mismatch.

3) Try changing the MFP authentication setting

• In PageScope → Network → SMB Settings → SMB Client Settings set Authentication to NTLMv2 (or NTLMv1/v2) and apply. If the share is a local workgroup account (not domain/kerberos), NTLMv2 is preferred. Then try a scan.

4) Quick network tests

• From any PC on the same network, try to browse \192.168.0.26\ and see the shared folder. If browsing works, Windows firewall and the Server service are OK.

If tests show SMB1 is disabled and the MFP needs SMB1

• Short-term options (tradeoffs noted):
  a) Enable SMB1 on the Windows host (NOT recommended long-term — SMB1 is insecure):
  • GUI: Control Panel → Programs and Features → Turn Windows features on or off → check "SMB 1.0/CIFS File Sharing Support" (restart may be required).
  • PowerShell (admin): Set-SmbServerConfiguration -EnableSMB1Protocol $true -Force (and/or Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -All)
  • After enabling, test the MFP. If it works, treat this as temporary while you implement a safer solution.
    b) Use a different protocol supported by the MFP: FTP or WebDAV
  • Your PageScope menu shows FTP and WebDAV settings — easiest secure path is to enable an FTP (or better, FTPS/WebDAV if the MFP and server support it) server on the Windows host and configure the MFP to send scans there. This avoids SMB1 entirely.
    c) Update the MFP firmware
  • Check the MFP firmware version (System or Version Info in PageScope). Konica sometimes releases firmware that adds SMB2/3 negotiation and/or stronger auth methods. If a newer firmware exists for bizhub C3350, install it — that solves the root cause without enabling SMB1 on Windows.
    d) Configure a small Linux/VM NAS that allows SMB2/3 and limit access to the MFP (if you have a NAS available).

Security note

• SMB1 is legacy and insecure; enabling it should be temporary and only within a trusted, segmented network. Prefer firmware update or switching to FTP/WebDAV or an SMB2/3-capable server.

If you want, I can:

• Walk you through the exact PowerShell commands to check/enable SMB1 on your Windows machine (and show how to undo it).
• Show steps to set up an FTP target quickly on Windows (IIS FTP) and configure the MFP to use it.
• Help check the MFP firmware version and point out what to look for in Konica firmware notes.

Tell me:

• The exact MFP error message when a scan fails (or paste the Job Log entry).
• The Windows version (Windows 10/11 / Server 2016/2019/2022).
• Whether scanning to this share ever used to work and when it stopped working.

 

[Distorted Vision]

MFP log does not give an error code or error description.
Scan still fails when Authentication set to NTLM v2

 

[ChatGPT]

Thanks — useful update. Since NTLMv2 didn’t work and the MFP gives no useful error, let’s move through a few targeted tests to pin down whether this is a protocol (SMB dialect / SMB1) vs. auth (NTLM v1 vs v2 / Windows policy) vs firewall problem.
Quick plan (try in order) — I’ll give the exact commands to run on the Windows host and the quick MFP changes to test:
1) Try NTLM v1 on the MFP (quick, non-destructive)

• On the MFP PageScope SMB Client Settings change Authentication → NTLM v1 and Apply.
• Try a scan.
• If it works, we know the MFP only supports NTLMv1 (insecure) and Windows is currently accepting it. If it still fails, continue below.

2) Check SMB protocol support on the Windows share (run on the PC that hosts C:\Scans-Konica)

• Open PowerShell as Administrator and run:
  • Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
  • Test that SMB server is listening: Test-NetConnection -ComputerName 192.168.0.26 -Port 445
• Expected:
  • If EnableSMB1Protocol = False and the MFP needs SMB1, that explains a failure.
  • If port 445 is not reachable, firewall or server service blocking it.

3) Try mapping the share from another PC using the same Scanner credentials

• From any Windows client, open CMD (or PowerShell) and run:
  • net use \192.168.0.26\Scans-Konica /user:Scanner <password>
• Observe the error message returned. If it says access denied or logon failure, it’s auth; if it says host unreachable or no network provider accepted, it’s a protocol issue.

4) Check Windows security policy re: NTLM (possible cause if the MFP is NTLMv1-only)

• In PowerShell (admin) check LM compatibility:
  • reg query "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v LmCompatibilityLevel
• Or open secpol.msc → Local Policies → Security Options → “Network security: LAN Manager authentication level”
  • Default modern setting is “Send NTLMv2 response only” which will reject NTLMv1. If the MFP only speaks NTLMv1, that will fail.

5) Inspect the Windows Event Logs for failed logons

• Event Viewer → Windows Logs → Security — look for 4625 (failed logon) entries around the time you attempt a scan. That will show the account and failure reason (bad password, logon type, etc.).

6) If all the above points to SMB1 vs SMB2/3 mismatch, test temporarily (short-term) by enabling SMB1 on the Windows box

• Security warning: SMB1 is insecure — use only briefly for testing and remove it once resolved.
• PowerShell (Admin) to enable (test only):
  • Set-SmbServerConfiguration -EnableSMB1Protocol $true -Force
  • (Optionally restart the machine)
• Test a scan from the MFP.
• To turn it off again:
  • Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force

7) Alternate (safer) short-term options if SMB1 is the issue

• Use FTP (or FTPS if supported) on the Windows PC and configure the MFP to send scans to FTP. PageScope already shows FTP settings, and IIS FTP can be set up quickly to point to C:\Scans-Konica.
• Or add a small NAS or Linux box that accepts SMB2/3 and grant only the MFP access.

8) Longer-term fixes (recommended)

• Firmware: Update the bizhub C3350 firmware — Konica Minolta firmware updates for this model may add SMB2/3 / modern auth support. Check the device’s System/Version info, then the Konica Minolta support/download site for the exact model and release notes.
• Replace SMB target with FTPS/WebDAV or an SMB2/3-capable NAS and avoid enabling SMB1 or NTLMv1 on Windows.

If you want to try one of the tests now, tell me:

• The Windows version (Windows 10/11, or Server 2016/2019/2022).
• The result of step 2 (output of Get-SmbServerConfiguration and Test-NetConnection).
• The exact error text you get on the MFP screen when the scan fails (even if it’s just “Scan failed” — note the time you try it so we can find events in the logs).
• If you’re comfortable, run net use from another PC and paste the returned error text.

If you prefer, I can give:

• Exact PowerShell commands to enable/disable SMB1 and to check firewall rules.
• Step-by-step to set up an IIS FTP site pointing at C:\Scans-Konica and configure basic auth (fast and avoids SMB1).
• Steps to pull the MFP firmware version and what to look for on Konica’s support site.