Create an account on the HP Community to personalize your profile and ask a question
10-07-2022 06:30 PM
- We have an HP LaserJet Enterprise MFP M630
- Firmware Bundle Version: 4.12
- Firmware Revision: 2411221_066372
- Firmware Datecode: 20220824
- HP FutureSmart Level: HP FutureSmart 4
- Firmware was updated from 4.11 today to hopefully resolve the issue. But it didn't.
- Archive received faxes to a network folder that is on a non-Windows server.
Relatedly, scan to a network folder on this same server.
- A valid UNC folder path is entered.
- Windows Domain field is blank. Why? Because this server is not and cannot be part of our Windows Domain. It is a third-party, non-Windows, but business vital Linux server that needs to be independent of AD.
- User name and password fields are blank.
Please correct the errors below and try again.
- Windows Domain is required.
- User Name is required.
- Password is required.
- This issue is also encountered when setting up new scan to network locations on this same server.
- These issues began when a technician "upgraded" to the 4.x version of the firmware last year when the device's hard drive was replaced and he installed 4.x -- even though we didn't request the drive be replaced. We presume he noted a S.M.A.R.T. condition to justify the replacement.
- We did not have this issue in the previous 3.x firmware version. Our old scan to network folder entries to this server that existed prior to the firmware "upgrade" still work just fine.
- It is obviously not an access or authentication failure as the previous scan to network folder settings that were configured in 3.x still work just fine and, I remind you, Verify Folder Access succeeds!
- It is a failure of the workflow logic that DEMANDS that a Windows Domain, User name, and Password be entered. (THESE FIELDS SHOULD NOT BE REQUIRED)
- Maybe there's a setting somewhere that is forcing me to enter those fields. But I haven't found it.
- As a last resort, I removed the domain in the Network settings tab and restarted the device. But it didn't help.
10-08-2022 10:24 AM
Typically in non-domain applications you would use the workstation name as the domain name and then user name and password. For security reasons HP does not allow nonauthenticated scanning.
I am a volunteer, offering my knowledge to support fellow users, I do not work for HP nor speak for HP.
10-10-2022 03:35 PM
Thank you for your response. Unfortunately, it did not work.
Although we have several working Quick Sets that connect to a share on one of our Windows servers on our local domain, the network share that fails is on a Linux server that is not on our local domain -- as I explained in the original post. It is not a "WORKGROUP" computer.
To make a correction to my original post, I was reminded that the previous settings did not actually carry over from the firmware upgrade. We had to recreate them. The one 'Scan to Folder' Quick Set to the Linux server also does not work. (I missed that it failed the 'Verify Access' test.) The symptoms are the same -- except, the Quick Set interface allows me to save the Quick Set with valid AD credentials even though any AD credential would fail the 'Verify Access' test on that Linux server. Sure enough, I get a printed failure notification when I try to scan to that location.
I called the vendor that controls the Linux server. I was told that there actually should be credentials set up on the Linux server for authentication to those shares. We tried several variations in the 'Windows Domain' field including, the server's hostname, FQDN, IP address, blank, etc. All would fail the 'Verify Access' test even though the username and password are apparently correct. Though, the technician I spoke to is going to double check with his team members to make sure something wasn't overlooked. My thinking is that maybe devices may need special permissions-- or something. (I'm not a Linux expert.)
I appreciate the 'Security' aspect, and I acknowledge that you're not an HP employee. But 'Verify Access' should be consistent and fail as well, and there should be a bit more transparency regarding mixed networks environments, such as ours.
Thanks for trying.
Didn't find what you were looking for? Ask the community