Laserjet Pro 4101fdw Scan to network folder issues

[btswein]

Brand new initial setup on Laserjet Pro 4101fdw. Firmware just auto-updated to LOCHSAXXXN002.2624A.00 (not yet listed on HP Support site.) I cannot consistently scan to a network folder (Server 2019) on a domain environment. I have multiple brands of devices that can scan just fine to these network folders, including other models of HP.

Using the EWS (the machine is remote) it sometimes tests fine, other times gives "pgAddrBookContacts-ErrorConnectionProblem" error in the "manual" address book.  I have tried enabling SMB 1 (yes I'm aware it's insecure, but I'm desperate), SMB2 and SMB3 all at the same time. I have used \\server IP address\folder as well as \\servername\folder and \\servername.domainname\folder. I have tried different credentials, using domain\user as well as just the username and password. Verified that username and password are correct (again, use the same account for every other printer just fine.) I have confirmed network firewall connectivity, manual IP address, DNS, subnet mask, default gateway etc. and scanning to email, printing etc. all work fine. The time is set correctly. I have configured LDAP and still run into this issue.  Please advise.

[Meghana_10]

Hello @btswein, Welcome to the HP Support Community. 

Thank you for providing such a detailed description of your environment and the troubleshooting you've already completed. It sounds like you've methodically ruled out most of the common causes.
 

Based on your findings, this appears more likely to be related to printer firmware behavior or SMB protocol compatibility rather than a configuration issue with your Windows Server 2019 file share. 
 

Recommended Troubleshooting

Please try the following steps to help isolate the source of the issue:
 

• Disable SMB1 and use only SMB2/SMB3.
• Test the network folder using \\IP_Address\Share instead of the server name.
• Try both domain\username and [email protected] for the scan credentials.
• Review the Server 2019 SMB and Security event logs during a failed scan attempt to verify whether the printer is reaching the server.
• If possible, test scanning to a different SMB server (such as a Windows 10/11 PC or a NAS) to help isolate the issue.

Also request for serial number for further assistance.
Have a great day!

[Repairatrooper]

Wondering the following,

- when it fails, do you get any kind of notification or does the scan simply time out? I realize that the error information supplied by Pro models like this is not the most comprehensive.

- Are you connecting via wireless or wired ethernet. I ask because I have clients who have had issues trying to connect via 5Ghz and have had to force the printer to only connect to 2.4Ghz wifi connections.

[btswein]

Hello. Please see responses below. One thing I find interesting is that from the EWS, every OTHER attempt to "Verify Access" works. Like if I try it twice, the second time it succeeds. This is consistent for the user at the control panel as well. If the user tries to scan to a network folder, it fails the first time, but succeeds 10 seconds later on a second attempt. I forgot to mention that the printer is connected via ethernet, static IP and brand new CAT6 (I did swap it with another one from another batch as well.) I can ping the printer just fine so I do not believe this to be a networking issue. Serial number is THBGV1Z3SW. I have two machines exhibiting the same issue, both firmware is up-to-date and 4 more that I am holding off on until I can figure this out.

• Disable SMB1 and use only SMB2/SMB3. -Done. The "default state" I have left the printer in is 2/3. 1 was enabled for testing only. So, regardless of SMB setting, it works the same (second attempt works.) The M521dn this machine is replacing only supports v1 so interesting that "dumbing" the 4101fdw down doesn't work.
• Test the network folder using \\IP_Address\Share instead of the server name. -Done. I am using \\ipaddress\sharename
• Try both domain\username and [email protected] for the scan credentials. -Done. I am using domain acronym\username. 
• Review the Server 2019 SMB and Security event logs during a failed scan attempt to verify whether the printer is reaching the server. -In progress
• If possible, test scanning to a different SMB server (such as a Windows 10/11 PC or a NAS) to help isolate the issue. -In progress
  

[btswein]

Good call, I forgot to mention this printer is connected via CAT6 ethernet, static IP (tried two new cables). The user at the control panel receives a "could not connect to network" error or the like, which is different than that of the EWS. However, if the user tries again 10 seconds later, it works fine.