Meshcentral Agent creation?
-
so you used a local FQDN, not a real one on the interwebs? Otherwise why would it matter?
-
I'll have another go, I'm still learning about Meshcentral so I may be missing ways of doing things.
I'm working with devices in a private network, most devices run in a windows domain called domain.local, however some devices run in remote offices with different windows domains, EG: site1.local.
My Meshcentral server is located in domain.local and called mesh.domain.local.
I created the initial agent with this command as shown on the setup video, node meshcentral --cert mesh.domain.local which gave me the agent with mesh.domain.local embedded as the host for the agent to connect to.
I created a forward lookup zone in the site1.local dns that points at mesh.domain.local, but the devices in the site1.local domain don't always connect to it.
So, I'm wanting to create a new agent that has the IP address of mesh.domain.local embedded within it and not the fqdn.
So my real question is, how do I create new mesh agents??
Another thing, the mesh server runs a startup script to start mesh central upon a reboot, so I don't have a server sitting there with an open command prompt as you see in the videos. That's why I was wondering if you can create new agents in the console OR terminal of the mesh server??
Thanks for any help.
-
OK, yeah, you have a private network. can the DNS servers in site1.local get info from domain.local? If they can, then the current FQDN should be fine.
I have no idea if you can do what you want, perhaps Scott does.
It's likely not really meant to work as you're using it. Normally you'd use it external to your network.
-
@siringo said in Meshcentral Agent creation?:
I'm working with devices in a private network, most devices run in a windows domain called domain.local, however some devices run in remote offices with different windows domains, EG: site1.local.
My Meshcentral server is located in domain.local and called mesh.domain.local.The first part is part of Active Directory. The second is the URL of the MC server. There's no relationship.
-
yep all dns ops work/resolve, everything is pingable.
I have a Hyper-V server at one site, the physical server can be seen in MC, but the VM it hosts can't be seen.
I've tried all the sensible things I can think of, now I'm moving onto the nonsensical.
-
@siringo said in Meshcentral Agent creation?:
yep all dns ops work/resolve, everything is pingable.
Then likely there is a firewall or other problem, not a DNS one. So using the IP address will likely not work.
-
@scottalanmiller said in Meshcentral Agent creation?:
@siringo said in Meshcentral Agent creation?:
I'm working with devices in a private network, most devices run in a windows domain called domain.local, however some devices run in remote offices with different windows domains, EG: site1.local.
My Meshcentral server is located in domain.local and called mesh.domain.local.The first part is part of Active Directory. The second is the URL of the MC server. There's no relationship.
Yep, I was trying to layout the setup for reader.
-
@siringo said in Meshcentral Agent creation?:
have a Hyper-V server at one site, the physical server can be seen in MC, but the VM it hosts can't be seen.
Has to be a networking layer thing.
-
You can test on any individual machine by using the hosts file to see if it fixes things.
-
Yep.
It'll be some weird networking issue I guess.
-
OK, all fixed. All I'm going to say is that I need to slow my typing down & take more care.
-
@siringo said in Meshcentral Agent creation?:
OK, all fixed. All I'm going to say is that I need to slow my typing down & take more care.
LOL - that leaves a lot to the imagination...
