If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Does anyone know of a fix for the SMB scanning issues that started in the last couple days with windows 7 computers ever since the new update?
Any info would help.
After update if you are getting this> "Server Connection Error" then do this> Go to Control Panel>Turn windows features ON/OFF>Telnet Client=un check, Telnet Server=uncheck, or SMB>Telnet Client/Telnet Server= uncheck
apply and restart.
Then try sending.
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
After update if you are getting this> "Server Connection Error" then do this> Go to Control Panel>Turn windows features ON/OFF>Telnet Client=un check, Telnet Server=uncheck, or SMB>Telnet Client/Telnet Server= uncheck
apply and restart.
Then try sending.
So I sent the original question in this thread. Removing the update definitely works, but id prefer to just make the adjustment needed for smb. Will your suggestion definitely work? I will be trying it tomorrow.
Here's what we did to make it work. When entering the user name, enter "//computer name/user name"
The issue in this month's Windows 7/Server 208 R2 patches are related to back end authentication issues.
You'll have issues if your scanning is set using one, or both, of the following:
1. Scan destination is set using an IP address instead of a host name
2. You're using a local account, instead of a domain account, to authenticate to the share with the account used also being an administrator on the PC or server hosting the share
So I sent the original question in this thread. Removing the update definitely works, but id prefer to just make the adjustment needed for smb. Will your suggestion definitely work? I will be trying it tomorrow.
No need to remove update. Just restore the changes made by update in SMB and file sharing.
I just had this issue come up last Friday, customer called in saying her scanning to PC was not working. It's a one PC office that has been working fine for months. She was scanning fine all day Wednesday, then first thing Thursday morning it errors out with a "Forward TX Error" under job list > details.
I tried everything I could think of, I figured something was installed that she didn't know about, didn't think to mess with the Windows updates. I ended up just setting her PC to scan to FTP using the old FTP utility. Next time she calls in for service (probably when her IP changes and FTP stops working) I'll look for these updates and try to get her back on SMB.
We are done with SMB scanning. It isn't reliable enough anymore. We are switching everyone to email scanning. Once it is setup it is much easier for user to create new one-touches.
We are done with SMB scanning. It isn't reliable enough anymore. We are switching everyone to email scanning. Once it is setup it is much easier for user to create new one-touches.
Emphasis on "once it is set up"
I have far too many IT departments who haven't got a clue as to what info/settings they need to supply us in order to get scan to email working, usually those are the ones using office365 or gmail for scanning . But yes, once set up, it is the best method for scanning IMO.
Comment