This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 38%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi
I am looking Information to see if it is possible to enable SMB2 and SMB3 on Windows 2000 Machines
I don't like the idea of having to Enable SMB1 on Windows 10 and Windows 11 Machines to communicate via Mapped Drive with Windows 2000 Machines
As you are all aware of the famous WannaCry Ransomware attack and others that have manipulated the SMB1. This is why by default Windows has this now disabled on Windows 10 and Windows 11
I would like to avoid this vulnerability by updating my Windows 2000 Machines to SMB2 and or SMB3
If you can help with any information or point me in the right direction, I would very much appreciate it
If you need anymore information, I will be glad to help.
Regards
Michael
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 66%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETG%3C/text%3E%3C/svg%3E)
In the machine tool world, we get a lot of older Windows systems that run only SMB - V1. Our solution is to put in a Nexas Networks ORiON box that allows for local SMB V1 access via Ethernet. It then also has SMB V3.0 access to the outside world via Wifi (or 2nd RJ45) via a shared directory inside the gateway box. It isolates the SMB V1 inside the machine tool control (like Mazak, HAAS, and Heidenhain) and yet allows for files to move back and forth. It is a simple Linux solution that I know is odd on this Microsoft platform, but it works for old Windows boxes well...
I am looking Information to see if it is possible to enable SMB2 and SMB3 on Windows 2000 Machines
Sorry, no it is not possible to do.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hi DSPatrick
Thank you for your quick response regarding my inquiry
I will just have to disable the SMB1 on the Windows 10 Machines when the Windows 2000 Mapped drives are not in use.
I will see if i can automate this some how when the Mapped drives are not in use and or idle.
I will do some research online and if possible will trial and test the method.
If I do come across something online that works, I will be sure to update here.
Many thanks for your support
Regards
Michael
Sounds good, you're welcome.
Just curious - Why would you not look at it the other way - Upgrade the Windows 2000 machine to something like Windows 10 or Windows 11? It is 22 years old.... If it's attached to some piece of hardware and working as a CNC CMM or something of the sort, look at upgrading the whole solution to something that is this newer and compatible. Don't try to band-aid the problem - come up with a solution.
Hi AJTek-Adam-J-Marshall
Sorry for only getting back to you now.
Yes upgrading to a modern OS would be the number one choice but unfortunately as the hardware is so old it is not compatible or able to run Windows 10 or 11, its that old it would struggle even with Windows 7 and Vista however there is the possibility of XP.
I believe you can use SMB2 on XP but will need to check this out and do some research online.
As its not possible to use SMB2 & SMB3 on Windows 2000, I will have to think of other solutions to maintain the security and integrity of the system, for example, locking down using group policy's and soon on.
I like to try and keep old hardware going for as long as possible and over extend its life-cycle, I know 22 years is a stretch indeed :D.
Well its a nice wee project and I look forward to the challenge it brings even know it may result in sleepiness nights and pulling out my hair.
Thanks again for everyone's support
Regards
Michael
If this is just for personal "use", and I say use in quotes because it shouldn't be actually used but can be a fun project as you say, then hey, it's OK.
If this is for a BUSINESS, you have the wrong outlook on how things should go. That system probably has EDO RAM and is a Pentium II. It should be recycled for usable metals and disposed of. From a business perspective, liability, downtime, and usability are paramount. If this is a short-sighted play at saving money, it is just that - short sighted. If something were to fail on it like the HDD, while if you have spares it can be replaced, but the time and effort needed far outweighs the cost of a new system. Case in point - this question, the time and energy used to even try to get XP on it (if you so try), and all of that - time = money. What's your salary? The business is paying for it.
If it's attached to an old machine, like a CMM or specialized equipment, that same CMM is old technology, has outlasted the depreciation of the asset, and has served you well in this time, and should be retired and a new one purchased.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 13%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Not when you're talking about 4+ million $ machines that still run win2000. Businesses can't just throw out a multi-million dollar machine that is still working well because of software. It's easy to say "well just retire it" .. anyway, the solution here is:
Install an FTP to the machine with SMB1, then access it from there, you can use scripts to setup automatic sync with a folder on your main server without having to touch the SMB.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 68%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
I worked in manufacturing IT for over 15 years before switching to IT in a different industry (my ears thanked me...). We also had outdated software running on outdated hardware. The reason is the manufacturers of those giant and costly units don't care to create updated packages for new OS's. You might go out to buy one of those brand new today and find it running (if you're lucky) Windows 7 straight from their factory! Why? Because they're not interested in modernizing or anything like that...now for the practical and applicable bit.
Take it out of your main network. Isolate it in a subnet and only give access to it from another updated machine. Even better, create a repository on the edge of the two networks, dump files from the main network there and pick them up from the Win2k unit. There's a security device that does all the 'work' for you, can't recall the name but it was about $2,500. We were looking into getting that for the plant I worked at when I left but the domain admins wouldn't allow any other method of network file access. Granted, these ran XP Embedded and not 2k but it's the same principal. $2,500 to get a small appliance in a rack vs $80,000-95,000 they quoted to replace the controller unit (still only take us to Win7) or nearly $600,000 to replace the whole machine (and STILL only take us to Win7)...it's not a fun game you're stuck in but I've been there. There is a solution that will help you if you ask the right people ;) Good luck!