bluejay41 wrote:
Still a problem? I have had much trouble connecting from any kind of Linux to a file server on a Win 7 machine. Is your file server a Win 7 machine? If so, the workaround is to get on the Win 7 machine and check for updates, and install every one of them, even the optional updates. Then reboot the Win 7 machine. Immediately power it off, and then reboot again (sometimes power off and reboot works better than a mere restart, and sometimes two successive reboots are needed).
These problems started in summer of 2017 after years of using Ubuntu and Win 7 machines with NeoRouter with no problems at all, and problems continue to this day, 3/12/18. Something about the presence of pending updates on the Win 7 machine screws up the remote access connection's credentials check (for a shared folder, I don't use remote desktop).
The permanent solution is to make the file server either a Win 10 or a Linux machine -- both work great with remote access via NeoRouter, at least while using Ubuntu 16.04. Win 10 had problems earlier, but not since version 1709. I have tried Ubuntu MATE and also Linux Mint, dual booted on the same hardware as Ubuntu 16.04, but both MATE and Mint have problems that Ubuntu 16.04 doesn't have. Same Samba and Samba configuration file in all three cases, but the login credentials windows are different in MATE and Mint (and different from each other), so I suspect problems there, in addition to the Win 7 pending updates problem.
I do NOT suspect problems with NeoRouter (using the free Linux version), not at all.
Hope this helps.
You misunderstand the issue, completely. OP's problem is Neorouter sign in related. Your reply is for samba network access AFTER a successful neorouter login. You're describing the WannaCry issue, where Win7 was likely using samba v1 before and after updates are using samba 2. You'll probably notice it won't talk to XP anymore, either.