Dell Printer - can't scan to network share (login error)

I have a new C1765nfw and no matter what I try it refuses to scan to a network share. It keeps telling me it can't log in after the scan is complete (error 031-529). I've attached screenshots showing my settings, although I have tried various combinations and it hasn't worked once.




I've already tried:

- Changing the user to "HDA\Printer"
- Opening TCP port 139 on HDA (my server)
- Disabling HDA's firewall completely
- Changing the "Server Address" to "HDA" instead of "192.168.1.99" (its IP address)
- Creating a subfolder in the share and putting its name in the "Server Path" field


Any ideas what I'm doing wrong? The printer is connected to my router via WiFi and my server is connected via Ethernet.

What are the NFTS permissions (under security, not share)? Does the user have permission to write to the folder P:\Scans?

Probably not.

You probably need

HDA\Printer

As the username, the printer doesn't authenticate to the computer/domain without it.

squishy said:

What are the NFTS permissions (under security, not share)? Does the user have permission to write to the folder P:\Scans?

Probably not.

Click to expand...

Good idea but unfortunately HDA\Printer already has full permissions:

k1pp3r said:

You probably need

HDA\Printer

As the username, the printer doesn't authenticate to the computer/domain without it.

Click to expand...

As I said in the first post, I've already tried that and it makes no difference.

EDIT: I've also tried mapping "\\HDA\Scans" as a network drive on my laptop using the "HDA\Printer" login credentials, and it worked fine. Both the laptop and printer are connected to my router via WiFi so I think the problem is on the printer end, rather than with the server or router.

Does it even work if you turn off password protected sharing completely?

All Control Panel Items\Network and Sharing Center\Advanced sharing settings -> Password Protected Sharing

Nope. Tried turning that off and it has the same issue. Something I have noticed is that if I use "HDA" as the server address, it takes a while to fail (15-20 seconds). If I use "192.168.1.99" it fails almost immediately. Hmm...

I've also tried:

- Giving my printer its IP, subnet mask, and default gateway manually
- Using an Ethernet connection instead of WiFi (I have a switch so the router is bypassed entirely)
- Giving "Everyone" full access to the "Scans" share.

Still not working.

EDIT: I tried getting it to send to a different network share on a different PC on my network, which is running Windows 7. That worked fine using my own login details. So for some reason my printer just can't login to HDA correctly, even if I use the same credentials that I use every day to connect. I've double-checked the SMB settings on HDA and both SMB 2.0 and SMB 3.0 are enabled.

I can also scan successfully if I remote desktop into HDA and go to Control Panel -> Devices and Printers -> Dell C1765nfw -> Start Scan. So there's at least some kind of communication between HDA and the printer. Also, HDA's Event Viewer shows no SMB errors or warnings.

The user manual says "check password is correct" next to error 031-529. Not very useful since I know it's correct.

In the username field, can you put HDA\Printer not just printer?

(Funny Side note, I use 'Robert Scanne' for my scanner accounts at customers....username comes out to ScanneR, Last and first init)

dbwillis said:

In the username field, can you put HDA\Printer not just printer?

(Funny Side note, I use 'Robert Scanne' for my scanner accounts at customers....username comes out to ScanneR, Last and first init)

Click to expand...

Once again, I already said in the first post that I've tried this. Doesn't help.

I've now also tried scanning to a share on my Windows 8.1 laptop, which works fine. So it seems to be only shares on HDA that the printer is having problems with.

Alright, I fixed the problem. I had a look at the communication between the two machines using WireShark and I saw the printer sending requests using SMB, whilst HDA was responding using SMB2. I guess the printer only supports SMB 1.0, which is pretty bizarre considering it was superseded in 2006.

Are there any disadvantages to permanently enabling SMB 1.0 on my server? I assume all of my other machines will continue to use SMB 3.0 and SMB 2.0 where they can.

DragonQ said:

Alright, I fixed the problem. I had a look at the communication between the two machines using WireShark and I saw the printer sending requests using SMB, whilst HDA was responding using SMB2. I guess the printer only supports SMB 1.0, which is pretty bizarre considering it was superseded in 2006.

Are there any disadvantages to permanently enabling SMB 1.0 on my server? I assume all of my other machines will continue to use SMB 3.0 and SMB 2.0 where they can.

Click to expand...

You know, I had a theory something like that might have been happening, but with no evidence and no exact way to test I didn't bother mentioning it. I was also going to say maybe run netcat on the server to listen but meh, glad you got it figured out.