But this will need to be repeated every reboot. This involves using a remote desktop application of which there are many on the market. My current workaround is to authenticate in cmd with "net use \\ipadress\share" which allows the clients to authenticate and have a working connection in explorer. Another option to access Windows on a Mac is to run Windows remotely on another PC and use remote desktop software on your Mac to connect to it. And both the test machine and clients have a login pin code setup. On the other clients it still asks for the pin and wont work.īoth the test machine and client machines log in with Office 365 usernames. If on my test machine I enter the credentials in credential manager it works without prompt. And even if you say you want to use another account and fil in the correct details. By hitting Win + Q (which isnt nearly as ergonomic as Command + Space ), you can pull up the bar and search for things on your computer or the Windows App Store. The windows clients that are on the network connect to \\ipadress\share and are prompted for a pin code. My test windows machine connects to \\ipadress\share and is prompted for the password. Mac users just connect to \\ipadress\share and are prompted for the password. And I cant get the Windows 10 clients to work properly. Windows 10 and Mac clients access the shares. We have a Synology setup on the network with a few SMB shares. Update: Fixed (LDAP domain before the username did it)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |