Connecting Machines with Pertino
-
@Sparkum said:
Oh wow I upgraded to the 30 day trail, they really do make it easy eh
Yeah, the pro tools make it really, really easy.
-
So I guess my real question is after my trail ends do I have to change the settings to allow my computers to continue to talk with the AD or when the trial ends does everything I've currently set up continue to function?
I wish you could actually buy the additional apps (one time cost) for use with the 3 computer trail, I would buy the ADConnect just for how easy it just made this.
-
@Sparkum said:
So I guess my real question is after my trail ends do I have to change the settings to allow my computers to continue to talk with the AD or when the trial ends does everything I've currently set up continue to function?
Yes you will have to make the manual changes if you do not have AD Connect.
-
Well atleast I have 30 days to get it going.
-
@Sparkum said:
Well atleast I have 30 days to get it going.
@scottalanmiller's original guide works as the process has not changed. I use A mix of the 3 free, a free 25 system beta grant, and clients with various amounts of paid subscriptions.
I love Pertino in general.
I think that making the apps available for a one time add to an account would be a nice feature.
-
A VM to join a whole site to the VPN would be nice. That's one of the main reasons I haven't used it. Having to put it on every computer in a site is not ideal.
-
@thecreativeone91 said:
A VM to join a whole site to the VPN would be nice. That's one of the main reasons I haven't used it. Having to put it on every computer in a site is not ideal.
And cost prohibitive.
-
Ya for sure, I would definately shell out (ballpark) or 20-40 to buy the ADConnect (I'm sure I can figure out how to get it going without but a complete end user that wants to connect say his house to his buddies house)
@scottalanmiller Took a quick look at the guide and I dont have a pertino network, so thats slightly confusing
-
@Sparkum said:
Ya for sure, I would definately shell out (ballpark) or 20-40 to buy the ADConnect (I'm sure I can figure out how to get it going without but a complete end user that wants to connect say his house to his buddies house)
You don't need AD connect or @scottalanmiller's guide for that. That is how Pertino works in the first place. everything is just up.
You should be able to ping and access by IP as well as by hostname of the device.
AD connect is designed to connect Active Directory as is Scott's guide.
-
-
@Sparkum said:
Ya for sure, I would definately shell out (ballpark) or 20-40 to buy the ADConnect (I'm sure I can figure out how to get it going without but a complete end user that wants to connect say his house to his buddies house)
@scottalanmiller Took a quick look at the guide and I dont have a pertino network, so thats slightly confusing
You don't have a Pertino network? Not sure what you mean. How are you using Pertino, making a network is the only thing that it does.
-
-
Is that important? You have the adapter. You have properties. Why are you looking at the list?
-
A Pertino network looks just like a local LAN network if I'm not mistaken. I wouldn't expect to see anything unusual in that list.
-
Oh sorry yep I was being dumb, I thought it went into Pertino settings not IPV6 settings, my bad.
-
To confirm is my DNS suffix my domain or pertino.net?
Thanks
-
@Sparkum said:
To confirm is my DNS suffix my domain or pertino.net?
Thanks
Your domain I'm sure. I don't see why pertino would be involved in DNS
-
@thecreativeone91
Going through pertino changes my hostname (like on pertino's website) to (random example)
g8d64jfs.pertino.net
So just wanted to confirm cause my connection isnt going through -
@Sparkum said:
@thecreativeone91
Going through pertino changes my hostname (like on pertino's website) to (random example)
g8d64jfs.pertino.net
So just wanted to confirm cause my connection isnt going throughAren't you using AD DNS?
-
Yep there in DNS as well.
