ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Pertino - Is Anyone Successfully Using Any Version Above 510 with DNS/AD Connect?

    Scheduled Pinned Locked Moved IT Discussion
    166 Posts 10 Posters 26.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DashrenderD
      Dashrender @scottalanmiller
      last edited by

      @scottalanmiller said:

      @Dashrender said:

      I ran into problems with ZT and DNS as well - but I didn't deploy ZT everywhere - nor did I want to.

      That's really a problem with design, not with ZT or DNS then, right? 😉

      I never said it was with ZT, just with my experience with ZT.

      I'm guessing life would have been fine if I would have deployed ZT it all 110 of my endpoints so that my one very temporarily mobile (home) user could connect. That situation gave me an excuse to give ZT a try, and for my situation it didn't work well at all because of DNS issues - my file server had two IPs in DNS, and my non ZT clients were constantly getting the ZT address from DNS and I couldn't stop the ZT NIC from registering with DNS.

      Again, wholistically, ZT is probably fine.

      scottalanmillerS 2 Replies Last reply Reply Quote 1
      • scottalanmillerS
        scottalanmiller @Dashrender
        last edited by

        @Dashrender said:

        I never said it was with ZT, just with my experience with ZT.

        It's very misleading to say that your experience with ZT is that DNS does not work when it hasn't been fully deployed yet.

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @Dashrender
          last edited by

          @Dashrender said:

          I'm guessing life would have been fine if I would have deployed ZT it all 110 of my endpoints so that my one very temporarily mobile (home) user could connect. That situation gave me an excuse to give ZT a try, and for my situation it didn't work well at all because of DNS issues - my file server had two IPs in DNS, and my non ZT clients were constantly getting the ZT address from DNS and I couldn't stop the ZT NIC from registering with DNS.

          Again, wholistically, ZT is probably fine.

          What was the driver to not fully finish deploying ZT to see if it worked?

          DashrenderD 1 Reply Last reply Reply Quote 0
          • wrx7mW
            wrx7m @scottalanmiller
            last edited by

            @scottalanmiller I totally get your point. I understand that the way to remedy that is for you to install ZT on every system. My reason for not pursuing ZT for the company is what is required for ZT to work- installing ZT on every system.

            scottalanmillerS DashrenderD 2 Replies Last reply Reply Quote 0
            • DashrenderD
              Dashrender @wrx7m
              last edited by

              @wrx7m said:

              @Dashrender To push out updates for AV clients and for ShoreTel, the use of "softphones" for external sales personnel.

              What about moving to a LANless design?

              For example, my AV is now cloud based (has been for 5+ years). The agent checks in with the cloud provider for updates and reporting of incidents - local LAN like thing not required.

              As for your softphones - again, LANless design - secure, then publish your PBX directly online so softphones can work from anywhere. If your PBX can't be secured, I guess that would be a no go.

              wrx7mW 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @scottalanmiller
                last edited by Dashrender

                @scottalanmiller said:

                @Dashrender said:

                I'm guessing life would have been fine if I would have deployed ZT it all 110 of my endpoints so that my one very temporarily mobile (home) user could connect. That situation gave me an excuse to give ZT a try, and for my situation it didn't work well at all because of DNS issues - my file server had two IPs in DNS, and my non ZT clients were constantly getting the ZT address from DNS and I couldn't stop the ZT NIC from registering with DNS.

                Again, wholistically, ZT is probably fine.

                What was the driver to not fully finish deploying ZT to see if it worked?

                Because I only had one mobile user who needed a remote access solution for 30 days. After that I didn't need the solution any longer. and sure, while ZT shouldn't cause any problems with everyone on the same LAN, It seems like unnecessary overhead.

                If mobile access was part of my users daily life - then I would change my tune in a second..

                scottalanmillerS dafyreD 2 Replies Last reply Reply Quote 1
                • wrx7mW
                  wrx7m @Dashrender
                  last edited by

                  @Dashrender said:

                  @wrx7m said:

                  @Dashrender To push out updates for AV clients and for ShoreTel, the use of "softphones" for external sales personnel.

                  What about moving to a LANless design?

                  For example, my AV is now cloud based (has been for 5+ years). The agent checks in with the cloud provider for updates and reporting of incidents - local LAN like thing not required.

                  As for your softphones - again, LANless design - secure, then publish your PBX directly online so softphones can work from anywhere. If your PBX can't be secured, I guess that would be a no go.

                  This is something I had been considering and I look every time my AV renewal comes around. I was considering Vipre right before GFI bought them out. Looks like a dodged a bullet. Currently using TrendMicro but maybe considering Cylance.

                  DashrenderD JaredBuschJ 2 Replies Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @wrx7m
                    last edited by

                    @wrx7m said:

                    @Dashrender said:

                    @wrx7m said:

                    @Dashrender To push out updates for AV clients and for ShoreTel, the use of "softphones" for external sales personnel.

                    What about moving to a LANless design?

                    For example, my AV is now cloud based (has been for 5+ years). The agent checks in with the cloud provider for updates and reporting of incidents - local LAN like thing not required.

                    As for your softphones - again, LANless design - secure, then publish your PBX directly online so softphones can work from anywhere. If your PBX can't be secured, I guess that would be a no go.

                    This is something I had been considering and I look every time my AV renewal comes around. I was considering Vipre right before GFI bought them out. Looks like a dodged a bullet. Currently using TrendMicro but maybe considering Cylance.

                    So you're in that 250 endpoint or greater range, eh?

                    1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @wrx7m
                      last edited by

                      @wrx7m said:

                      @scottalanmiller I totally get your point. I understand that the way to remedy that is for you to install ZT on every system. My reason for not pursuing ZT for the company is what is required for ZT to work- installing ZT on every system.

                      Out of curiosity, what's the downside to that? Why not deploy everywhere? Why struggle with other solutions just to avoid full deployment?

                      DashrenderD wrx7mW 2 Replies Last reply Reply Quote 0
                      • Deleted74295D
                        Deleted74295 Banned
                        last edited by

                        Give Webroot a try. Really great team and product.

                        1 Reply Last reply Reply Quote 1
                        • scottalanmillerS
                          scottalanmiller @Dashrender
                          last edited by

                          @Dashrender said:

                          @scottalanmiller said:

                          @Dashrender said:

                          I'm guessing life would have been fine if I would have deployed ZT it all 110 of my endpoints so that my one very temporarily mobile (home) user could connect. That situation gave me an excuse to give ZT a try, and for my situation it didn't work well at all because of DNS issues - my file server had two IPs in DNS, and my non ZT clients were constantly getting the ZT address from DNS and I couldn't stop the ZT NIC from registering with DNS.

                          Again, wholistically, ZT is probably fine.

                          What was the driver to not fully finish deploying ZT to see if it worked?

                          Because I only had one mobile user who needed a remote access solution for 30 days. After that I didn't need the solution any longer. and sure, while ZT shouldn't cause any problems with everyone on the same LAN, It seems like unnecessary overhead.

                          If mobile access was part of my users daily life - then I would change my tune in a second..

                          Okay for 30 days, that makes sense.

                          1 Reply Last reply Reply Quote 0
                          • DashrenderD
                            Dashrender @wrx7m
                            last edited by

                            @wrx7m said:

                            @scottalanmiller I totally get your point. I understand that the way to remedy that is for you to install ZT on every system. My reason for not pursuing ZT for the company is what is required for ZT to work- installing ZT on every system.

                            Why don't you want to deploy ZT to every system? It's my understanding that that was how Pertino is supposed to work as well - but their hacks allow it to get around that, when they are working.

                            1 Reply Last reply Reply Quote 1
                            • JaredBuschJ
                              JaredBusch @wrx7m
                              last edited by

                              @wrx7m said:

                              @Dashrender said:

                              @wrx7m said:

                              @Dashrender To push out updates for AV clients and for ShoreTel, the use of "softphones" for external sales personnel.

                              What about moving to a LANless design?

                              For example, my AV is now cloud based (has been for 5+ years). The agent checks in with the cloud provider for updates and reporting of incidents - local LAN like thing not required.

                              As for your softphones - again, LANless design - secure, then publish your PBX directly online so softphones can work from anywhere. If your PBX can't be secured, I guess that would be a no go.

                              This is something I had been considering and I look every time my AV renewal comes around. I was considering Vipre right before GFI bought them out. Looks like a dodged a bullet. Currently using TrendMicro but maybe considering Cylance.

                              Vipre has been solid for years. Used them from Sunbelt to GFI to ThreatTrack.

                              Only left them to get away from the local server. Moved to Webroot across the board.

                              Cylance is silly stupid on their device count requirements.

                              1 Reply Last reply Reply Quote 1
                              • DashrenderD
                                Dashrender @scottalanmiller
                                last edited by

                                @scottalanmiller said:

                                @wrx7m said:

                                @scottalanmiller I totally get your point. I understand that the way to remedy that is for you to install ZT on every system. My reason for not pursuing ZT for the company is what is required for ZT to work- installing ZT on every system.

                                Out of curiosity, what's the downside to that? Why not deploy everywhere? Why struggle with other solutions just to avoid full deployment?

                                Agreed - you presumably deploy Adobe Reader (at least in the day) and probably Adobe Flash as well - so if this gives you something helpful (access from anywhere) why not?

                                scottalanmillerS 1 Reply Last reply Reply Quote 1
                                • wrx7mW
                                  wrx7m @scottalanmiller
                                  last edited by

                                  @scottalanmiller I wouldn't necessarily struggle with deploying traditional solutions. I didn't think I would struggle with Pertino LOL. It is SOOOO easy everyone said. My main concern is that I can't deploy it on certain devices like printers or items I want to access that also don't have the ability to run the client.

                                  DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
                                  • dafyreD
                                    dafyre @Dashrender
                                    last edited by

                                    @Dashrender said:

                                    @scottalanmiller said:

                                    @Dashrender said:

                                    I'm guessing life would have been fine if I would have deployed ZT it all 110 of my endpoints so that my one very temporarily mobile (home) user could connect. That situation gave me an excuse to give ZT a try, and for my situation it didn't work well at all because of DNS issues - my file server had two IPs in DNS, and my non ZT clients were constantly getting the ZT address from DNS and I couldn't stop the ZT NIC from registering with DNS.

                                    Again, wholistically, ZT is probably fine.

                                    What was the driver to not fully finish deploying ZT to see if it worked?

                                    Because I only had one mobile user who needed a remote access solution for 30 days. After that I didn't need the solution any longer. and sure, while ZT shouldn't cause any problems with everyone on the same LAN, It seems like unnecessary overhead.

                                    If mobile access was part of my users daily life - then I would change my tune in a second..

                                    For single users or temporary scenarios, to me, VPNs make more sense due to ease of setup & tear down.

                                    1 Reply Last reply Reply Quote 0
                                    • Deleted74295D
                                      Deleted74295 Banned
                                      last edited by

                                      This post is deleted!
                                      1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @Dashrender
                                        last edited by

                                        @Dashrender said:

                                        @scottalanmiller said:

                                        @wrx7m said:

                                        @scottalanmiller I totally get your point. I understand that the way to remedy that is for you to install ZT on every system. My reason for not pursuing ZT for the company is what is required for ZT to work- installing ZT on every system.

                                        Out of curiosity, what's the downside to that? Why not deploy everywhere? Why struggle with other solutions just to avoid full deployment?

                                        Agreed - you presumably deploy Adobe Reader (at least in the day) and probably Adobe Flash as well - so if this gives you something helpful (access from anywhere) why not?

                                        Flash, Java.... lol

                                        DashrenderD 1 Reply Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender @wrx7m
                                          last edited by

                                          @wrx7m said:

                                          @scottalanmiller I wouldn't necessarily struggle with deploying traditional solutions. I didn't think I would struggle with Pertino LOL. It is SOOOO easy everyone said. My main concern is that I can't deploy it on certain devices like printers or items I want to access that also don't have the ability to run the client.

                                          ZT has a gateway option as well - I know Dafyre was working on it, not sure he ever got it working.

                                          So assuming you can move those two things to a LANless solution (softphones, and AV management) do you really need printer access at the ZT level?

                                          if someone asked me that I would first thing - ok the printer is remote, how do I manage it. I would remote into the user's machine and then manage the printer from their local network connection.

                                          1 Reply Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @wrx7m
                                            last edited by

                                            @wrx7m said:

                                            @scottalanmiller I wouldn't necessarily struggle with deploying traditional solutions. I didn't think I would struggle with Pertino LOL. It is SOOOO easy everyone said. My main concern is that I can't deploy it on certain devices like printers or items I want to access that also don't have the ability to run the client.

                                            It is SOOO easy, when you deploy it as designed 🙂

                                            Printers are an "issue" but outside of what we want to be location agnostic and if you need to get around that we have this new thing around the late 1980s called a printer server. So that's not a real issue today.

                                            What other devices are causing problems?

                                            JaredBuschJ wrx7mW DashrenderD 4 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 8
                                            • 9
                                            • 4 / 9
                                            • First post
                                              Last post