Does anyone know if this will require a firmware update from the win 10/server 2012 firmware or does 2016 use the same SMB version as 2012?
-
-
Re: Server 2016 scanning
Possibly Network Support Firmware -
Re: Server 2016 scanning
Also depends what model you are referring to?
The new 04's will be fine as will the 03's unless you have some of the early models on factory FW.Let us eat, drink, and be merry, because tomorrow we may die!
For all your firmware & service manual needs please visit us at:
www.copierfirmware.co.uk - www.printerfirmware.co.uk
Comment
-
Re: Server 2016 scanning
So far I have not had to update firmware to scan to Server 2016 which is basically Server 2012 R2 with some minor changes. The only problems I have is encountered required have had to do with proper network settings on the MFP. Domain name name must be correct in order for the Domain DNS to recognize the MFP. MFP DNS must be set to local primary and secondary DNS. Computer name and not IP address must be used.Comment
-
Re: Server 2016 scanning
It was an LW426. The firmware to allow for scanning to server 2012 win 8/10 worked with no other changes needed.Comment
-
Re: Server 2016 scanning
Server 2016 is just the server version of Windows 10 so if you can scan to the latter it will work with the former.
The run down of server versions to desktop versions that are most commonly seen in the field are:
Server 2003 = Windows XP
Server 2003 R2 = Windows XP SP 2
Server 2008 = Vista
Server 2008 R2 = Windows 7
Server 2012 = Windows 8
Server 2012 R2 = Windows 8.1
Server 2016 = Windows 10Comment
-
Re: Server 2016 scanning
Make sure to check your NetBIOS settings in the IP v4 protocol. If it's set for "NetBIOS over DHCP", I've seen that cause SMB scans to fail. Setting it to "NetBIOS over TCP/IP" resolves the issue.
Also be sure the network connection is set to "Private".
Good luck.Comment
Comment