OK, I'll try to make this short, KM3050 SMB scanning to a Windows 2003 server as a DC. Setup a new "user" called kyocera with the same password still giving login error. Gave kyocera user full access to the scan folder, login error. Connected laptop to the network and got an IP from the DHCP server and scanned to my laptop just fine, laptop is not part of the domain though. Tried to scan to an XP workstation, login error. Even tried to disable the SMB packet signing with the IT person with no luck. Used the customers login, DOMAIN/login name and just the login name, login error. Signed off a user and logged in using the kyocera username and pass and I was able to move files in and out of the scanning folder so I know that username has full rights to the folder. Reflashed firmware on copier just because and still login error. Rechecked IPs, DNS, and domain entry with no luck. Did I leave anything out...wheww that was a lot.

SMB won't work on server 2003

Kyocera made a scanner utility for the 30, 40 and 50 for server 2003.

It's on KMA

quote:

Originally posted by RZiggy:
SMB won't work on server 2003

Kyocera made a scanner utility for the 30, 40 and 50 for server 2003.

It's on KMA

Firmware 2.03B was supposed to fix that issue.

If you need it, Tech Bulletin 2 describes how to use the special Scanner File Utility.

quote:

DOMAIN/login

I thought domains used a backslash.

This message has been edited. Last edited by: aragul,

The account that you setup, Is it a power user or a network admistrator. If it isn't, it has to be in order to have SMB to work. A regular user doesn't work on 2003 server.

Hope this helps

Doedee316

User is part of the admin group. Firmware is full updated. Didn't want to run the special file utility as customer wants to scan to multiple folders.

Scanner file utility allow scanning to multiple folders.

PLEASE CLARIFY - Is there really a 'Special Scan File Utility' program specifically for 30-5050 MFP style machines, because I cant find anything on KM UK login. I hate SMB and am naturally VERY keen to know. I have no login for KMA here in UK so a link or email of this program (if it exists) would be great!!!!

Regards,
Mark

I have customers scanning SMB just fine to 2003 server.

In fact, I was at a customer yesterday that had DNS issue. We changed the server host name to IP address and SMB scanning started to work again.

I dont have many customers scanning to folder these days. Email is so much easier to setup and maintain.

There is a special Scan File Utility alright, but it's intended use is the Voyager and Harrier Series machines. The FalconIII machines do not require a scan file utility. To the best of my knowledge none exists for them. =^..^=

Well actually, the file utility for Falcon III does exist and it was written specifically to connect with Server 2003. SMB scanning can be accomplished with Server 2003, but it creates a lot of security problems that most IT admins won't allow.

Just a couple of weeks ago I had to set up scanning from an 1820 to Server 2003. The FTP route was a no-go as the IT admin was really a Mac person and not very good with Windows.

I went back to my notes regarding SMB scanning from the "Boot Camp" for the Falcon III machines and discovered a file with directions for SMB scanning to Server 2003. By default SMB is digitally signed in Server 2003, and that must be turned off in order to make scanning work. I could not successfully scan until I did this procedure. Here is the text of that document:

Title : Push Scanning via SMB to a Windows 2003 Server
Problem :
When attempting to scan a document to a shared folder on a Windows 2003 Server in an Active Directory domain using SMB, the copier is unable to logon. You can browse to the server, but cannot logon. When you enter the credentials (user name and password) to logon, they are rejected.

Solution :
This only happens when Active Directory 2003 is used for the domain. When there is no Active Directory, it will accept the logon credentials. This issue is detailed in Microsoft's Knowledgebase in article # 811497 (http://support.microsoft.com/default.aspx?scid=kb;en-us;811497 ).
It appears that Windows 2003 Server Active Directory requires SMB signing for secure communication. This also applies to any member server in the Windows 2003 domain. You cannot scan to any server that is part of a Windows 2003 Active Directory domain. It also does not matter whether you use an administrator account or regular user account.

I. This server feature can be turned off as the Microsoft article explains:
1.If the server is a member server, open the Group Policy Editor. Click Start, Run, type in gpedit.msc, and hit OK.

* If the server is a Domain Controller, click Start, Settings, Control Panel, Administrative Tools, Domain Controller Security Policy. This will open the Default Domain Controller Security Settings window.
2.In the Group Policy Editor, open the Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options folder.

* In the Default Domain Controller Security Settings window, select Local Policies, Security Options.
3.Locate the 'Microsoft network server: Digitally sign communications (always)' policy setting, and then click Disabled or Do Not Configure.

* If this option is grayed out in your Group Policy Editor, you are not logged in as an Administrator or you are working on a Domain Controller. Either login using an Administrator account or use the Domain Controller Security Policy tool (as described above).
* Note - It may take some time (possibly hours) for the new group policy to be applied. After you make changes to group policies, you may want the changes to be applied immediately, without waiting for the default update interval (90 minutes on domain members and 5 minutes on domain controllers) or without restarting the computer. To make this update, at a command prompt, run the Gpupdate.exe utility. For more information on this utility, please see Microsoft KB article 298444 (http://support.microsoft.com/default.aspx?scid=kb;en-us;298444&Product=winsvr2003).
To apply the changes you made to the group policies immediately:
1. Click Start, then Run.
2. Type in 'gpupdate /force' and hit OK.

Chris, You're a star for posting that!
Just so happens that Im here to post simular so you've saved me from typing!
I just found out about those group policy settings also.

Mark

Digital Signing was the original problem that prompted Kyocera to modify the scan to file utility in the first place. The current firmware does digitally sign the scan.

The above mentioned posts DECREASE the server's security and should NOT be recommended to any customer. Most network administrators aren't going to let you touch their group policy settings anyway.

Credentials require FQDNS signing and as I recall are case sensitive - but not in the traditional sense. I have only done this a couple of times since most of my customers that have a DC also have an exchange server and prever scan to email and use LDAP.

The case sensitivity is not what you would normally expect - the domain name MUST be in uppercase letters or it will be ignored - ie:
"DOMAIN\user"

It is also important to make sure that the time on the machine jives with the server time and time zone - otherwise it may reject it as well.

This post has turned into a goldmine of info. For example I didn't know that domain names needed to be in CAPS! that could explain some other failures

- thanks to all that post!

Scoful / Doug1948 could either of you direct me to or send a copy of this elusive Special scan file utility please? Still intrigues me!

and Kyotech - did your issue get sorted?

Regards to all
Mark

http://www.kmaconnect.com/dnetpub/jsp/Kyocera/ResourceDetails.jsp?rid=17184
Tech Bulletin #2 page has a link to it...

Scoful - thanks for the link, but it is dead. Probably because Im in the uk and cannot log in to KMA! KME and KMUK technical sites don't list anything about this, which is why Im so intrigued
Could you email me something?

Thanks in advance
Mark

This message has been edited. Last edited by: UKTeam,

UK send me an e-mail and I will send it to you.
hcom@nctv.com

Thanks Doug..

SMB Scanning definately works with server 2003, without changing the security settings. This used to be a packet signing issue, but as previously mentioned has been fixed with firmware. If your machine has up to date firmware then the issue is either with the folder path or the login.

Use the IP address as the Host Name, for the path just use the share name of the file, no c:\ etc. It gets more complicated with mapped network drives, but does work. User name should be DOMAIN\user or user@domain, which just leaves the password.

The error code you get when you try to scan should point you towards the problem. What code do you get?

The SFU does exist. I believe it's just the latest version of the regular SFU which you need to activate 'Enterprise Mode' on the machine to use. It then works through the application button when activated.

szt001 - thankyou, for that last piece of the puzzle! On metric machines in the uk Enterprise setting is default off. Finally I have a working back-up option. Im so grateful to all who post....

regards,
Mark