We have run into a publishing issue. Here is the error message.
Publishing has been cancelled.
You can’t connect to the file share because it’s not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see:
We are running RoboHelp 11
Windows 10 Enterprise
8 Gig RAM
Our company is upgrading to the newest version of Windows 10, and it is not letting us publish to our folder on our server. Is there a patch for the SMB 1 and SMB 2 issue for RoboHelp 11?
I have not seen anyone report these errors and I don't recall seeing them
mentioned in any patch.
I think you need to liaise with your IT people on this.
Thanks. I will see if IT can do anything to resolve this issue. I am surprised no one else has ran into this issue.
If I'm reading the article right, MS has automatically uninstalled client-side SMBv1 from Windows 10, but the server is still set up to use SMBv1. So I *think* your IT guys either need to install client-side SMBv1 on your PC OR upgrade the server to SMBv2 or above. The article you linked should be all they need to figure out what they need to do.
Thank you for the reply. I will forward the link to IT and hopefully they can use the information to help resolve this issue. If it works, I will let this post know, so others will have a resolution. Thanks.
We talked to IT and they won't install SMB1, because it is not secure enough. They asked if RoboHelp will still work if they setup a Virtual Desktop using an older version of Windows. Like Windows 7. I understand that RoboHelp works best on your C drive, but can RH work on a Virtual Desktop and publish?
I have used a version of RoboHelp on a virtual machine, not sure which version now but it worked.
See Versions of Windows and MS Word compatible with RoboHelp. RoboHelp 11 is OK with Windows 7.
Generating an output to the virtual machine will work. Your IT will have to decide if that machine is allowed to publish to the network. If not, you will have to get the generated output to where it is required by some other means. IT will be able to figure something out.
See www.grainge.org for free RoboHelp and Authoring information.
Andre, can you check with your IT guys that the location you are publishing to is set up as SMBv2? To me, the message indicates that the server is configured for SMBv1.
So if they are concerned about SMBv1 security, wouldn't that also need to be updated?
It's also possible the message is wrong (it wouldn't be the first time MS has been unclear), but it wouldn't hurt to ask the question to be sure.
If your laptop/desktop has been upgraded to the newest version of Windows 10 and the SMB was upgraded to SMB2, here is the solution; make certain that the server you’re publishing to has been upgraded to SMB2. I tested this scenario. I had our IT create a test folder for me to publish to on the upgraded server and used the upgraded laptop/desktop with SMB2 to publish the test project.
An upgraded laptop/desktop with SMB2 cannot publish to a server that is using SMB1.
Here is an FYI.
A laptop/desktop with SMB1 can publish to a server that is using SMB2. I tested this scenario.
Here is another FYI.
If you have an upgraded laptop/desktop with SMB2 and your IT cannot upgrade your project server in time, you might have to have IT create a Virtual Machine on your upgraded laptop/desktop and use an older version of Windows.