KM 2560 SMB Scanning issue

[aopinc]

Anyone seen this before? Nine months of scan to folder no problems. Suddenly it quits. Being a copier connectivity specialist I checked the path, the credentials and basically anything network related. I found a Trend Micro internet security firewall and turned it off. Very next scan worked. I turned on the windows firewall which almost never effects smb, scan failed. I turned it back off and the scans still fail. The error code is 2203. That would make me think router, but it will scan to e-mail just fine, print and access command center. I have only been doing network copier connectivity for 6 yrs and I am temporarily stumped. Any ideas would be great. I am pretty new to the Kyocera line.

[Jules Winfield]

Re: KM 2560 SMB Scanning issue

One thing to check (and maybe you have already) is the AD user account that was used for the Scan to SMB setup. Check to make sure the password for it hasn't changed or expired or something.

[Venom]

Re: KM 2560 SMB Scanning issue

You should always allow exception in windows firewall for Scan File Utility

[aopinc]

Re: KM 2560 SMB Scanning issue

No passwords have changed or expired. This is a very simple network. 3 end users, no server. I am replacing the router power supply now since they have had some internet and network issues as well. I hope that will be a fix. To venom, Is the windows firewall exception a Kyocera thing? I have not had to allow an exception for scanning since back in the days of scanrouter or other softwares that controlled scanning. I have set-up and managed hundreds of clients since then. Though I will admit that Windows 7 does seem to be very picky compared to XP. Now that the machines use true SMB sharing, as long as that folder is shared properly there should be no firewall issues. Also the firewalls are all turned off and I am still having the same problem. Thanks for the replys guys.

[blsquires]

Re: KM 2560 SMB Scanning issue

error 2101= can not connect (enter disable host name ip address) assigned the wrong port number network not connected.

check 1. enter the correct host name or ip address. 2 enter correct port number. 3 check if server is working properly check the network connection (network condition within lan etc. cable )

[Venom]

Re: KM 2560 SMB Scanning issue

To venom, Is the windows firewall exception a Kyocera thing? Thanks for the replys guys.

Having reread this I realize that you don't use Scan File Utility on that model and no you shouldn't need to mess with the firewall for SMB scanning. Check if Gateway is proper, I would also try to use IP address instead of host name just to see if the DNS is working. Try to set up on your laptop to see if it works. Maybe set up a new user on customer's PC and see if it works.

[blackcat4866]

Re: KM 2560 SMB Scanning issue

I'm a little unclear on: Is this SMB or FTP scanning? What port number are you using and is it open? =^..^=

[habik]

Re: KM 2560 SMB Scanning issue

As Venom suggested, check the scan to IP in stead of Host name to see if DNS is OK and then set correct DNS Primary, secondary...

Is it Domain controlled?

is it home/work or public network?

I hate Trend micro!!

[aopinc]

Re: KM 2560 SMB Scanning issue

DNS is good. I checked all those settings. I also tried to scan using IP address as path instead of host name. Although the fail happens almost instantly with the ip settings which tells me there is a path communication or authentication error. It is not Domain controlled. It is a work network. Blackcat, not sure what your unclear on, it is SMB direct scan to folder. It makes no sense that it will scan to e-mail, and it scanned to folder yesterday once yet failed 10 other times. I have seen some really odd things caused by routers. I have even seen e-mail issues fixed by replacing a router. Thats my next step. I will keep my fingers crossed that it will work! Thanks for all the replies and if any thoughts or ideas come up let me know. Thanks

[blackcat4866]

Re: KM 2560 SMB Scanning issue

You left out those three little letters: SMB or FTP or SMTP or TWAIN. I didn't see any of those, up until now. And what about the port? 139? 445?
=^..^=

[aopinc]

Re: KM 2560 SMB Scanning issue

It is using port 139 which windows opens when you allow full controled sharing. I haven't ever had to change a port on SMB. Some scan utilities require different ports but nothing like that is being used. Plus the firewall is off. Sorry I left that out, it is in the title and on the other repiles so I didn't think about it. Thanks for your help.

[aopinc]

Re: KM 2560 SMB Scanning issue

It is using Port 139. Never needed to change that before. Sorry if I left those out It is in the Title and my replies so I didn't think about it. Thanks for your help.

[Venom]

Re: KM 2560 SMB Scanning issue

Couple more things....Is the scan folder shared and does everyone have the rights to read and write?

[its not that easy]

Re: KM 2560 SMB Scanning issue

OK here's my two cents worth. Did you check for a duplicate IP address? It could be that your scans are being routed to another device on the network with the same address as the computer you're trying to scan to. It's real easy to check. unplug the network cable from the computer and ping the IP address. If you get a reply.... Well, you know what that means. I've seen this happen a number of times. The customer's IT people will inadvertently assign an address that's in the DHCP pool, and voila! Instant conflict.

Anyone seen this before? Nine months of scan to folder no problems. Suddenly it quits. Being a copier connectivity specialist I checked the path, the credentials and basically anything network related. I found a Trend Micro internet security firewall and turned it off. Very next scan worked. I turned on the windows firewall which almost never effects smb, scan failed. I turned it back off and the scans still fail. The error code is 2203. That would make me think router, but it will scan to e-mail just fine, print and access command center. I have only been doing network copier connectivity for 6 yrs and I am temporarily stumped. Any ideas would be great. I am pretty new to the Kyocera line.

[aopinc]

Re: KM 2560 SMB Scanning issue

Just an update. I replaced the router, scanning is back up and running fine. Thanks for all the replies and help!