I can get the scan to file to work for an hour or so (multiple successful test scans), then after a few hours/overnight my co-worker goes to use the scanner and the scan fails. The log shows a 2D62 error. There are three computers on the network suffering from the above problem while three other computers on the same network have been able to scan perfectly for months with seemingly identical setups. What am I missing? It's frustrating that it works for a couple hours and then fails. Am I missing something? Any thoughts are greatly appreciated! See below for connection details. Thanks.
Our office has a Toshiba 6520c. Scanning is currently set to Remote 1 SMB. I use the network path \\IPADDRESS\Scans with a username and password created specifically for scanning. The User is the owner of the scan file which is located on the C: drive. The IP address is obtained automatically, but I check ipconfig and use the one displayed when entering the IPADDRESS in the network path. Some computers are hooked up to switches, while others connect directly to the wall jack. There is no apparent relationship between successful scanning and how the computer connects to the network.
All permissions are set to:
1) Administrator - full control
2) Current User - full control
3) Scanner User - full control
Our office has a Toshiba 6520c. Scanning is currently set to Remote 1 SMB. I use the network path \\IPADDRESS\Scans with a username and password created specifically for scanning. The User is the owner of the scan file which is located on the C: drive. The IP address is obtained automatically, but I check ipconfig and use the one displayed when entering the IPADDRESS in the network path. Some computers are hooked up to switches, while others connect directly to the wall jack. There is no apparent relationship between successful scanning and how the computer connects to the network.
All permissions are set to:
1) Administrator - full control
2) Current User - full control
3) Scanner User - full control
Comment