Konica Minolta BizHub C3350 - Scan to Folder Stopped Working

[Distorted Vision]

Konica Minolta firmware is only available to KM technician and authorised dealers. It is not publicly available on the internet.
Furthermore I don't want to risk bricking it which would necessitate a MFP board replacement.

 

[ChatGPT]

Good — thanks for that detail. Since you don’t want to touch firmware, let’s avoid any risky MFP updates and focus on safe, supported alternatives and short, reversible tests so you can restore the device to its current state at any time.
Summary / recommendation (short)

• Don’t update firmware if you’re worried about bricking — that’s sensible.
• Easiest safe fixes:
  1. Configure the MFP to send scans to an FTP (or FTPS) target on your Windows PC (or a small NAS). Your PageScope shows FTP/WebDAV settings, so this will avoid SMB1/NTLM issues entirely.
  2. If you must use SMB, do a short, tightly‑scoped test by temporarily enabling SMB1 on the Windows host but restrict access with a firewall rule to only the MFP IP. Treat this as diagnostic only — then disable SMB1 again.
• I can walk you step‑by‑step for either approach. Below are the detailed options and exact commands.

Option A — Recommended: Run an FTP/FTPS server on Windows and point the MFP to it
Why: Konica page shows FTP settings and FTP is simple to set up. No SMB1, no NTLM mess, and minimal risk to the MFP.
Quick, low-effort method using FileZilla Server (Windows)

1. Download & install FileZilla Server on the PC that hosts C:\Scans-Konica.
2. During setup choose to run as a service (automatic).
3. In FileZilla Server Interface:
   • Edit → Users → Add user “Scanner”
   • Password: set the same password you use on the MFP.
   • Under Shared folders → Add C:\Scans-Konica and give Write permission.
4. (Optional but recommended) Enable FTP over TLS:
   • Edit → Settings → FTP over TLS settings → generate a self-signed certificate or use a real cert → require TLS for both control and data if the MFP supports FTPS.
   • If MFP doesn’t support FTPS, leave plain FTP on an isolated/trusted LAN.
5. Add a Windows Firewall rule to allow inbound FTP (TCP 21) from MFP IP only:
   • PowerShell (admin): New-NetFirewallRule -DisplayName "Allow FTP from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 21 -RemoteAddress 192.168.0.39
   • Replace 192.168.0.39 with your MFP IP.
6. Test from a PC with an FTP client (FileZilla/Windows Explorer → ftp://username@192.168.0.26) to confirm credentials work, and files can be uploaded.
7. Configure the MFP (PageScope) → Address Book SMB/FTP entry:
   • Host Address: 192.168.0.26 (your PC IP)
   • File Path: (folder path — many MFPs accept just a folder name or “/”)
   • User ID / Password: Scanner / password
   • Protocol: FTP (or FTPS if you enabled TLS and MFP supports it)
8. Try a scan. If it works, remove or leave SMB configuration alone.

Notes:

• If you want to use IIS instead of FileZilla I can give steps — IIS FTP is fine but slightly more setup (IIS features).
• WebDAV is also possible (PageScope shows WebDAV) and has advantage of HTTPS, but IIS WebDAV setup + cert is a bit more work — I can provide that if you prefer.

Option B — Diagnostic: Test SMB1 briefly but safely (ONLY for testing)
Why: Confirms whether the MFP is SMB1-only without committing to leaving SMB1 enabled.
Steps (run on the Windows machine that hosts C:\Scans-Konica)

1. Check current SMB settings:
   • Open PowerShell as Administrator and run:
     Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
2. Restrict SMB access to the MFP IP before enabling SMB1 (prevents exposing SMB1 to the whole LAN):
   • PowerShell (admin): New-NetFirewallRule -DisplayName "Allow SMB from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 445 -RemoteAddress 192.168.0.39
     (replace 192.168.0.39 with MFP IP from your screenshots)
3. Enable SMB1 (test only):
   • PowerShell (admin): Set-SmbServerConfiguration -EnableSMB1Protocol $true -Force
   • Re-run Get-SmbServerConfiguration to confirm.
4. Try a scan from the MFP.
5. When done, remove SMB1 and firewall rule:
   • Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force
   • Remove-NetFirewallRule -DisplayName "Allow SMB from MFP"

Security notes: do NOT leave SMB1 enabled in production. Use this only to confirm whether SMB1 was the blocking cause.
Diagnostics to collect if you want more troubleshooting instead of switching protocols

• On the Windows PC, attempt to map the share with the same Scanner account and note the error:
  • Command (from another PC): net use \192.168.0.26\Scans-Konica /user:Scanner <password>
  • Paste the exact error text here — it often tells whether it’s authentication vs protocol.
• Check Security Event Log for failed logons (Event ID 4625) immediately after a test scan — it will show failure reason.
• If you want an advanced capture, run a packet capture on the Windows server (Wireshark/tcpdump) and check SMB negotiation (see which dialect the MFP proposes). I can give the capture filter and what to look for.

Questions so I can proceed with exact step‑by‑step

1. Do you want me to walk you through FileZilla Server (fast) or IIS FTP / WebDAV (built-in but longer)?
2. What is the Windows version on the PC that hosts C:\Scans-Konica? (Windows 10/11 or Server 2016/2019/2022)
3. Do you want to do the SMB1 test too (I’ll give the exact commands and how to restore)?

If you tell me which option you prefer I’ll give the exact step‑by‑step commands/screens to follow.

 

[Distorted Vision]

FYI

 

[ChatGPT]

Thanks — that screenshot makes things clearer: your Windows host has SMB1 disabled (EnableSMB1Protocol = False) and SMB2 enabled, and TCP/445 is reachable from the server (so the SMB service and firewall are not totally blocking connections). That strongly points to an SMB dialect/auth mismatch between the MFP and Windows.
Next steps — quick, ordered, low‑risk checks you can run now
1) Quick try on the MFP (non-destructive)

• In PageScope → Network → SMB Client Settings set Authentication = NTLMv1/v2 (the combined option) or try NTLM v1 (only) as a diagnostic, then attempt a scan.
• Report whether anything changes on the MFP display (even “Scan failed” — note the time).

2) Capture Windows failure info (most useful single item)

• Immediately after a failed MFP scan, open Event Viewer on the Windows host:
  • Windows Logs → Security → Filter Current Log → Event ID = 4625
  • Open the latest 4625 entry and look at:
  • Account For Which Logon Failed (the username the MFP is presenting)
  • Failure Information → Status and Sub Status (hex codes)
  • Logon Type (should be 3 for network)
• Paste a screenshot or the Status/SubStatus hex codes here and I’ll interpret them (they tell whether it’s a bad password, unknown user, rejected auth method, etc.).

3) Simulate the MFP from another PC (quick auth/protocol check)

• From an administrative CMD on another Windows machine run (replace password and username as needed):
  • net use \192.168.0.26\Scans-Konica /userATRE-DESKTOP\Scanner YourPassword
  • or if it’s local account only: net use \192.168.0.26\Scans-Konica /user:Scanner YourPassword
• Note the exact error text returned — paste or screenshot it here. That often clearly says “logon failure”, “access denied”, or “no network provider accepted”.

4) Check Windows LAN Manager auth level (why NTLMv1 might be rejected)

• Run (Admin PowerShell or CMD):
  • reg query "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v LmCompatibilityLevel
  • or in PowerShell: Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa' -Name LmCompatibilityLevel
• If the value is 5 (Send NTLMv2 response only), Windows will reject NTLMv1 — that explains failures if the MFP only speaks NTLMv1. Don’t change this permanently; it’s a security setting.

5) If you want to confirm SMB dialect offered by the MFP (advanced)

• A packet capture (Wireshark) on the Windows host while the MFP attempts to connect will show the SMB negotiation (which dialect the MFP proposes). If you want to do this I can give the capture filter and what to look for.

If these diagnostics show that the MFP only speaks NTLMv1 / SMB1
Recommended resolution paths (safe options)
A — Best/least risky: use FTP (or FTPS) instead of SMB

• Configure an FTP server on the Windows host (FileZilla Server is quick) and point the MFP to that address. I can give exact, step‑by‑step FileZilla or IIS FTP instructions and a firewall rule so only the MFP can reach it. This avoids enabling SMB1 forever.

B — Diagnostic: enable SMB1 temporarily (if you want to confirm)

• If you want to confirm the MFP is SMB1‑only, do a temporary test with SMB1 enabled but locked down to the MFP IP:
  • Allow SMB from MFP IP only:
  • New-NetFirewallRule -DisplayName "Allow SMB from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 445 -RemoteAddress 192.168.0.39
    (replace 192.168.0.39 with MFP IP)
  • Enable SMB1 for test:
  • Set-SmbServerConfiguration -EnableSMB1Protocol $true -Force
  • Test scan. Then immediately revert:
  • Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force
  • Remove-NetFirewallRule -DisplayName "Allow SMB from MFP"
• Security warning: do not leave SMB1 enabled long-term.

C — Longer-term: get the MFP updated via Konica technician

• If a technician can safely update firmware to a version that supports SMB2/3 and NTLMv2 or Kerberos, that’s the true fix — but you’ve already said firmware is restricted, so I won’t push that.

Which would you like to try next?

• If you want the fastest useful data: try step 1 (NTLMv1/v2 on MFP) and then check Event Viewer (step 2) and paste the 4625 Failure Status/SubStatus here — I’ll decode it and tell you exactly whether it’s “bad password”, “unknown user”, or “auth method rejection”.
• If you prefer to skip SMB debugging and move straight to a working solution, I’ll give step‑by‑step FileZilla Server instructions (secure firewall rule included) so you can get scan‑to‑folder working ASAP.

Tell me which diagnostic or fix you want and I’ll give the exact commands/screens to follow.

 

[Distorted Vision]

FYI

 

[ChatGPT]

Thanks — that screenshot + PowerShell output make the situation clear: your machine currently has SMB1 disabled (EnableSMB1Protocol = False) while SMB2 is enabled, and your attempt to run Set‑SmbServerConfiguration -EnableSMB1Protocol $true failed with “The specified service does not exist” (Windows error 1243). The Get-SmbServerConfiguration / Test‑NetConnection outputs you posted match that diagnosis.
What the error means (short)

• The Set‑SmbServerConfiguration call failed because the SMB server component the cmdlet talks to isn’t available/runnable on that system (the underlying service or server feature isn’t present or is disabled). The usual fixes are: (A) ensure the Server service (LanmanServer) is present and running, or (B) enable the SMBv1 Windows optional feature (server component) using the OS feature tools — DISM or Enable‑WindowsOptionalFeature. Microsoft documents the feature names and commands for enabling/disabling SMBv1.

Safe step‑by‑step checks and how to fix (pick 1 → 2 → 3 in order)
1) Check the Server service (LanmanServer) and start it if stopped

• Open an elevated PowerShell (Run as Administrator) and run:
  • Get-Service -Name LanmanServer
  • sc query lanmanserver
• If the service is Stopped, start it and set it to Automatic:
  • Set-Service -Name LanmanServer -StartupType Automatic
  • Start-Service -Name LanmanServer
• Re-run Get-SmbServerConfiguration afterwards. If Start-Service fails with an error, paste that error text.

2) If the LanmanServer service is missing or Set‑SmbServerConfiguration still errors, enable the SMBv1 optional feature (test only)

• NOTE: SMBv1 is insecure. Use this only briefly for diagnostic/testing or on an isolated/trusted network. Prefer the FTP/FTPS or firmware route long-term. Microsoft documents these commands to enable the SMBv1 feature.
• From elevated Command Prompt (or PowerShell), you can enable the feature with DISM:
  • dism /online /Enable-Feature /FeatureName:SMB1Protocol /All
  • (or enable only the server piece if you prefer) dism /online /Enable-Feature /FeatureName:SMB1Protocol-Server /All
• Or use PowerShell:
  • Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -All
  • (or Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Server -All)
• Reboot if prompted. After reboot check:
  • Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

3) Test the MFP after enabling SMB1 (diagnostic only)

• Try a scan-to-folder from the Konica.
• If it works, you’ve confirmed the MFP needs SMB1 (or only speaks NTLMv1). Don’t leave SMB1 enabled long-term — see “how to undo” below.

How to undo / clean up (very important)

• Disable SMB1 when finished testing:
  • dism /online /Disable-Feature /FeatureName:SMB1Protocol
  • or Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
• Or via GUI: Control Panel → Programs and Features → Turn Windows features on or off → uncheck “SMB 1.0/CIFS File Sharing Support” and reboot.
• Alternatively, restore with Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force after you confirm Server service is running.

Safer long‑term alternatives (recommended)

• Use FTP/FTPS or WebDAV on the PC and point the MFP to that target. Your Konica PageScope UI already shows FTP/WebDAV settings — setting up a small FileZilla Server or IIS FTP site is usually the quickest way to get scanning working without touching SMB1. (I can give step‑by‑step instructions for FileZilla or IIS if you want.)
• If possible, have Konica update the firmware via an authorized technician so the MFP can negotiate SMB2/SMB3 and modern auth (NTLMv2/Kerberos) natively. You already said you don’t want to risk firmware updates, which is reasonable — so FTP/FTPS is the safest route if you want no SMB1 change.

If you want me to proceed

• Tell me which approach you want:
  • A — Try to start/verify LanmanServer (I’ll give the exact commands and how to interpret errors), or
  • B — Temporarily enable SMB1 (I’ll give exact DISM/PowerShell commands and the recommended firewall restriction to allow only the MFP IP), or
  • C — Skip SMB debugging and set up a FileZilla (FTP/FTPS) target on the PC and configure the C3350 to send scans there (I’ll walk step‑by‑step).
• If you choose B (SMB1 test), tell me the MFP IP so I can show the firewall command that restricts SMB1 access to only the MFP while testing.

References: your posted outputs and Microsoft guidance on enabling/disabling SMBv1.
Which do you want to try next?

 

[Distorted Vision]

Option C: Skip SMB debugging and set up a FileZilla (FTP/FTPS)

 

[ChatGPT]

Perfect — we’ll set up FileZilla Server and point the Konica to it. I’ll give a safe, step‑by‑step procedure for both plain FTP (fast) and FTPS (recommended if the MFP supports it). I’ll also include firewall rules that restrict access to the MFP IP only so you don’t expose FTP to the rest of the LAN. Your screenshots/outputs helped confirm SMB is the blocker, so FTP is the simplest workaround.
Before we start (confirm these)

• Windows host IP (the PC where C:\Scans-Konica is): 192.168.0.26 (I’ll use this in examples).
• MFP IP (source of scans): confirm it for me — I believe it’s 192.168.0.39 from your screenshots. Tell me if different; I’ll tailor the firewall commands.

Plan summary

1. Install FileZilla Server on the Windows host.
2. Create a local user (Scanner) or reuse your existing Scanner account and give NTFS write rights to C:\Scans-Konica.
3. Create the FTP user in FileZilla Server and map its shared folder to C:\Scans-Konica (grant write).
4. (Optional but recommended) Configure FTPS (FTP over TLS) and generate a self‑signed cert if the MFP supports FTPS.
5. Configure Windows Firewall to allow inbound FTP/FTPS from only the MFP IP, and open the passive port range used by FileZilla.
6. Test with an FTP client from another PC, then configure the Konica MFP (PageScope) to use FTP/FTPS and test a scan.
7. Troubleshoot using FileZilla logs and Windows Event Viewer if needed.

Detailed steps
A — Prepare folder & local account (one-time on the Windows host)

1. Create the folder (if not already present):
   • Open an elevated PowerShell (Run as Administrator) and run:
     mkdir "C:\Scans-Konica"
2. Ensure the local Scanner user exists and has NTFS Modify rights:
   • If the Scanner local account already exists, skip the user-create step.
   • To create (only if needed): net user Scanner P@ssw0rd! /add
   • Grant NTFS Modify permission:
     icacls "C:\Scans-Konica" /grant "PATRE-DESKTOP\ScannerOI)(CI)M"
     (Replace PATRE-DESKTOP with your PC name if different. If you created Scanner as local user the computer name is implied when you use UI; using the domain\user form in icacls avoids ambiguity.)

B — Install FileZilla Server

1. Download FileZilla Server from the official site (filezilla-project.org) and run the installer.
   • During install choose "Install as service" (start with Windows) for reliability.
2. Launch FileZilla Server Interface and connect to the local server (default 127.0.0.1:14147).

C — Create FTP user & shared folder inside FileZilla Server

1. In FileZilla Server Interface: Edit → Users.
2. Click “Add” under Users and create username: Scanner (or match whatever you prefer).
3. Under Shared folders:
   • Click “Add” under Shared folders and choose C:\Scans-Konica.
   • In Shared folders grant the user at least Write and Append (and List) — checking “Write” will allow uploads.
4. (Important) Ensure “Force SSL for user” is NOT required yet unless you set up a TLS certificate and your MFP supports FTPS.

D — (Optional / Recommended) Configure FTPS (FTP over TLS)

• If your Konica supports FTPS (explicit TLS) use it — it encrypts credentials and files.
  1. In FileZilla Server Interface: Edit → Settings → FTP over TLS settings.
  2. Generate a new self-signed certificate (or import a real cert if you have one).
     • Private key + certificate file location will be stored locally.
  3. If you enable TLS, you can require TLS for control and data. Note: some devices require explicit FTPS (TLS on port 21) not implicit (port 990). Konica typically supports explicit FTPS — check the MFP’s FTP settings for an FTPS/TLS option.
  4. If you enable TLS, set FileZilla to listen on port 21 (default) for explicit FTPS.

E — Passive mode settings (important on NAT or stricter firewalls)

1. In FileZilla Server settings → Passive mode settings:
   • Choose “Use the following IP” → leave blank for LAN-only setups OR enter host IP 192.168.0.26.
   • Set a small passive port range, e.g. 50000-50020.
2. You will open TCP 21 and that passive range in the firewall (next step).

F — Windows Firewall rules (restrict to MFP IP)

• Replace MFP_IP with the MFP address you confirm (e.g. 192.168.0.39).

1) Allow FTP/FTPS control port from MFP only (port 21):

• Open an elevated PowerShell and run:
  New-NetFirewallRule -DisplayName "Allow FTP from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 21 -RemoteAddress 192.168.0.39

2) Allow passive port range from MFP only (example 50000-50020):
New-NetFirewallRule -DisplayName "Allow FTP Passive from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 50000-50020 -RemoteAddress 192.168.0.39
3) (Optional) If you enabled FTPS implicit on port 990 instead, allow 990 instead of 21.
4) Verify the rules:
Get-NetFirewallRule -DisplayName "Allow FTP from MFP","Allow FTP Passive from MFP" | Format-Table DisplayName,Enabled
G — Test the FTP server from another PC

1. Use FileZilla Client (or Windows Explorer) to test:
   • Host: 192.168.0.26
   • Port: 21 (or 990 for implicit FTPS)
   • Username: Scanner
   • Password: (the Scanner password)
   • If FTPS: choose “Require explicit FTP over TLS” in client (FileZilla client).
2. Try uploading a small file into C:\Scans-Konica. Confirm it appears on the host.

H — Configure the Konica bizhub C3350 (PageScope / Remote UI)

1. Log into the device web UI (PageScope) as Administrator.
2. Address Book → Register New Destination → Type: File.
3. Protocol: FTP (or FTPS if you configured TLS and the MFP supports it).
4. Host Address: 192.168.0.26 (Windows host).
5. File Path: Scans‑Konica or / (try Scans‑Konica first). Note: some Konica firmware wants only the folder name while others want a full path — try both if initial fails.
6. User ID: Scanner
7. Password: (Scanner password)
8. Port: 21 (or 990 for implicit FTPS). For explicit FTPS most MFPs still use port 21 and a checkbox for FTPS/TLS — enable FTPS/TLS if you set up FTPS.
9. Passive/Active mode: set to Passive (PASV) — most NAT/LAN setups work with Passive.
10. Save and run a test scan.

I — If the scan fails: quick troubleshooting

• Check FileZilla Server log (bottom of interface) — it will show connection attempts and authentication errors.
• Check Windows Firewall logs / disable temporarily (only for test) to see if firewall is blocking.
• Confirm the exact filename/path the MFP is attempting to upload (FileZilla log shows STOR commands).
• If login fails, double‑check the password and that the FTP user is mapped to the folder.

J — Security & cleanup notes

• Do NOT allow anonymous logins.
• Restrict firewall rules to only the MFP IP as above.
• If you used plain FTP (no TLS), keep this only on an isolated/trusted LAN — traffic and credentials are sent in clear text.
• If the MFP supports FTPS, prefer FTPS so credentials and file contents are encrypted.
• If you want central logging or retention, you can point FileZilla logs to a file or use Windows auditing.

K — If you want, I can give exact commands for your environment

• Confirm these three items and I’ll paste the exact commands you can copy/paste into an elevated PowerShell:
  1) Confirm MFP IP (I think 192.168.0.39 — please confirm).
  2) Tell me whether you want FTPS (encrypt) or plain FTP (faster to get working).
  3) Confirm the Scanner username and whether it already exists as a local user on the Windows host (you already have a Scanner account according to earlier screenshots — do you want to reuse that account?).

If you confirm those three items I’ll give a ready-to-run command block for:

• NTFS permissions (icacls)
• New-NetFirewallRule rules (control + passive ports)
• Quick test commands to verify the service is reachable

Ready when you are — confirm MFP IP and FTPS vs FTP and I’ll give the exact PowerShell commands and the minimal Konica PageScope field values to enter.

 

[Distorted Vision]

C:\Scans-Konica is on: 192.168.0.26
MFP IP is: 192.168.0.39

 

[ChatGPT]

Great — thanks for confirming IPs. Below are exact, copy/paste-ready steps (PowerShell + FileZilla UI) to get FTP or FTPS working from the bizhub C3350 to C:\Scans‑Konica on 192.168.0.26, with firewall rules that restrict access to only the MFP (192.168.0.39).
I’ll provide:

• Quick checks
• PowerShell commands (run as Administrator)
• FileZilla Server UI steps (for FTPS option too)
• Konica PageScope fields to enter
• Troubleshooting tips

Note: your earlier outputs show SMB1 is disabled and SMB port 445 is reachable, so FTP avoids the SMB compatibility/auth problem.
Before you begin

• Confirm you know the Scanner account password (you already have PATRE‑DESKTOP\Scanner from earlier). We’ll reuse that local account in FileZilla (map the FTP user to the same NTFS folder).
• Run everything in an elevated PowerShell / admin session where I give commands.

1) Create folder (if needed) and set NTFS permission
Run these in an elevated PowerShell on 192.168.0.26:
New-Item -Path 'C:\Scans-Konica' -ItemType Directory -Force
icacls "C:\Scans-Konica" /grant "PATRE-DESKTOP\ScannerOI)(CI)M"
(Replace PATRE-DESKTOP if the computer name is different. This gives Scanner Modify rights.)
2) Install FileZilla Server

• Download from filezilla-project.org and install FileZilla Server.
• During install choose “Install as service” and “Start server after setup”.

3) Configure FileZilla Server — create FTP user and map folder

• Open FileZilla Server Interface (connect to local server).
• Edit → Users → Add → create user "Scanner" (or use same name).
• In Shared folders → Add → select C:\Scans-Konica.
  • Grant Read, Write, Delete, Append (Write/Append required for uploads).
• (Optional) Under General settings for that user, uncheck “Force TLS” for now if you haven’t configured TLS — you can enable TLS later.

4) (Recommended) Configure FTPS (TLS) — optional but encrypted

• In FileZilla Server: Edit → Settings → FTP over TLS settings.
• Click “Generate new certificate” → fill fields and save certificate and key locally.
• Check “Enable FTP over TLS support (FTPS)”.
• Optionally check “Require TLS for user login” (only do this if you confirm the MFP supports FTPS).
• Most bizhub MFPs support Explicit FTPS (explicit TLS on port 21). If unsure, leave TLS optional first, test plain FTP, then enable FTPS if the MFP supports it.

5) Configure passive mode in FileZilla (important)

• Edit → Settings → Passive mode settings:
  • Select “Use the following IP” → put 192.168.0.26 OR leave blank if purely LAN.
  • Set custom port range, e.g. 50000-50010 (small range).
  • Click OK.

6) Add Windows Firewall rules that allow only the MFP
Run these (Admin PowerShell) — they restrict FTP access to the MFP IP 192.168.0.39 only:

Allow control port (21) from MFP only​

New-NetFirewallRule -DisplayName "Allow FTP from MFP (control)" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 21 -RemoteAddress 192.168.0.39

Allow passive port range 50000-50010 from MFP only​

New-NetFirewallRule -DisplayName "Allow FTP Passive from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 50000-50010 -RemoteAddress 192.168.0.39

(If you opted for implicit FTPS on 990 instead of explicit on 21)​

New-NetFirewallRule -DisplayName "Allow FTPS from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 990 -RemoteAddress 192.168.0.39​

Verify the rules:
Get-NetFirewallRule -DisplayName "Allow FTP from MFP (control)","Allow FTP Passive from MFP" | Format-Table DisplayName,Enabled
7) Test from a PC (quick)

• From another PC on the LAN (or from the host itself using an FTP client like FileZilla Client):
  • Host: 192.168.0.26
  • Port: 21
  • User: Scanner
  • Password: (Scanner password)
  • Use Passive (PASV)
• Upload a small test file into the FTP root and confirm it appears in C:\Scans-Konica.

You can also test basic connectivity:
Test-NetConnection -ComputerName 192.168.0.26 -Port 21
8) Configure the Konica bizhub C3350 (PageScope / Remote UI)

• Log into PageScope as Administrator.
• Address Book → Register New Destination → Type: File
• Protocol: FTP (or FTPS if you set TLS and the MFP supports FTPS—choose FTPS/TLS explicit if available)
• Host Address: 192.168.0.26
• Port: 21 (or 990 if you set implicit FTPS)
• File Path: Scans‑Konica (try exactly this first) — if fails, try "/" or leave blank
• User ID: Scanner
• Password: (enter Scanner password)
• Transfer Mode: Passive (PASV)
• Save and run test scan.

Konica notes:

• If FTPS explicit is supported by the MFP, select the FTPS/TLS option and set Port = 21. If the MFP only supports plain FTP, use FTP and keep TLS disabled on FileZilla.
• If initial test fails, try User ID variations: Scanner OR PATRE-DESKTOP\Scanner. For FTP usually just Scanner is correct.

9) Troubleshooting (if it fails)

• Look at FileZilla Server log (bottom pane) — it will show connection attempts, username presented, and STOR commands. This will show whether the MFP connected, authenticated, and attempted to upload.
• If login fails: confirm the password and that the FileZilla user’s home directory is C:\Scans-Konica.
• If connection fails: verify the firewall rule exists and the MFP IP is correct:
  Get-NetFirewallRule -DisplayName "Allow FTP from MFP (control)" | Format-Table DisplayName,Enabled,Profile
• If passive data connection fails: open the small passive range in firewall (we used 50000-50010). Confirm those ports are configured in FileZilla passive settings and the firewall matches them.
• If FTPS fails: try plain FTP first to confirm functionality, then switch to FTPS. Many MFPs support explicit FTPS (TLS on port 21).

10) Security notes & next steps

• If possible, enable FTPS (explicit TLS) so credentials and data are encrypted. Confirm the MFP supports FTPS before requiring TLS.
• Keep the firewall rules restricted to the MFP IP to avoid exposing FTP to the rest of the network.
• Once scanning is working, you can keep this setup or pursue manufacturer firmware to restore SMB2/3 on the MFP in future.

A small ready-to-run Admin PowerShell block (adjust if Scanner user already exists and computer name differs):

create folder (if needed) and set permissions​

New-Item -Path 'C:\Scans-Konica' -ItemType Directory -Force
icacls "C:\Scans-Konica" /grant "PATRE-DESKTOP\ScannerOI)(CI)M"

firewall rules (replace MFP IP if different)​

New-NetFirewallRule -DisplayName "Allow FTP from MFP (control)" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 21 -RemoteAddress 192.168.0.39
New-NetFirewallRule -DisplayName "Allow FTP Passive from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 50000-50010 -RemoteAddress 192.168.0.39

verify FTP port open (simple test)​

Test-NetConnection -ComputerName 192.168.0.26 -Port 21
Run that block, then complete the FileZilla UI steps above.
If you want, I can:

• Provide screenshots/fields tailored to the C3350 PageScope screens (exact labels) if you paste the PageScope FTP settings page, or
• Give the precise passive port range + FileZilla passive-mode screenshots to use, or
• Walk through interpreting a FileZilla Server log if you paste the relevant lines.

Finally — confirmation of context: you previously showed SMB1 disabled and that 445 is reachable, which is why I recommended this FTP path.
Go ahead and run the PowerShell block and set up FileZilla user & passive settings; when you have the test log output or if the Konica gives an error on the test scan, paste the FileZilla log lines or the exact MFP error text and I’ll walk you through the fix.

 

[Distorted Vision]

In Step 3 above there is no Edit Menu in FileZilla Server

 

[ChatGPT]

Thanks — good catch. FileZilla Server UI varies by version and can hide the old Edit menu; there are two quick ways to get to the Users dialog so you can create the FTP account and assign C:\Scans-Konica even if you don’t see an Edit menu.
Follow the appropriate method below that matches what you see in your FileZilla Server Interface.
If you see a toolbar (icons) at the top of the FileZilla Server window

1. Open the FileZilla Server Interface and Connect to the local server.
2. Look at the top toolbar — there are small icons for Settings, Users and Groups. The Users icon usually looks like a single person or two people.
3. Click that Users icon to open the Users dialog (same as Edit → Users from older docs).
4. In the Users dialog: click Add, type Scanner (or the username you want), click OK.
5. With the user selected, click Shared folders on the left, click Add and choose C:\Scans-Konica. Click Set as home dir (the H).
6. Tick Write (and List, Delete, Append as needed) so uploads work. Click OK / Close.

If you don’t see a toolbar or a menu bar

1. Try pressing Alt on your keyboard to reveal a hidden menu bar (some builds hide it until Alt is pressed). If a menu appears, you can use Edit → Users.
2. If no menu appears, look for a small gear/settings icon or a “Users / Groups” button somewhere in the window — click that to reach the same Users dialog. Newer FileZilla Server versions moved Edit → Users into toolbar buttons.
3. If there’s a left/right pane showing “Connected to: 127.0.0.1:14147” and some small icons, hover over those icons — the tooltip will say “Users” or “Groups”. Click it.

If none of the above is visible

• Close the GUI and re-open the “FileZilla Server Interface” from Start → FileZilla Server → FileZilla Server Interface. Connect to 127.0.0.1:14147 and watch the small dialog — the admin UI normally shows the toolbar on connect.
• If you installed FileZilla Server as a service and the Interface won’t connect, run the Interface “as Administrator” (right‑click → Run as administrator) then click Connect.

Important notes about users and NTFS permissions

• FileZilla’s FTP users are managed inside FileZilla Server (virtual users), not Windows local accounts. You can name the FileZilla user “Scanner” and set the same password as your Windows Scanner account for convenience — but FileZilla will authenticate against its own user list, not the Windows accounts.
• The FileZilla service (runs as LocalSystem by default) performs the file write operations. LocalSystem typically already has write access; if an upload fails, ensure the service account (SYSTEM) or Administrators have Modify on C:\Scans-Konica. If you prefer to keep tight ACLs, grant Modify to NT AUTHORITY\SYSTEM or to the group used by the FileZilla service.

If you still can’t find the Users dialog

• Paste a screenshot of the FileZilla Server Interface window (what you see after you click Connect). I’ll point to the exact icon/button to click.
• Or tell me the version number you installed (Help → About if visible) and I’ll give the exact UI path for that version.

Once you can open Users, complete the rest of the setup (passive ports, optional TLS, firewall rules) and then configure the MFP to use:

• Protocol: FTP (or FTPS if you enable TLS and the C3350 supports explicit FTPS)
• Host: 192.168.0.26
• Port: 21 (or 990 for implicit FTPS; for explicit FTPS use port 21 and enable FTPS option)
• Username: Scanner (the FileZilla user you created)
• Password: the password you set in FileZilla
• Transfer mode: Passive (PASV)
• File path: try Scans-Konica, or “/” if the device expects the user home folder

If you want, I can:

• Post the exact small sequence of screenshots / button locations for the FileZilla Server version you have, or
• Give the exact PowerShell firewall commands again (we prepared those earlier) and the recommended passive port range to open.

Which would you like: a screenshot walk‑through for your FileZilla window, or the firewall/passive-port commands next?

 

[Distorted Vision]

Still don't see any way to Create users:

FileZill Server 1.11.1

 

[ChatGPT]

Thanks — the screenshot helped. In FileZilla Server 1.11.x the user management UI is still there, it’s just not obvious in your window because the toolbar/icons or the configuration panel are hidden. Try these quick checks in order — one of them will expose the Users dialog so you can add the Scanner account and map C:\Scans‑Konica.
1) Use the Server → Configure dialog (reliable)

• In the Admin window click the Server menu → Configure... (or press Ctrl+F).
• The Configuration dialog will open. In that dialog you’ll see categories on the left (General, Settings, Users, Groups, Passive mode, etc.).
• Click Users → Add → enter the FTP username (Scanner) → Shared folders → Add → select C:\Scans‑Konica and give Write permissions. OK/Apply.

2) Look for the Users toolbar icon (alternate UI)

• In many FileZilla Server builds there are three small icons under the menu bar (Settings, Users, Groups). Hover the small icons — the tooltip will say “Users”. Click it to open the same Users dialog.
• If you don’t see any icons, try resizing/maximizing the FileZilla window — the icons sometimes disappear if the window is narrow.

3) Reveal the hidden menu bar

• Press the Alt key once (or Alt+E) to reveal any hidden menus; sometimes the full menu (including Edit) only shows on Alt. If an Edit menu appears, choose Edit → Users.

4) Run the Admin Interface “as Administrator”

• Close the interface, then right‑click FileZilla Server Interface and choose “Run as administrator” and Connect. Some UI elements behave differently unless run elevated. After connecting repeat steps 1–2.

5) If the menus still don’t show: check what components you installed

• If you installed “Administration interface only” (no server) the admin interface may not show full controls. Re-run the FileZilla Server installer and make sure you install both the Server service and the Admin interface (choose “All” or “Standard”). The admin interface log shows “Successfully connected to server 127.0.0.1:14148” so it looks connected, but re‑installing with the Server component can solve a missing UI problem.

6) Last resort: open the Users dialog via Configure → “Users” page URL

• If Configure/Ctrl‑F opens the configuration dialog but you don’t see “Users” in the left pane, post a screenshot of the Configure dialog and I’ll point at the exact place. (Paste that screenshot here.)

What I recommend you try now (in order)

• Click Server → Configure... (Ctrl+F) and look for Users in the left list. If you find it, tell me and I’ll give the exact fields to fill.
• If Configure isn’t present, press Alt and check for Edit → Users.
• If neither works, maximize/resize the Admin window and run it as Administrator, then look for the small icons under the menu bar (hover to see “Users” tooltip).

If you still can’t find it, paste a new screenshot of the whole FileZilla Admin window (like the one you posted) after you’ve expanded it or opened Server → Configure — I’ll mark exactly where to click.

 

[Distorted Vision]

I see this

 

[ChatGPT]

Thanks — that screenshot makes it clear. The admin UI you have is connected, but the user/config panels are hidden behind the Configuration dialog. Use Server → Configure (or the keyboard shortcut) to open the configuration dialog where Users and Groups are managed.
Do this now and you’ll see the Users panel I was referencing:
1) Open the Configuration / Users dialog

• In the FileZilla Server Administration window click Server → Configure...
  • Or press Ctrl+F.
• That opens the Configuration dialog. In the left column you’ll see categories such as General, Settings, Users, Groups, Passive mode, FTP over TLS, etc.

2) Add the FTP user and map the folder

• Click Users in the left column.
• Click Add (button) and type Scanner (or whatever user you want). Click OK.
• With the user selected, click Shared folders on the left.
• Click Add (under Shared folders) and choose C:\Scans-Konica. Click Set as home dir (the little house icon) if shown.
• In File and Directory permissions, check List, Read, Write (and Delete/Append if you want the MFP to overwrite/append). Click OK / Apply.

3) Important NTFS note (service account must have access)

• FileZilla Server service runs as SYSTEM by default. Make sure the service account has write access to C:\Scans-Konica. Run this (Admin PowerShell) to grant Modify to SYSTEM and Administrators:
  • icacls "C:\Scans-Konica" /grant "NT AUTHORITY\SYSTEMOI)(CI)M" /grant "AdministratorsOI)(CI)M"
• If you prefer to restrict to just the uploads from the FTP user, you can still keep the folder ACLs tight — the server (SYSTEM) needs filesystem rights to write the files.

4) Configure passive ports and (optionally) TLS

• In Configuration dialog click Passive mode on the left:
  • Set “Use custom port range” to e.g. 50000–50010 and click Apply.
• If you want encryption, click FTP over TLS settings → Generate new certificate → Enable FTP over TLS support (FTPS). If you enable Require TLS, confirm your MFP supports FTPS before forcing it.

5) Save & restart (if required)

• Click OK / Apply in the Configuration dialog. FileZilla server will now accept FTP logins for the Scanner user and drop files into C:\Scans-Konica.

6) Firewall rules (you already prepared these earlier)

• You should have the inbound rules allowing port 21 and passive range only from 192.168.0.39 (MFP). If you need the exact commands again I’ll paste them.

7) Configure the Konica

• Protocol: FTP (or FTPS explicit if you enabled TLS and the MFP supports it)
• Host: 192.168.0.26
• Port: 21 (explicit FTPS also uses 21)
• User: Scanner
• Password: (the password you set in FileZilla)
• Transfer Mode: Passive (PASV)
• File Path: Scans‑Konica (or / if it fails — try both)

If you still don’t see Server → Configure or Ctrl+F does not open the configuration dialog

• Either run the Admin interface “as Administrator” (right‑click → Run as administrator) and connect again, or re-run the FileZilla Server installer and ensure you installed “All” (Server + Administration interface). The Admin UI will only be able to show full configuration if the service+server component is installed and you are connected to that service.

If you want I can:

• Paste the exact PowerShell firewall commands again (21 + passive range restricted to 192.168.0.39).
• Walk you through the exact fields to set on the Konica (I can annotate with the values to paste).
• Interpret FileZilla Server logs if a test scan fails.

Tell me whether Server → Configure (or Ctrl+F) opened the Configuration dialog — if so, say “I see Users” and I’ll give the exact buttons/checkboxes to click in that dialog. If not, tell me whether you re‑ran the installer (so I can give the reinstall steps).

 

[Distorted Vision]

I see this:

 

[ChatGPT]

Perfect — that Settings dialog is exactly where we need to be. You already have the server config open; now create the FTP user, mount the C:\Scans-Konica folder and give the user upload rights.
Follow these exact steps in the dialog you posted (copy/paste friendly):
1) Create the FTP user

• In the left column click Rights management → Users.
• Click the Add button (bottom-left under the Available users list).
• Type Scanner (or your preferred username) and click OK. The new user appears in the Available users list.

2) Enable the user and set auth

• Select the Scanner user in the Available users list.
• On the right, check the box User is enabled.
• Change Authentication from “Use system credentials to log in” to Password. (This exposes the password fields.)
• Enter the password you want the MFP to use and confirm it.
• IMPORTANT: leave unchecked “Use system credentials also for accessing files and directories” (so the server uses its own service account to write).

3) Add the folder (mountpoint) and give file permissions

• With the Scanner user still selected, in the Mount points area click Add.
• In the Add mountpoint dialog:
  • Virtual path: / (this makes the FTP user root point to the folder)
  • Native path: C:\Scans-Konica
  • Click OK.
• Back in the Mount points list select the mountpoint you just added.
• In the Mount options area enable the required permissions — at minimum check: List, Read, Write, Create, Delete, Append (names may vary slightly). This allows uploads/overwrite from the MFP.

4) Apply and close

• Click Apply (bottom-right) then OK to save changes.

5) Ensure the server account can write to the folder (NTFS)

• FileZilla Server runs as the SYSTEM service by default. Make sure the service account has Modify on the folder:
  • Open an elevated PowerShell and run:
    icacls "C:\Scans-Konica" /grant "NT AUTHORITY\SYSTEMOI)(CI)M" /grant "AdministratorsOI)(CI)M"
• (If you prefer the FTP service to impersonate a Windows user instead, you can instead use “Use system credentials to log in” and map mountpoints accordingly — but using FileZilla users with SYSTEM access is simpler.)

6) Passive mode & listener check (important)

• In that same Configuration dialog, click Passive mode (left pane) and set a small port range, e.g. 50000–50010. Click Apply.
• Click Server listeners (left pane) and ensure there is a listener on port 21 (IPv4) — default is present. If not, add a listener on port 21.

7) Firewall rules (restrict to MFP IP)
Run these in elevated PowerShell on 192.168.0.26 (you already prepared similar rules — run them if not already present):
New-NetFirewallRule -DisplayName "Allow FTP from MFP (control)" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 21 -RemoteAddress 192.168.0.39
New-NetFirewallRule -DisplayName "Allow FTP Passive from MFP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 50000-50010 -RemoteAddress 192.168.0.39
8) Quick test from a PC

• Using FileZilla Client (or any FTP client) connect to 192.168.0.26 port 21 with user Scanner and the password you set. Use Passive mode. Upload a small file; confirm it appears in C:\Scans-Konica.

9) Konica PageScope settings (values to enter)

• Protocol: FTP (or FTPS explicit if you later enable TLS)
• Host Address: 192.168.0.26
• Port: 21
• File Path: / (or leave blank; if that fails try Scans-Konica or just “.”)
• User ID: Scanner
• Password: (the password you set in FileZilla)
• Transfer Mode: Passive (PASV)

10) If anything fails — what to check

• FileZilla Server log (bottom of administration window) — it shows the connection, login and STOR command and any permission errors. Paste the relevant log lines if you need help interpreting.
• If login fails: confirm password in the Users → General tab.
• If upload fails with permission denied: re-run the icacls command above to give SYSTEM Modify access.
• If data (PASV) connection fails: verify passive port range matches firewall rule and FileZilla passive mode setting.

If you want, I can:

• Give the exact commands to enable FTPS (generate cert) in FileZilla and the MFP settings for FTPS, or
• Interpret FileZilla Server log lines if you paste them after a failed test, or
• Walk through the MFP PageScope fields with screenshots.

Try creating the Scanner user and mountpoint now and tell me whether the FTP client test can upload a file — if it fails, paste the FileZilla Server log output (the orange/black messages in the admin UI) and I’ll decode it.

 

[Distorted Vision]

It all worked! Now give me the steps to configure MFP to use FTP.

 

[ChatGPT]

Nice — glad FileZilla is working. Below are the exact steps to configure the bizhub C3350 to send scans to your new FTP target plus quick troubleshooting and security notes. I’ll use your values (FTP host = 192.168.0.26, FTP user = Scanner, MFP IP = 192.168.0.39). Replace the password text with the actual password you set in FileZilla.
A — Configure FTP destination in the MFP Web UI (PageScope / Remote UI)

1. Open PageScope / Remote UI in a browser and log in as Administrator.
2. Go to Address → Address Book → Register New Destination (or Address Book List → Add).
3. Fields to enter:
   • Type: File
   • Protocol: FTP (if you set up FileZilla without TLS) — or FTPS / FTP over TLS if you configured TLS and the MFP supports explicit FTPS.
   • Host Address: 192.168.0.26
   • Port: 21 (for FTP or explicit FTPS)
   • File Path: / (use a single forward slash so the MFP writes into the user’s home/virtual root). If that doesn’t work, try leaving File Path blank or try "Scans-Konica" (some firmware variants expect a folder name).
   • User ID: Scanner
   • Password: (the password you created in FileZilla)
   • Transfer Mode: Passive (PASV) — choose Passive.
   • (If FTPS) Enable FTPS / Use TLS: check the box for FTPS or TLS (explicit). For explicit FTPS use port 21 and the FTPS option.
4. Apply / Save the address-book entry.

B — Configure and test from the MFP control panel

1. On the MFP touch panel select Scan → Address Book and pick the FTP destination you just created.
2. Place a sheet in the scanner and press the Scan / Start button to send a test scan.
3. On success the file should appear in C:\Scans-Konica on 192.168.0.26.

C — If the MFP reports an error or the scan fails — quick checks

1. Watch FileZilla Server log (Administration interface) while you press Start on the MFP:
   • You should see a connection attempt, a USER/PASS exchange and then a STOR command for the file. If the log shows “530 Login incorrect” — password or username mismatch. If it shows no connection at all, the MFP cannot reach port 21 or passive ports.
2. If login fails:
   • Re-enter the password in PageScope (typos happen). Confirm you created the FileZilla user Scanner and set that exact password in the Users → General tab.
3. If the connection is accepted but data transfer fails:
   • Verify the passive port range in FileZilla matches the firewall rule (we used 50000–50010). Confirm the firewall rules exist and are enabled:
     • Get-NetFirewallRule -DisplayName "Allow FTP from MFP (control)","Allow FTP Passive from MFP"
4. If FTPS fails:
   • Try plain FTP first (temporarily) to confirm everything else works. If plain FTP works but FTPS fails, the MFP may not trust the self‑signed certificate — either install a CA-signed cert on the server or leave FTP allowed but restricted by firewall to the MFP IP only.
5. If permission errors occur:
   • Ensure FileZilla service (SYSTEM) can write to the folder: icacls "C:\Scans-Konica" (and grant Modify to NT AUTHORITY\SYSTEM if necessary).

D — Useful FileZilla log lines to paste here (if you need help)

• Connection attempt lines (show IP and port)
• USER and PASS response and any 530/550 errors
• STOR command and any permission denied (550) messages

E — Security & housekeeping (recommended)

• If the MFP supports FTPS, enable explicit FTPS (TLS) in FileZilla and on the MFP so credentials and files are encrypted. If you require FTPS, remove the “Require TLS” only after confirming the MFP accepts the cert or you’ve installed a cert the MFP trusts.
• Keep the firewall rules restricted to the single MFP IP (you already did this). To view or remove rules:
  • View: Get-NetFirewallRule -DisplayName "Allow FTP from MFP (control)" | Format-Table DisplayName,Enabled
  • Remove: Remove-NetFirewallRule -DisplayName "Allow FTP from MFP (control)","Allow FTP Passive from MFP"
• Use a strong password for the Scanner account and rotate it periodically.
• After everything is working, consider enabling FTPS and then disabling plain FTP (remove the firewall rule for port 21 or change FileZilla to require TLS).

F — Commands that might help (copy/paste in an Admin PowerShell on 192.168.0.26)

• Check FileZilla service is running:
  Get-Service -Name "FileZilla Server" # (service name may vary; check Services.msc)
• Verify firewall rules:
  Get-NetFirewallRule -DisplayName "Allow FTP from MFP (control)","Allow FTP Passive from MFP" | Format-Table DisplayName,Enabled,Profile
• View passive port usage (if you suspect blocked data channels) by watching FileZilla logs during a transfer.

If you want, I can:

• Provide exact screenshots and the precise PageScope field locations for your firmware build (paste a screenshot of the PageScope FTP settings page if you’d like me to mark the fields), or
• Walk you through enabling FTPS (generate certificate in FileZilla, test MFP acceptance), or
• Interpret the FileZilla log lines if a test fails.

Want me to walk you step‑by‑step through a live test now? If so, run one test scan and paste the FileZilla admin log lines shown during the test (or the exact error text from the MFP) and I’ll decode them.