cancel
Showing results for 
Search instead for 
Did you mean: 
1 Reply
Joe Arseneau
Valued Advisor
Valued Advisor

Re: SMB workflow scanning - 5875 & 7855

I would have to assume you are using old firmware, which I would also guess to be 073.xxx.xxx.34540 specifically. Which is from 2015

 

If that is the case, simply update both to current and it will just start working with no loss of data, and if it doesn't, you can simply do a Wireshark, which is now conveniently built into the printer (the capture, you still need to use a viewer to read it)

7855

58XX

The Trace feature in current firmware is at CWIS > Properties > Security > Logs > Network Troubleshooting It is not in releases before 2017

1.JPG

 

For reference, you can find a firmwares date from its version number

Firmware decoding.png

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe Arseneau
0 Kudos
Rigo
New Member
New Member

SMB workflow scanning - 5875 & 7855

Product Name: Other - specify product in post

I have a DFS server with multiple network drives, I continue to get the following error.

"Job Deleted. No messages were sent. Login error."

smb1.PNG

Share Name: \\dc.loc\global\

Share Permissions: Everyone (Full) + domainadmin(Full)

Permissions at the drive level G:\Global\  (domainadmin has Full permissions)

Attempted to scan to folder and same error: "Job Deleted. No messages were sent. Login error."

=============================================================

Here's an interesting thing I found out.

If I create a share without creating a namespace in DFS I can scan to the drive successfully. 

Example: If I create a folder under the "G:" drive in my file server. I right click on the folder and shared with same permissions as my Global. I was able to scan successfully. 

Why can I not scan over to my share folders using a DFS namespace vs those who are regular share folders in a drive ?

smb2.PNG

 

 

0 Kudos