Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Junior Member
    Join Date
    Jun 2019
    Location
    Savannah
    Posts
    2
    Rep Power
    0

    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?

  2. #2
    Service Manager 2,500+ Posts
    SMB scanning on windows server 2003

    copier tech's Avatar
    Join Date
    Jan 2014
    Location
    London
    Posts
    3,579
    Rep Power
    66

    Re: SMB scanning on windows server 2003

    Quote Originally Posted by metalman1226 View Post
    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?
    Worth updating the firmware incase this is a known issue however iím sure Kyocera would have got you do this anyway.
    Let us eat, drink, and be merry, because tomorrow we may die!

    www.copierfirmware.co.uk

  3. #3
    Junior Member
    Join Date
    Jun 2019
    Location
    Savannah
    Posts
    2
    Rep Power
    0

    Re: SMB scanning on windows server 2003

    Quote Originally Posted by copier tech View Post
    Worth updating the firmware incase this is a known issue however iím sure Kyocera would have got you do this anyway.
    That was the first thing I thought of. That's usually where I start with all Kyocera problems. This one is a real bugger

  4. #4
    Field Supervisor 500+ Posts
    SMB scanning on windows server 2003

    guitar9199's Avatar
    Join Date
    Sep 2016
    Location
    Eveleth, MN
    Posts
    946
    Rep Power
    26

    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.

  5. #5
    IT Manager 1,000+ Posts bsm2's Avatar
    Join Date
    Feb 2008
    Location
    Florida
    Posts
    1,618
    Rep Power
    42

    Re: SMB scanning on windows server 2003

    check the domain

  6. #6
    Senior Tech 250+ Posts
    SMB scanning on windows server 2003

    Blizzoo's Avatar
    Join Date
    Aug 2013
    Location
    east europe
    Posts
    343
    Rep Power
    17

    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
    Defects are simple, our mind is complicated

  7. #7
    Senior Tech 100+ Posts
    Join Date
    Dec 2015
    Location
    Pooler, GA
    Posts
    231
    Rep Power
    11

    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.

  8. #8
    Service Manager 1,000+ Posts rthonpm's Avatar
    Join Date
    Aug 2007
    Location
    Pennsyltucky
    Posts
    1,804
    Rep Power
    55

    Re: SMB scanning on windows server 2003

    Quote Originally Posted by mincopier View Post
    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

  9. #9
    Retired 5,000+ Posts slimslob's Avatar
    Join Date
    May 2013
    Location
    Bakersfield, CA
    Posts
    9,604
    Rep Power
    209

    Re: SMB scanning on windows server 2003

    Quote Originally Posted by bsm2 View Post
    check the domain
    Quote Originally Posted by guitar9199 View Post
    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.

  10. #10
    Service Manager 1,000+ Posts rthonpm's Avatar
    Join Date
    Aug 2007
    Location
    Pennsyltucky
    Posts
    1,804
    Rep Power
    55

    Re: SMB scanning on windows server 2003

    Quote Originally Posted by slimslob View Post
    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.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Get the Android App
click or scan for the Copytechnet Mobile App

-= -= -= -= -=


IDrive Remote Backup

Lunarpages Internet Solutions

Advertise on Copytechnet

Your Link Here