Matthew.adams 0 Posted August 2, 2017 Share Posted August 2, 2017 Trying the new 2.0 beta. Installed on two Windows machines. Each one prompted me to sign in and now they are each displaying their own name on the Synergy screen. I can’t connect to either one from the other. One has the PC name in a green box the other has the name in a grey box. Is there some configuration I’m missing? Link to post Share on other sites
Matthew.adams 0 Posted August 2, 2017 Author Share Posted August 2, 2017 Trying the new 2.0 beta. Installed on two Windows machines. Each one prompted me to sign in and now they are each displaying their own name on the Synergy screen. I can’t connect to either one from the other. One has the PC name in a green box the other has the name in a grey box. Is there some configuration I’m missing? Aten should be the server and WL-CNOMALT2 should be the client Both are connected to the same wifi working on the same subnet. Link to post Share on other sites
Matthew.adams 0 Posted August 2, 2017 Author Share Posted August 2, 2017 Upload path: https://synergy-logs.symless.com/2017-08-02/1010-2017-08-02T11-18-11.log Link to post Share on other sites
Matthew.adams 0 Posted August 2, 2017 Author Share Posted August 2, 2017 Aten is running Windows 10 Enterprise and WL-CNOMALT2 is Windows 7 Prof Link to post Share on other sites
Paul Suarez 107 Posted August 3, 2017 Share Posted August 3, 2017 Please reboot both machines please and provide us the logs that'll include the first lines of logs it generates for both machines. Thanks in advance @Matthew.adams. Link to post Share on other sites
Matthew.adams 0 Posted August 3, 2017 Author Share Posted August 3, 2017 I think this is resolved now. I disabled the virtual box network adapter and both machines connected immediately. Link to post Share on other sites
Paul Suarez 107 Posted August 3, 2017 Share Posted August 3, 2017 Gothca! Thanks for the update on this @Matthew.adams. Link to post Share on other sites
johnny2678 3 Posted August 4, 2017 Share Posted August 4, 2017 7 hours ago, Matthew.adams said: I think this is resolved now. I disabled the virtual box network adapter and both machines connected immediately. Same issue... disabling the virtual box adapter isn't an option for me as I am running virtual box 24x7. Advice? Love the simplicity of 2.0, but this is the kind of issue that I can usually resolve myself after poking around in the settings... except... 2.0 doesn't have any... Link to post Share on other sites
Paul Suarez 107 Posted August 5, 2017 Share Posted August 5, 2017 Hi @johnny2678. This feature is on the works right now. Please sit tight as we improve and add more features in v2. Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now