Thanks: 
Likes: are you having problems viewing the file_share folder on your pc? ps: The machine prints from pc regularly- Tnx
Dislikes: 0
are you having problems viewing the file_share folder on your pc? ps: The machine prints from pc regularly- Tnx
please explain your problem more conciselyOriginally Posted by Claudio_Napoli
Perchance does the MFP have a DHCP address? You would not necessarily get the same IP every time.
You can also search by hostname. And if you don't find it by hostname, perhaps you have a DNS problem?
=^..^=
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 =^..^=
Or you’re running an old firmware level on your Toshiba and Windows 10 won’t connect because the copier isn’t compatible with SMB v3. But we’re all offering advice on pretty slim details. If it’s a Toshiba 2060 you’re trying to connect to a Commodore 64 then you’re in a world of hurt.
Why does every customer think they're the first one to ever say: "you've been here so much we should get you an office, ha, ha, ha"?
Maybe it was me who was not clear, the problems arose after Windows updated Win10 for about 10 days. 40% of the machines I have had this problem in the last 10 days and then they are all up to date, for example: Es2010ac-2510ac_version 1502. It cannot be SMB as the problem is in "file_share". However as soon as I get back from vacation I will let you know.
After OS update SMB is blocked as OS detects it as a threat, most likely the OS's that aren't working are Pro version of W10. Enable SMB protocols, restart the PC and then try to create the shortcut to the HDD of copier. If you ahve a 2510 series, they don't support SMB3 it's time to upgrade the unit, those were manufactured when earth was still hot bud!
Windows 10 FileShare
Control Panel
- Programs
-- Turn Windows Features On/Off
--- Expand Windows 1.0 CIFS file sharing support
----Check box Windows 1.0 CIFS client
----- OK
------ Restart computer
Network & Sharing Center
- Advanced Sharing Settings
-- Network Discovery, Private
--- Disable "Automatic setup of network connected devices"
2010/2510AC supports SMB v3.0 even older 2050/2550 with latest FW.
In 08 setting mode you can change the SMB protocols for Server and Client protocols to use SMB v1.0/2.0 or 3.0. Codes are 08-8833 -> Server Protocol and 08-8834 -> Client Protocol, changing both codes to 3 will allow SMB v3.0. I think the SMB v3.0 is set ON as per default with the latest FW's anyway.
I would personally create a scan to shared network folder and check if it connects/scans to that location on the problematic machine. This will rule out the SMB if scans ok and must be something else preventing file_share access.
Also Network Discovery must be set to ON on client PC.
Defects are simple, our mind is complicated
Thanks to all, i solved the problem, there were some windows 10 installed by a pc technician that were "slim" and some files were missing
tnx
Reply With Quote
Bookmarks