Posts made by WLS-ITGuy

I don't know where that 198.105.x.x ip is coming from which is why I asked about the DNS/Office 365 thing.

It is not an IP here on campus that is for sure.

@dafyre said in ZeroTier Question:

@Dashrender said in ZeroTier Question:

@WLS-ITGuy said in ZeroTier Question:

@dafyre I got the onsite vs offsite part. However, shouldn't ZeroTier handle the offsite routing? Or is that not how this works

It's not about handling routing because there would be no route.

Example
Server internal wire network IP - 192.16.8.10
________________________ZT IP - 10.0.50.10

If, when you're offsite, DNS returns the 192.16.8.10 address, the ZT network would never look at this traffic because it's not part of the ZT network. Instead that traffic would go to the normal NIC, wireless probably, and go out that way and of course fail.

And this is why I default to building a ZT Gateway. Yes, it is more work up front. Yes, it is slightly more complicated. However, it prevents you from having to deal with these types of issues.

If I put the ZT IP Addresses in the ZT NIC I won't need to do this, yes?

@Dashrender said in ZeroTier Question:

@WLS-ITGuy said in ZeroTier Question:

Also, if I ping another server from off site I get this:

http://i.imgur.com/i2l62Y5.png

WOW - how does that happen? What is returning that IP address? I wonder if the coffeehouse server is returning bad info?

This is from a single user at his home.

@dafyre I got the onsite vs offsite part. However, shouldn't ZeroTier handle the offsite routing? Or is that not how this works

@dafyre said in ZeroTier Question:

You need to go into the NIC settings for your ZT adapter and specify the ZT IP address of you internal DNS server...

What is happening is your ping / nslookup from off-site is using whatever DNS servers your ISP gives you.

Both of the IP addresses that I pointed to are the ZT IP addresses of my internal DNS servers.

DUDE! YOU ARE A GENIUS! <---Absoluetely no sarcasm

Also, if I ping another server from off site I get this:

http://i.imgur.com/i2l62Y5.png

@Dashrender said in ZeroTier Question:

Sounds like you have a DNS issue. You might not be able to use short NetBIOS type names.. you might have to move to FQDN instead.

For example, if you're at StarBucks and the DHCP server gives a suffix of starbucks.com out with the IP, and you ping server1, your system might be pinging server1.starbucks.com instead of server1.yourdomain.com

I missed this or it didn't click. So you're saying that I might have to go to wls-dc01.wls.wels.net instead of WLS-DC01, correct?

@Dashrender said in ZeroTier Question:

@WLS-ITGuy said in ZeroTier Question:

@Dashrender said in ZeroTier Question:

Are their email address - [email protected]
and your email address - [email protected]?

If so, those are two different DNS MX records. They can each go anywhere you want them to.

That is correct. Exchange works fine as it is. I was just wondering if *.wels.net was getting sucked into Office 365 somehow.

We have noticed a few issues with people who are trying to access their Microsoft Accounts getting errors saying that there is no account for them at WELS Cloud.

I would think in your case, you wouldn't want to have a *.wels.net record because of problems like this.

Sorry - I meant the * as wls.wels.net

@Dashrender said in ZeroTier Question:

Are their email address - [email protected]
and your email address - [email protected]?

If so, those are two different DNS MX records. They can each go anywhere you want them to.

That is correct. Exchange works fine as it is. I was just wondering if *.wels.net was getting sucked into Office 365 somehow.

We have noticed a few issues with people who are trying to access their Microsoft Accounts getting errors saying that there is no account for them at WELS Cloud.

@dafyre said in ZeroTier Question:

Show us the output of

ipconfig /all

?
http://i.imgur.com/4KvbqJ0.png
http://i.imgur.com/Q8orjss.png

@scottalanmiller said in ZeroTier Question:

@WLS-ITGuy said in ZeroTier Question:

Let me ask this question...

We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.

Could this be part of the issue?

I don't see how but at this point I am looking at everything.

O365 doesn't have any components that would be involved here.

Let me explain a bit.

www.wels.net is the main org

www.wls.wels.net is us.

The main org went Azure and Office 365 but due to costs we weren't going to move to office 365.

Could it have something to do with their DNS of www.wels.net being pointed to Office 365?

Let me ask this question...

We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.

Could this be part of the issue?

I don't see how but at this point I am looking at everything.

Sure - any specific commands?

If not, I get:

Default Server: Unkown
Address: 2602:306:8b7e:f60::1

@Dashrender All devices on LAN or off LAN have ZT installed.

@scottalanmiller I don't see where though...Or how for that matter.

@scottalanmiller ZT Range is 192.168.191.x/24

@scottalanmiller I just did as a test to see if it would resolve via IP and it does.

Just to add some info I can ping the ZT NIC IP of the DC on the remote machine. I can also connect to mapped drives using \SERVER-IP\SHARE

@scottalanmiller If I ping the server name, whether it is FQDN or just the name, it shows the 198.105.254.130 address from a WIndows 10 laptop.

I am on campus now so I cannot test on my laptop. However, when I did test last night, I got a similar address like the one above. But I could see the Server name in my Finder on my mac.

@scottalanmiller The drives are mapped via logon script but have a red x when off campus. When you click on them it says it could not reconnect.