SMB scanning on windows server 2003

[metalman1226]

We replaced a Kyocera taskALFA 3552ci with a 3553ci. The customer was scanning to a folder on their server with the 3552ci with no issues. Insert the 3553ci and it won't connect. The error code it gives is 1102. We checked everything we could think of. We had the correct credentials, we checked the folder permissions, everything on the server end. We spoke to their IT and then had Kyocera technical support remote in to the server but it yielded nothing. The 3552 will scan all day, the 3553 won't connect. Any ideas?

[copier tech]

Re: SMB scanning on windows server 2003

We replaced a Kyocera taskALFA 3552ci with a 3553ci. The customer was scanning to a folder on their server with the 3552ci with no issues. Insert the 3553ci and it won't connect. The error code it gives is 1102. We checked everything we could think of. We had the correct credentials, we checked the folder permissions, everything on the server end. We spoke to their IT and then had Kyocera technical support remote in to the server but it yielded nothing. The 3552 will scan all day, the 3553 won't connect. Any ideas?

[metalman1226]

Re: SMB scanning on windows server 2003

That was the first thing I thought of. That's usually where I start with all Kyocera problems. This one is a real bugger

[guitar9199]

Re: SMB scanning on windows server 2003

Check your network settings. I've seen some cases where if you don't have the MFP on the same Workgroup/Domain, it'll block SMB. You might also want to either match the DNS settings to what the network is pulling (ipconfig /all), or switch the DNS servers to Google DNS. (8.8.8.8 Primary- 8.8.4.4 Secondary). You should also check the IP address of the 3553, and make sure the firewall on the server is set to "allow" for that IP address.

Good luck. These can be frustrating.

[bsm2]

Re: SMB scanning on windows server 2003

check the domain

[Blizzoo]

Re: SMB scanning on windows server 2003

Not a long time ago someone here had a similar problem and the fix was: he changed the static IP (used to be the same as their old machine) to another number

[mincopier]

Re: SMB scanning on windows server 2003

Isn't server 2003 no longer supported?

Anyway could be a SMB version issue. The server may want to communicate with SMBv1 and the copier is using SMBv2.

On the server open Event Viewer, Applications and Service Logs, Microsoft, Windows. Look at errors for SMB Server and SMB Client. Would not hurt to look at the others. This should get you in the right direction.

[rthonpm]

Re: SMB scanning on windows server 2003

Isn't server 2003 no longer supported?

Anyway could be a SMB version issue. The server may want to communicate with SMBv1 and the copier is using SMBv2.

On the server open Event Viewer, Applications and Service Logs, Microsoft, Windows. Look at errors for SMB Server and SMB Client. Would not hurt to look at the others. This should get you in the right direction.

Server 2003 has been out of support for close to five years now. It can only use SMB1 and also can't accept modern TLS and packet signing methods. More than likely there's some security setting on the machine that the server can't understand. Especially since 1102 is an authentication error.

Sent from my BlackBerry using Tapatalk

[slimslob]

Re: SMB scanning on windows server 2003

check the domain

Check your network settings. I've seen some cases where if you don't have the MFP on the same Workgroup/Domain, it'll block SMB. You might also want to either match the DNS settings to what the network is pulling (ipconfig /all), or switch the DNS servers to Google DNS. (8.8.8.8 Primary- 8.8.4.4 Secondary). You should also check the IP address of the 3553, and make sure the firewall on the server is set to "allow" for that IP address.

Good luck. These can be frustrating.

Misspell the domain name and the device will not be recognized.

If one of the DNS settings is not the domain DNS netBIOS name resolution will not work. I don't know about Kyocera but Ricoh will list the rejection in its communication log. The very first Microsoft security update that affected SMB scanning blocked "out of domain" scanning and direct IP address scanning as these are methods that malicious sources use.

[rthonpm]

Re: SMB scanning on windows server 2003

The very first Microsoft security update that affected SMB scanning blocked "out of domain" scanning and direct IP address scanning as these are methods that malicious sources use.

This was issued after Server 2003 had gone end of life.

[slimslob]

Re: SMB scanning on windows server 2003

This was issued after Server 2003 had gone end of life.

But was still updated by the update I referred to did apply to Server 2003. In fact it applied to all Windows OS from XP on.

[rthonpm]

Re: SMB scanning on windows server 2003

You're thinking of the EternalBlue SMB1 patch backported to XP and Server 2003, MS17-010. The NetBIOS change in Windows was implemented in MS16-077, only for Vista/Server 2008 and newer systems.

https://support.microsoft.com/en-us/help/3161949/ms16-077-description-of-the-security-update-for-wpad-june-14-2016

So many patches to keep track of! Had to double check with my security guys.

Sent from my BlackBerry using Tapatalk