Seriously Impressed by Pertino Speeds
-
We have ADConnect on now too. Have not seen an issue though. It's been solid and fast since we turned it on, but it has not been a long time.
-
@scottalanmiller said:
We have ADConnect on now too. Have not seen an issue though. It's been solid and fast since we turned it on, but it has not been a long time.
I turned it on, set the DNS servers as resources and the LOB application died because all traffic was routing over Pertino instead of the LAN.
-
@JaredBusch said:
I turned it on, set the DNS servers as resources and the LOB application died because all traffic was routing over Pertino instead of the LAN.
Oh yes, that is how it is expected to work, at least that's my understanding of how the ADConnect work. We were not expecting any LAN traffic, we have everything in the software defined network.
-
That is the one issue in today's version of AD Connect. There can be suboptimal routing when your Pertino-enabled devices are local to the resources they are accessing (unless you disconnect Pertino on those laptops when they hit the LAN).
A near-term release has additional filtering that detects connectivity based on SSID/network and determines routing.
-
@scottalanmiller Your set up is perfect for Pertino since most of your AD servers are offsite, so the system doesn't have to decide how to route...Pertino is the only option.
-
@Josh said:
A near-term release has additional filtering that detects connectivity based on SSID/network and determines routing.
That will be great. Near field detection would be very handy. We are definitely lucky that all servers of all types are remote to all end user equipment.
-
Oh i thought pertino had lan/wan detection already.
-
@Hubtech said:
Oh i thought pertino had lan/wan detection already.
Well it does insofar as it is not part of the VPN system but part of the DNS system. You can do it manually anyway that you like. But the Pertino system itself does not push down any detection or force anything yet.
-
@Hubtech No prioritization yet. The only detection is on the receiving side if you're using AD Connect (ie local device without Pertino tries to access local file server - the filter guarantees it receives local address rather than Pertino 50.203.224.x). Nothing to do with routing, more with controlling IPs that are handed out.
I do know of customers that have set prioritization for interface that is used. Supposedly this helps.
-
And the exact problem I am having is that the Dynamics NAV SQL Server and the RDS server when both put on Pertino were routing all traffic over Pertino instead of locally. I took the SQL server out of the network (made its own network) and everything started working again.
What Pertino is waiting on me for is some packet captures that I have not had time to create.
Because I seen odd behavior of LAN devices without Pertino also having problems access SQL. Those devices have the NAV client locally installed.
