Thanks: 
Likes: 
Dislikes: New Network firmware is scheduled to be released in january 2013 for the latest models. For the models with GW-Controller 05A and earlier, there will be no firmware update available.Originally Posted by coltrain
New Network firmware is scheduled to be released in january 2013 for the latest models. For the models with GW-Controller 05A and earlier, there will be no firmware update available.
I'm having the same issue with a TOSHIBA e-STUDIO455 and a TOSHIBA e-STUDIO556. Does anyone know the actual reason why this isn't working?
Thanks,
Kasee
Windows 8 uses SMB version 3, most devices are built on SMB version 1 and 2. Version 3 is supposed to be backwards compatible, however most devices running versions 1 and 2 don't have that functionality enabled, or do not understand the newer protocol entirely.
this is actually a problem with the new APPLE O/S as well. it seems the new O/Ss have changed some security issues in SMB which makes legacy products incompatible. Have to use FTP for now until firmware updates come out for your machines if they do.
That's what I did as well. FTP works.
You can reinstate SMB on OSX 10.7.x (and possibly 10.8.x, but I have yet to test it) by downloading SMBUp:
Download SMBUp for Mac - Reinstate and manage Samba on OS X 10.7 Lion. MacUpdate.com
Original site (currently down) http://eduo.info/smbup/
For Windows 8 we will need to look into disabling SMB2.2, a few forum threads around suggest a registry fix: https://community.emc.com/message/597592#597592
but I have yet to test it. (Currently downloading ISO).
Last edited by ruben; 11-07-2012 at 09:39 PM.
That's why I always force users to use FTP scanning.
Anyone know if there is a fix for this yet? New firmware out there? Or a work around?
I did a SMB folder installation today, Kyocera FS-3640 to Win8. Other than incorrect login information provided, it was a lot easier the Win7. The driver disk Autorun failed every time, but if I inserted the disk, ignored the new window, the followed the Add A Printer wizard it worked fine. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
Is there any update on this? I have just encountered the problem with Server 2012 E.
I've not yet had a chance to experiment with this, but I will revert to SMB v1 on the server and retest. Probably won't get to it for a few days...
Steve
Reply With Quote
Bookmarks