ZeroTier Question
-
@WLS-ITGuy said in ZeroTier Question:
I would assume that DNS only has a small role in the issue. I have both internal DNS servers set in ZT with FQDNs but I have 3 or 4 that cannot see mapped drives. using the FQDN.
Would it make sense to map the drives using the ZT ip?
Jeff
DNS is completely your issue. There is no problem here except DNS.
-
@JaredBusch said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
I would assume that DNS only has a small role in the issue. I have both internal DNS servers set in ZT with FQDNs but I have 3 or 4 that cannot see mapped drives. using the FQDN.
Would it make sense to map the drives using the ZT ip?
Jeff
DNS is completely your issue. There is no problem here except DNS.
So then it has nothing to do with Internal domain vs external domain or it has exactly that to do with
-
@WLS-ITGuy said in ZeroTier Question:
@JaredBusch said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
I would assume that DNS only has a small role in the issue. I have both internal DNS servers set in ZT with FQDNs but I have 3 or 4 that cannot see mapped drives. using the FQDN.
Would it make sense to map the drives using the ZT ip?
Jeff
DNS is completely your issue. There is no problem here except DNS.
So then it has nothing to do with Internal domain vs external domain or it has exactly that to do with
it is related to that, but because of DNS.
What address are your users putting into Outlook (or is auto config using?) Are they using full outlook or OWA? or both?
As for network shares - again, this is definitely a DNS issue.
for the non static IP ZT clients, you need to try to confirm which DNS servers it's using as the first point of contact. it needs to be the internal ones on the ZT network. The ZT adapter should get the ZT IP of the internal DNS servers from the autoassignment from ZT.
-
@WLS-ITGuy said in ZeroTier Question:
@JaredBusch said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
I would assume that DNS only has a small role in the issue. I have both internal DNS servers set in ZT with FQDNs but I have 3 or 4 that cannot see mapped drives. using the FQDN.
Would it make sense to map the drives using the ZT ip?
Jeff
DNS is completely your issue. There is no problem here except DNS.
So then it has nothing to do with Internal domain vs external domain or it has exactly that to do with
If I'm understanding the problem correctly... The problem here is that your ZT interface looks to the DNS server that it is pointed to. The DNS server has two IP addresses for every device... one an internal LAN IP address, and the other is your ZT IP address.
Regardless of the location of your device (in office, or on the road), the DNS server randomly grabs an IP address and feeds it back to your device... If your device is off-site, and it gets the ZT IP address for the server you are connecting to, then everything is fine.
If your device is off-site and it gets your internal LAN IP address, then it's going to fail, because your computer doesn't have an IP address on your internal LAN if it is off site.
-
@Dashrender said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
@JaredBusch said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
I would assume that DNS only has a small role in the issue. I have both internal DNS servers set in ZT with FQDNs but I have 3 or 4 that cannot see mapped drives. using the FQDN.
Would it make sense to map the drives using the ZT ip?
Jeff
DNS is completely your issue. There is no problem here except DNS.
So then it has nothing to do with Internal domain vs external domain or it has exactly that to do with
it is related to that, but because of DNS.
What address are your users putting into Outlook (or is auto config using?) Are they using full outlook or OWA? or both?
As for network shares - again, this is definitely a DNS issue.
for the non static IP ZT clients, you need to try to confirm which DNS servers it's using as the first point of contact. it needs to be the internal ones on the ZT network. The ZT adapter should get the ZT IP of the internal DNS servers from the autoassignment from ZT.
ZT doesn't actually assign the DNS servers to the NIC. That has to be done manually... and technically, any device that gets a ZT IP address is static, as far as I know.
-
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
-
@WLS-ITGuy said in ZeroTier Question:
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
The short answer would be for you to generate a hosts files with the ZT IP addresses of any servers they will need access to... and for you to copy that file to those two machines...
Edit: I would include the AD servers, and any file server or application server that they need access to in the hosts file.
-
@dafyre said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
The short answer would be for you to generate a hosts files with the ZT IP addresses of any servers they will need access to... and for you to copy that file to those two machines...
Edit: I would include the AD servers, and any file server or application server that they need access to in the hosts file.
While I really dislike the lack of elegance of this solution, the dual IP nature of devices almost mandates this to ensure DNS works correctly.
-
@Dashrender said in ZeroTier Question:
@dafyre said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
The short answer would be for you to generate a hosts files with the ZT IP addresses of any servers they will need access to... and for you to copy that file to those two machines...
Edit: I would include the AD servers, and any file server or application server that they need access to in the hosts file.
While I really dislike the lack of elegance of this solution, the dual IP nature of devices almost mandates this to ensure DNS works correctly.
I thought simple trumped elegance?
-
@dafyre said in ZeroTier Question:
@Dashrender said in ZeroTier Question:
@dafyre said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
The short answer would be for you to generate a hosts files with the ZT IP addresses of any servers they will need access to... and for you to copy that file to those two machines...
Edit: I would include the AD servers, and any file server or application server that they need access to in the hosts file.
While I really dislike the lack of elegance of this solution, the dual IP nature of devices almost mandates this to ensure DNS works correctly.
I thought simple trumped elegance?
the problem is scale. This solution doesn't scale well.
-
@Dashrender said in ZeroTier Question:
@dafyre said in ZeroTier Question:
@Dashrender said in ZeroTier Question:
@dafyre said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
OK. Let me preface the next comment by Thanking you all for helping with this.
I have access to 2 machines, both off-campus. What do you need from those machines to assist in this issue?
The short answer would be for you to generate a hosts files with the ZT IP addresses of any servers they will need access to... and for you to copy that file to those two machines...
Edit: I would include the AD servers, and any file server or application server that they need access to in the hosts file.
While I really dislike the lack of elegance of this solution, the dual IP nature of devices almost mandates this to ensure DNS works correctly.
I thought simple trumped elegance?
the problem is scale. This solution doesn't scale well.
You are quite right about that. Something like PDQ Deploy would help with that though.
-
Just a curiousity question. Is it possible to install ZT on VMWare servers? I have three vsphere servers and it would be nice to be able to connect to those via vsphere client but it is just a "want" more than a need.
-
@WLS-ITGuy said in ZeroTier Question:
Just a curiousity question. Is it possible to install ZT on VMWare servers? I have three vsphere servers and it would be nice to be able to connect to those via vsphere client but it is just a "want" more than a need.
ESXi is a unique microkernel and no longer (since VMWare 4.X?) a Linux kernel.
-
@WLS-ITGuy said in ZeroTier Question:
Just a curiousity question. Is it possible to install ZT on VMWare servers? I have three vsphere servers and it would be nice to be able to connect to those via vsphere client but it is just a "want" more than a need.
No, not at this time. ZT has not been written for ESXi and would need to be special written and compiled for that platform. It is not trivial at all compared to normal platforms (mostly because it has some unique needs.)
-
Is ESXi its own completely unique thing or is it based on something else?
-
@adam.ierymenko said in ZeroTier Question:
Is ESXi its own completely unique thing or is it based on something else?
At the very core of it is a Linux kernel of some flavor, but that just used to load their own vmkernel.
-
@adam.ierymenko said in ZeroTier Question:
Is ESXi its own completely unique thing or is it based on something else?
100% unique. It shares no code nor API with any other product.
-
@JaredBusch said in ZeroTier Question:
At the very core of it is a Linux kernel of some flavor, but that just used to load their own vmkernel.
No Linux at all. Never was. Long ago there was Linux in the host VM (Dom0 equivalent) but never in the ESX product itself. That was just a VM on top of ESX that provided a GUI. But that was removed long ago and now there isn't even that.
