I have been using the 3635 scan via SMB on two XP machines without issue for the last few years. Recently we decided to upgrade one of the machines to 8.1 and we are having one heck of a time getting the scan via SMB to work. It is still working on the other XP machine with no issue. We created a new folder on the 8.1 machine and set it up to be shared.
It was working fine for a few days from the first day we got the new client, however there was an automatic windows update that happened a few days later and one morning we came in and all of a suddeny the scan via smb would not work when it was working the night before.
Now, no matter what we do, we get the error "Job failed due to file access denied". Below is what we have entered into the fields (which is the same way it is entered for the XP machine). The file properties for the folder is set to shared on the Win 8.1 machine, so I am wondering if there is a slightly different way to fill out the fields because it is an 8.1 client? I have seen a previous post where someone mentioned having to put the domain/workgroup name in CAPS / your username, however we tried that as well and still got the same error. The software version we are using is 20.105.01.010
First, I've created a new user on my system called "Tigress" with password "scan". Next, I've created a folder on the Desktop called "XeroxScans" and it is shared and has read/write access by "Everyone".
Friendly Name: Tigress
Name or IP address:
IP Address: 192.***.*.*
Document Path: (left blank)
Login Name: Tigress
I am sure it is just a simple setting of flag that needs to be checked but I just cannot find anything online referencing such. Can someone please help in getting this resolved. Thanks so much!
As I understand you have tried domain/XeroxScans?
Can you access the share from another computer with the same credentials?
What firmware are you using?
Please remember to select "Accept as Solution" for posts that helped you solve the issue.
port 445 not 139
I havnt tried a 3635 on windows 8 yet so i wont promise it will work. FTP is a good way to get around Windows 8 SMB v3
Yes I tried WORKGROUP/XeroxScans where "WORKGROUP" is my domain with no luck.
Software version is 20.105.01.010
I tried changing the port to 445 but still got the file access denied error.
I then attempted to tried to go the FTP route as you suggested but spent nearly an hour trying to setup an FTP folder on the Windows 8.1 client and no matter what I do cannot access the ftp folder.
I created a folder in inetpub>ftproot>SCAN (where SCAN is the name of the folder)
I shared the folder and assigned read/write permissions to everyone.
I then added an FTP site through IIS Manager in Win 8.1. Verified the site is running and can access it through the browser of the separate machine. However the file SCAN will not show up.
AM I missing something that needs to be checked etc?
Thanks in advance,
I did follow the "solutuon for the case invalid name" and it did nothing to solve the problem. After spending many hours trying to figure up what paramter had suddenly changed on the client machines and posting on this forum to no avail, I finally did in fact call my local Xerox support center.
A certfifed Xerox technician came on site and spent an hour trying to troubleshoot the problem.
He finally called Xerox support which he had direct access to and spoke with a gentleman name GALEN. Seems like Galen had been through this issue many tims before because he knew exactly what to do once he had discovered that I had set up all teh paramters correctly. (He was provided with remote access during the call).
The issue was with teh Xerox 3635. As the tech explained it to me - the logic inside had become corrupted and it was not updating setting internally even though it was reflecting on the GUI that paramters had been updated. My firmware updates and reboots were doing nothing to fix that and the only way to correct the issue was to do a completely memory clear. Had to hold down a couple buttons and then enter a code of 1394 specific to the Phaser 3635 or something to that nature.
Anyways, the point of this post is that if this seems to be an issue (which clearly from how fast Galen advised us on what to do, IT IS) then it would be nice if Xerox actually posted these steps either in an FAQ or in these forums so that others are not wasting time and money trying 50 different things while still not having any luck.