@mattbagan said in Comparing MeshCentral 2 to ScreenConnect:
Am I supposed to create an account on their site or just follow the guide?
We are talking about the self-hosted version, documentation and info here https://www.meshcommander.com/meshcentral2. The other one in https://meshcentral.com/ is the old version which was only hosted by them.
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@Romo Perfect bug report for GitHub
Just updated the terminal support for Windows in the MeshAgent and I just started seeing this yesterday. Looking into it.
Reported on github 
In some of the windows 7 machines we have deployed the meshagent, we have just been informed people are getting the Interactive Services Detection modal:
User sent photo
Any idea why this just started appearing?
@Ylian Welcome to the community, so glad you are here
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
Hi. Ylian here. I am the guy behind MeshCentral.
Welcome, that's so awesome that you found us!
I was looking for that as well, lol
@Dashrender said in Anyone Tried MeshCentral with LetsEncrypt?:
if you visit meshcentral.com and try to make a new account you see this.
That's the old version of MeshCentral which was hosted by them.
Here is the link for the info on the new self hosted version: https://www.meshcommander.com/meshcentral2
@valentina said in What Are You Doing Right Now:
Good morning! Is Rocket not working?
@valentina We are back up again
@jmoore said in Konica Minolta BizHub C3850 No Printing on Windows 10:
@Romo Why is it setup like that?
Don't really know, from my interaction with the owner I guess that is how she wanted it setup =). She was the one that could explain what was happening, so I could fix the issue quite fast after I spoke with her.
Authentication was enabled but not properly set:
I had to got to :
Printer preferences -> Basic tab -> User Authentication and Account Track -> SET THE PROPER PASSWORD -> Verify
After that the computer was properly authorized to print =).
Just got it working, it was indeed a DNS issue. When launching the docker container I added the --add-host name:ip option to add an entry to the hosts file that pointed to the internal ip of our nextcloud server and that made it properly work.
Its now properly working
Getting the following logs from the docker container:
wsd-00026-00053 2018-11-22 17:36:11.045672 [ docbroker_005 ] ERR Cannot get file info from WOPI storage uri [https://nc.domain.com/apps/richdocuments/wopi/files/59572_ocxqc3gr3v6o?access_token=2mcS0atAQxZXjW25Be3rTmQexxAHHddO&access_token_ttl=0&permission=edit]. Error: Connection refused| wsd/Storage.cpp:446
wsd-00026-00053 2018-11-22 17:36:11.048893 [ docbroker_005 ] ERR Failed to add session to [/apps/richdocuments/wopi/files/59572_ocxqc3gr3v6o] with URI [https://nc.domain.com/apps/richdocuments/wopi/files/59572_ocxqc3gr3v6o?access_token=2mcS0atAQxZXjW25Be3rTmQexxAHHddO&access_token_ttl=0&permission=edit]: Connection refused| wsd/DocumentBroker.cpp:1041
wsd-00026-00053 2018-11-22 17:36:11.049298 [ docbroker_005 ] ERR Error while loading : Connection refused| wsd/LOOLWSD.cpp:2534
Searching around, I found it could be related to the docker container not resolving the ip address properly, in this case it needing to be the internal ip.
Happy Birthday @DustinB3403, hope you have a great day!!
@biggen Can you post your full smb.conf file
I also recommend packet tracer as @black3dynamite mentions. I use it pretty often to troubleshoot network trouble. Recreate the network in it (obviously not 100% since we don't even work with Cisco gear) vlans, acls, l3 routing etc and watch how the packets should flow.
@scottalanmiller said in What Are You Doing Right Now:
Quiet day today. Customers are quiet, too.
Linux Academy time for me =). Just finished with the excel rendering ticket.
@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:
@pmoncho said in Handling DNS in a Single Active Directory Domain Controller Environment:
@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:
@stuartjordan said in Handling DNS in a Single Active Directory Domain Controller Environment:
I believe the forest level with Samba can only be 2008R2 though.
Sure, but what does that really affect? Forest level limitation is nothing like an old code limitation. Nothing wrong with using a 2008 R2 Forest level.
If I am reading this correctly, I believe Samba 4.4 and higher can go to 2012 R2.
https://wiki.samba.org/index.php/Raising_the_Functional_Levels
Rumor is, but I'm not sure that 4.4 is widely available yet?
Even newer versions =).
Centos 7.5 is using 4.7.1
Fedora 28 is using 4.8.5
@manxam Apparently, she doesn't need all of them so we are going to start removing them. For the moment, I disabled the shared mailboxes to be available offline and she says everything has been working better.