@scottalanmiller Is hosted considered traditional? I didn't know.

@Breffni-Potter I want the user to be able to connect to anything on my LAN that I want to give them access to. File server, shoretel, printers et al. I want for me to be able to get to anything I want, period.

I know the standards of different VPN tech, like IP-sec, SSL, etc.

@Breffni-Potter Right now I have Windows Server 2008 R2 with a God-forsaken PPTP connection. I am open to an appliance- virtual or physical.

@Breffni-Potter I understand what traditional VPN is. I want to know if someone has a recommendation as to which "brand" is good and/or which to avoid.

I know this isn't traditional but it still piqued my interest. Has anyone heard of Pritunl?

http://pritunl.com/

I have a webex with Pertino tomorrow to discuss my issues with the engineers. We will see how that goes. I am still interested in traditional VPN suggestions.

@scottalanmiller I was asking for suggestions on traditional VPN several posts up but everyone kept telling me to use ZT LOL. For a "traditional" VPN, do you have suggestions? I like the connection/client running as a service feature of pertino and ZT that enables to run prior to user login.

Anyone have experience with privatetunnel?

https://www.privatetunnel.com/home/

Edit - Looks like top tier is 10 devices. NM, if that is the case.

@Breffni-Potter said:

Stick the summary at the top of the thread so it does not get lost

It has been at the top of the thread. It is my OP.

So in summary-

Pertino 520+ builds break my DNS when installed on my DNS servers
Pertino gateway does not allow any pertino network traffic to pass through it in my experience. I have tried Ubuntu Server 14.04.3, Ubuntu Server 15.10 and CentOS 7 all with Pertino builds 510, 520, 526 and 528.

@scottalanmiller Right but you weren't using it when 520 came out.

@scottalanmiller I haven't even gotten to a point where I can say that DNS does or does not work across the gateway because I can't even get any traffic to traverse the gateway. It gets there then stops.

@scottalanmiller DNS bug is in Pertino because it prevents the dynamic updates of all host records on my DNS servers.

@scottalanmiller Well, I am saying prior to it being made public. I do see your point. In terms of when everyone else knew about it. I was dealing with pertino devs/engineers in trailing a year ago.

@scottalanmiller said:

@wrx7m said:

@scottalanmiller LOL - Semantics. The gateway product was "developed/engineered" for the purpose of allowing access to devices that did not have the actual client installed on them.

And it is very, very important to understand that none of us recommended the system you are discussing or saying that it was easy. I realize that the name is all Pertino, but the Pertino product we spoke of was designed and produced to be a fundamentally different product that how you are trying to use this. I would say that they can't even be considered the same product given the gaps in "intent".

Also, the DNS bug is a problem that prevents me from using it. period.

@scottalanmiller I understand that things have changed with the cradlepoint acquisition but the release of the gateway was prior to that.

@scottalanmiller I was using the term loosely to describe my windows 8.1 workstation in my office. Where I can connect to using screen connect.

@scottalanmiller Well, with ssh it would not be so bad but in the world of gui, it is a pain because you are resizing windows and scrolling and waiting for screen refreshing, etc.

@scottalanmiller LOL - Semantics. The gateway product was "developed/engineered" for the purpose of allowing access to devices that did not have the actual client installed on them.