New
#21
No, you totally misunderstand me. I'm not blaming anyone. I understand the reasons for MS withdrawing SMB1 and fully support that decision. I have every intention of upgrading my app to a later SMB version at the first possible opportunity. Unfortunately, that probably won't be for a couple of weeks.
My question was a very simple one. A week ago, I was able to communicate with both my Win10 boxes. Today, one of those boxes has spontaneously decided not to accept a connection from my app (even though it claims still to support SMB1). I simply wanted to know what might have changed to cause that to happen and whether it would be possible, temporarily, to undo it so I could complete testing. I don't have time for an immediate upgrade to SMB2 before I have the basic functionality working.
The bridge club would like to start using the software asap. I have no problem with them starting off with an SMB1 version as the system will be used on a closed network with no connection to the outside world. I already know the club's computer supports SMB1 and that isn't going to change because said computer lives in a cupboard and is never allowed to talk to anyone. Even if the worst happened and it did get infected with something, we'd simply format the hard drive and reinstall everything.
I'm a bit fed up with being painted as some sort of dinosaur, resisting progress and determined to use an outdated and dangerous protocol just for the hell of it. I'm not. I'm simply being pragmatic. I understand the risks and have decided they are minimal in the environment we are using. I was looking for a quick and dirty temporary solution and, as it happens, I now have one. I'm only continuing this thread in order to defend myself against unjustified accusations.