You'll probably notice it won't talk to XP anymore, either. You're describing the WannaCry issue, where Win7 was likely using samba v1 before and after updates are using samba 2. Your reply is for samba network access AFTER a successful neorouter login.
OP's problem is Neorouter sign in related. I do NOT suspect problems with NeoRouter (using the free Linux version), not at all. 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 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.
Win 10 had problems earlier, but not since version 1709.
By moving the 'Slider' all the way to large, the display settings will automatically set to 'Full. 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. -On 'Display configuation' settings, you can change the 'Remote Desktop Connection' display by moving the slider from 'Small to Large'. 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). CalcMe.portable edition for Windows 10 Version 1903 and above. 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. NeoRouter Mesh Portable 8.8.0 With Registration Code Download For PC. 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). 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. The use port 80 traffic outbound used mostly by browsers HTTP traffic and port 443 traffic HTTPS and thus will work with any ethernet connection that has a path to the internet without the ned for IT to setup a firewall route and without modifying firewall rules.Still a problem? I have had much trouble connecting from any kind of Linux to a file server on a Win 7 machine. The solutions in my list all work off a brokered connection over standard ports and protocols much like the hardware solutions you mentioned. One of the solutions in my list provides access to the entire network or can be limited by device as you wish. One of the solutions I mentioned will run on multiple PC's and servers and any of them can broker a connection and provide a layer 2 or 3 connection to the LAN and provide redundancy by default where the hardware device does not without adding another expensive hardware device.Ī lot of what has been discussed here like Logmein, Teamviwer, Splashtop, etc are desktop remote access solutions and only provide a remote connection to a desktop, laptop,server, tablet or phone. If the E W O N or tosibox dies then you lose access to your whole network. Could you use them to access a multi machine network sure but the connection could get bogged down fast depending on the amount of remote work. So would you recommend using any of the above mentioned routers versus a solution such as E W O N or Tosibox?Īs far as E W O N or tosibox they are single point solutions and made for a single machine or cell.
0 kommentar(er)
