Slimslob is correct agian. LRC0451 allows for server 2012 R2 and win 8/8.1 smb scanning. Works like a champ. A "Failed to write" message in the system log is a dead give away.
Slimslob is correct agian. LRC0451 allows for server 2012 R2 and win 8/8.1 smb scanning. Works like a champ. A "Failed to write" message in the system log is a dead give away.
Thanks Slimslob. We had a tech just install it this morning... but still having problems. I've used \\server\sharename\folder and \\10.x.x.x\sharename\folder and both are still failing. Any tips on Windows Error Logs or a log on the machine itself that will help me debug? We have this working just fine on the old Server 2003 product. And, I'm 99% sure I have the share setup correctly. We are using the same Admin name and password as well.
Thanks!
User Tools - System Settings - Interface Settings - Print List button. Last page of the printout has communications errors. For discovery, make sure that you are set on the same Domain and/or Work Group. Computer name discovery uses Net-bios. First DNS must be the domain DNS. User Tools - System Settings - Interface Settings page 2 has a ping command. If you cannot ping the server then there is a network or firewall problem.
I'm on site at the client's office today and have done some testing and it still is not working.
- I can ping the machine's IP address no problem (10.10.10.5).
- I have that machine as primary DNS server (10.10.10.5).
- I tried having username be "MyAdminName" and "DOMAIN\MyAdminName".
- I've made sure the Password is correct.
- I went to a computer that was NOT on the domain and put in the same path \\ServerName\Shares\EmployeeName\Scans and prompted me for a username and password. I supplied it and was able to read / write to that directory.
- The last page of the Print List shows the following: #[smb client(256)] 15/01/14 09:27:12 SMBC: failed to write file (08212:0x2020001) ERR:
At this point I'm at a loss. Any other ideas? I wish I had more detailed logging somewhere...
Thanks for any advice you can give me...
Hugh
Oh, here is what I see on the Firmware page:
Module Name Version Part Number animation 1.00 B2215610A Network Support 5.20 B2215605L Security Module 1.03 -------- Fax 03.00.00 B2215602H System/Copy 1.70 B2215601S SD Scanner ap_1.25 B2215604H Web Support 1.09 B2215606G NetworkDocBox 3.03 B2215608K Web Uapl 1.12 B2215609D Fax(option) 01.00.00 B2215903B SD#1 PCL Font 1.00 B7675383 SD Printer 1.70 B8375601K FCU 02.00.00 B7715571 Engine V1.65:01 B2235117S OpePanel 1.06 B2231491A
Are you sure that you got the Network Support Special/Custom Firmware B2215605L_LRC0451 Dated 12/5/2012
Not to be confused with Network Support Normal Firmware B2215605L Dated 7/16/2010
Both show as ver. 5.20
Send him back out with the LRC0451 ONLY on the card. It is very easy to install both Net Support versions. One overwrites the other and then the LRC0451 does not get updated. Best way is to download the new one and only put it on the card. I have updated a tone of older machines and it works like a champ.
The LRC04051 will show as 5.20e.
Still needs firmware updated
This is a good reminder to keep all of the machines in the field updated. Server 2003 is coming to end of life in July 2015, company's are moving to Server 2012, generating calls like this that could be taken care of proactively. It's just a thought, I'm not a fanatic about it but I try to keep it in mind.
Bookmarks