Hey everyone,
I hope you can help me out with a tricky situation. I'm dealing with CNC routers that are critical for our operations and unfortunately, they run on really outdated versions of Windows like 2000, XP, and 7. I know it's not ideal, but upgrading them is out of the question due to their high cost. Instead, I've set them up on separate VLANs and they don't have internet access, so we push programs to them via SMB shares from our production VLAN.
However, I've recently run into a problem with Windows 11 (and 10) not allowing connections to these older machines anymore. I'm getting a "password invalid" error, even though I'm using valid credentials. I've tried various fixes through PowerShell for SMB, but nothing has worked. I even considered removing passwords on the older machines to see if that resolves the issue, though that might create a security risk.
Another solution I thought about is setting up a middleman server on a separate VLAN to allow for easier file transfer, but I'm unsure how to implement that effectively. It's also critical that we keep the workflow as streamlined as possible to avoid frustrating our technicians.
Any insights or suggestions on how to tackle this challenge? Thanks for your help!
5 Answers
It sounds like you’re in a bit of a tough spot. One potential solution could be setting up a middleman server running Linux that connects to your old machines. You could use Samba to share the SMB connections back out in a way that works with Windows 11. This way, you could avoid the direct issues with SMB v1 and keep your operations running.
That’s an option I’ve considered, but it would depend on compatibility with my machines.
I've had similar experiences moving files to CNC machines. One method that worked for me was using a Linux server as an intermediary. You can set it to automatically mount the old SMB shares and reshare them with an updated samba configuration. Just ensure you have proper monitoring because users might accidentally save files to unmounted directories.
Thanks, that sounds like a solid plan. I'll try to implement that and keep an eye out for those potential pitfalls.
Just remember to lock down those SMB shares properly on your server.
If you're really stuck, another approach is to go with dedicated solutions like DNC Pro to upload/download files securely via serial interfaces. It sidesteps the SMB issues entirely and might be more reliable for your workflow, especially since USB transfers aren't always viable.
I faced a similar issue with outdated equipment and found that having a Linux box perform the SMB share mapping solved it effectively. Just ensure your automount connections are reliable to avoid issues with file visibility.
Yes, that’s key. I’ll set up some checks to make sure everything is working as it should.
Good luck! It seems like you've got a plan forming.
You might run into issues with the latest security policies in Windows 11 that enforce encryption for SMB traffic. If you’re using accounts on your older systems, make sure they’re not using the guest account without a password, as that could also cause problems. Some users have had luck running two Linux servers to handle different SMB configurations, isolating the traffic effectively.
Right, I’m definitely not relying on the guest account, so I’ll check those settings again.
You might also consider enabling NTLM if it’s not already, as that can sometimes help with authentication issues.
What about using an SFTP server on this middleman? Seems like a more secure option.