I can't possibly answer that as I don't have your setup.
But I can scan to 10.13.2 in the lab without issue after doing all I provided.
thanks for your reply.
i've managed to fix some but not all of the issue. i found that you can't edit a previously stored scan destination (which was ftp) and change it to smb, but i deleted all the ftp connections and created new smb connections for each of the updated macs.
what's now weird is that i can scan to one of the macs but not the others, even though they are setup the same. the only difference is the mac i can scan to is running 10.13.3 beta while the others are running 10.13.2. could that be it?
Depends on what Apple broke.
If you were using FTP, Apple removed that ability, now you will need a 3rd party FTP service.
If it was a simple SMB setup, it may have killed your share, or upgraded from SMBv1 to SMBv2 or 3. IN that case, a simple firmware update could resolve it.
And if it wasn't 10.13 that broke it, it was likely Security patch 2017-01, which again, caused by Apple, and the fix is here (Excerpt below)
If you experience issues with authenticating or connecting to file shares on your Mac after you install Security Update 2017-001 for macOS High Sierra 10.13.1, follow these steps to repair file sharing:
3 of our office macs have been updated to high sierra. since then i'm not able to scan (using the scan to network function) to any of these macs.
has anyone got a workaround for this?