Ricoh port 139 vs 445 smb scanning

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aviso66
    Trusted Tech

    100+ Posts
    • Dec 2012
    • 202

    #1

    Ricoh port 139 vs 445 smb scanning

    Hi,

    for laptops with windows 7 and above, can i keep the machine at port 139? Bec port 445 as i understand that it uses tcpip scanning.
    bec most of the time i am using the computer name\sharefolder for scanning setup.
  • PrintWhisperer
    Trusted Tech

    250+ Posts
    • Feb 2018
    • 452

    #2
    Re: Ricoh port 139 vs 445 smb scanning

    Originally posted by aviso66
    Hi,

    for laptops with windows 7 and above, can i keep the machine at port 139? Bec port 445 as i understand that it uses tcpip scanning.
    bec most of the time i am using the computer name\sharefolder for scanning setup.
    "Being ignorant is not so much a shame, as being unwilling to learn" - Benjamin Franklin

    Comment

    • slimslob
      Retired

      Site Contributor
      25,000+ Posts
      • May 2013
      • 36699

      #3
      Re: Ricoh port 139 vs 445 smb scanning

      Originally posted by aviso66
      Hi,

      for laptops with windows 7 and above, can i keep the machine at port 139? Bec port 445 as i understand that it uses tcpip scanning.
      bec most of the time i am using the computer name\sharefolder for scanning setup.
      The main difference NetBios over IP on Port 139 and TCP/IP Port 445 is one is for local networks and the other supports internet communication. Port 139 is the older of the two and uses NetBIOS/NETBUI. NetBIOS is an older transport layer that allows Windows computers to talk to each other on the same network. The key term here is "same network."

      Later versions of SMB (after Windows 2000) began to use port 445 on top of a TCP stack. Using TCP allows SMB to work over the internet.

      SO unless you want bad actors coming off the internet, leave NetBios enabled and use NetBIOS name resolution. Using IP address is not a good idea. One of the first patches that Microsoft put out that caused problems for Scan to Folder over SMB treated IP address scans as coming from outside the local network, i.e. a malicious source. The only machines I serviced that had problems had been using IP address. One other thing, make sure everything is either on a domain with the first DNS being the domain DNS thereby getting name resolution from Active Directory Services or for peer to peer they are all in the same workgroup.

      Comment

      Working...