Hi, Is it necessary to enable netbios for scan to folder?

[aviso66]

Hi,

I am just checking if it is required to enable NetBIOS for TCP/IP for scan to folder?
Does it solve anything?

I saw it from here:

http://www.tsrc.ricoh-usa.com/pwhp/S...te%20Paper.pdf

thanks

[gkalman2004]

Hi,

I am just checking if it is required to enable NetBIOS for TCP/IP for scan to folder?
Does it solve anything?

I saw it from here:

http://www.tsrc.ricoh-usa.com/pwhp/S...te%20Paper.pdf

thanks

If you have fixed ip address then you not use it, but if your network use dhcp to assign automaticaly ip's to pc's , laptops etc.. you may want to print\scan to a machine name not to ip .
So you will choose \\printer-name not \\192.168.1.x to address the printer/machine.
In this second case you will need Netbios and Wins for name services
( The Name Service, according to RFCs 1001 and 1002, is called NetBIOS Naming Service or NBNS. Microsoft WINS is an implementation of NBNS.)

[slimslob]

If you have fixed ip address then you not use it, but if your network use dhcp to assign automaticaly ip's to pc's , laptops etc.. you may want to print\scan to a machine name not to ip .
So you will choose \\printer-name not \\192.168.1.x to address the printer/machine.
In this second case you will need Netbios and Wins for name services
( The Name Service, according to RFCs 1001 and 1002, is called NetBIOS Naming Service or NBNS. Microsoft WINS is an implementation of NBNS.)

One other thing, if it is a domain network with Server 2012R2 or Server 2016, the domain name must be correct on the MFP, the first DNS on the MFP must be the primary local domain DNS and you must use netbios name in order to scan to folders on the server. A recent Microsoft update to server blocks scan by IP address and by netbios name from any device not a member of the domain.

[rthonpm]

NetBIOS was an old component of the WINS networking protocol. DNS has replaced, and surpassed, WINS in almost all network environments. Unless you're dealing with very old devices (10xx - 30xx series) there's no real need for netBIOS to be turned on. For never equipment, so long as the domain name in Network Settings and the workgroup name in SMB settings correspond to the internal domain name you should be alright.

For all intents and purposes, unless you have an active WINS server on the network, keeping netBIOS turned on in a Windows network doesn't really do anything.

[gkalman2004]

NetBIOS was an old component of the WINS networking protocol. DNS has replaced, and surpassed, WINS in almost all network environments. Unless you're dealing with very old devices (10xx - 30xx series) there's no real need for netBIOS to be turned on. For never equipment, so long as the domain name in Network Settings and the workgroup name in SMB settings correspond to the internal domain name you should be alright.

For all intents and purposes, unless you have an active WINS server on the network, keeping netBIOS turned on in a Windows network doesn't really do anything.

When WINS is still required

If you still have any client computers running (OMG) Windows 95, Windows 98 or Windows ME in your environment, you'll still need WINS around so these clients can find domain controllers so their users can log on to your network. And if you still have any member servers running Windows NT 3.51 or Windows NT 4.0 , they'll need WINS as well. Sometimes an organization will keep an old server or client computer around because it controls or monitors some industrial system and they don't want to (or have any idea how to) upgrade the system while ensuring the legacy control software still works properly. Ex. Ricoh 240W plotter with legancy board and software instaled on WinXP.
WINS will also be required if you have any legacy applications still running that have a dependency on NetBIOS name resolution either because of the way the application is configured or how it has been coded.