Results 1 to 7 of 7

Thread: 365 scanning

  1. #1
    Field Supervisor 500+ Posts kingarthur's Avatar
    Join Date
    Feb 2008
    Posts
    758
    Rep Power
    35

    365 scanning

    not sure if anyone else has had a problem, we've got a few KM machines in the field using 365 for scanning, we had a few fail on Friday, (server connect error) I changed the SMTP ( smtp.office365.com) for an IP (40.100.174.18) which seems to have done the trick
    Tip for the day; Treat every problem as your dog would.....If you cant eat it or f*ck it....then p*ss on it & walk away...

  2. #2
    Technician
    Join Date
    Sep 2016
    Location
    Nova Scotia
    Posts
    12
    Rep Power
    8

    Re: 365 scanning

    Sounds like a DNS issue. I would do a connection test on the DNS server, if they fail I would check if they have another. If not 8.8.8.8 always does the trick.

  3. #3
    Field Supervisor 500+ Posts kingarthur's Avatar
    Join Date
    Feb 2008
    Posts
    758
    Rep Power
    35

    Re: 365 scanning

    I always make sure DNS is set to 8.8.8.8 and secondary is 8.8.4.4
    Tip for the day; Treat every problem as your dog would.....If you cant eat it or f*ck it....then p*ss on it & walk away...

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

    Re: 365 scanning

    Quote Originally Posted by kingarthur View Post
    I always make sure DNS is set to 8.8.8.8 and secondary is 8.8.4.4
    I always set those as the second and third DNS. In order for local name resolution to function properly the primary DNS must be a local device.

  5. #5
    Technician
    Join Date
    Jan 2019
    Location
    Ohio
    Posts
    42
    Rep Power
    2

    Re: 365 scanning

    Quote Originally Posted by slimslob View Post
    I always set those as the second and third DNS. In order for local name resolution to function properly the primary DNS must be a local device.
    This for sure. Google's DNS won't help with internal resolution, so you will want the primary DNS to match the Default Gateway for internal resolution (smb scanning etc) and the secondary/tertiary DNS to be 8.8.8.8/8.8.4.4 -- this will be useful for external connections such as KFS or SMTP tx

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

    Re: 365 scanning

    Quote Originally Posted by Xer0615 View Post
    This for sure. Google's DNS won't help with internal resolution, so you will want the primary DNS to match the Default Gateway for internal resolution (smb scanning etc) and the secondary/tertiary DNS to be 8.8.8.8/8.8.4.4 -- this will be useful for external connections such as KFS or SMTP tx
    Or in the case of a local Domain, the primary domain DNS.

  7. #7
    Technician
    Join Date
    Jan 2019
    Location
    Ohio
    Posts
    42
    Rep Power
    2

    Re: 365 scanning

    Quote Originally Posted by slimslob View Post
    Or in the case of a local Domain, the primary domain DNS.
    yeah, I actually intended to qualify that as "typically" but I guess I miscommunicated it. I think in my year doing this I've encountered someone with a DNS that didnt match their DG all of twice. But you are in fact correct

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