Bizhub 283 - Trouble setting up scanning with SMB protocol

[odv]

Re: Bizhub 283 - Trouble setting up scanning with SMB protocol

not really sure what you mean by the last one. the printer is already set up on the network and all computers access it. i read something about creating a separate user just for it but we have a pretty tight policy about users so i used my server account.
if you could provide an example itd really help. we have a number of files within the server, say server\\v:\ and then a number of files that have restricted access; my account for example, can access all those files, so whats the problem with me using my credentials for the printer? would it trigger if its noticing two devices using the same credentials?

ok scratch that last one, now the error is "no folder specified"
filepath must be off

[TheOwl]

Re: Bizhub 283 - Trouble setting up scanning with SMB protocol

not really sure what you mean by the last one. the printer is already set up on the network and all computers access it. i read something about creating a separate user just for it but we have a pretty tight policy about users so i used my server account.
if you could provide an example itd really help. we have a number of files within the server, say server\\v:\ and then a number of files that have restricted access; my account for example, can access all those files, so whats the problem with me using my credentials for the printer? would it trigger if its noticing two devices using the same credentials?

The last one is to make sure that your machine is enabled for NTLM v1/v2 because Konica Minolta devices out of the box are enabled for NTLM v1 only. AD and later versions of Windows Server required user authentication via NTLM v2.

The reason why you would use an account specific to the machine or your MFD fleet is that user passwords change, so you would then have to change all the passwords stored in the devices. Using an account for the machine allows you to set security permissions around the machines and to use a highly complex password that will never change.

When you say server\\v:\ you are referring to a physical drive within your server and not a UNC path. When setting the one-touch, it should look something like:

Host: server
File: sharename\childname

[odv]

Re: Bizhub 283 - Trouble setting up scanning with SMB protocol

The last one is to make sure that your machine is enabled for NTLM v1/v2 because Konica Minolta devices out of the box are enabled for NTLM v1 only. AD and later versions of Windows Server required user authentication via NTLM v2.

The reason why you would use an account specific to the machine or your MFD fleet is that user passwords change, so you would then have to change all the passwords stored in the devices. Using an account for the machine allows you to set security permissions around the machines and to use a highly complex password that will never change.

When you say server\\v:\ you are referring to a physical drive within your server and not a UNC path. When setting the one-touch, it should look something like:

Host: server
File: sharename\childname

yeah, we figured out yesterday that instead of putting the ip on host we'd just put server and filepath shared folder\...

how come the IP wouldn't work better than the name?

[TheOwl]

Re: Bizhub 283 - Trouble setting up scanning with SMB protocol

yeah, we figured out yesterday that instead of putting the ip on host we'd just put server and filepath shared folder\...

how come the IP wouldn't work better than the name?

Does the server have multiple IP addresses?

[habik]

Re: Bizhub 283 - Trouble setting up scanning with SMB protocol

yeah, we figured out yesterday that instead of putting the ip on host we'd just put server and filepath shared folder\...

how come the IP wouldn't work better than the name?

Host Name used "host box checked"
IP used "host box unchecked"




Sent from my iDon't believe in marketing device using Tapatalk