OS-X and GP - Machine Start

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

OS-X and GP - Machine Start

L6 Presenter

Need some feedback. 

 

On Windows 10 this doesn't seem to be a problem but for OS-X (version 10.14.3 Mojave) GP doesn't connect on a reboot.  It's saying the portal isn't available.  I think GP is starting up before the the NIC and that's what's causing this.  Does anyone have any pointers on where to look?

 

We're running GP version 4.1.6.

 

20190129_090336.jpg

1 accepted solution

Accepted Solutions

mine is user prompt, which explains the big difference -_-

it only kicks in once i'm logged on

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

6 REPLIES 6

Cyber Elite
Cyber Elite

Could there be latency on your DNS resolution, or the speed with which you are connected (latency on DHCP, mounting your nic, some sort of CaptivePortal you first need to get past,..)

 

i'm on 10.14.3 also and don't have this issue on 4.1.8-2, may want to give that a spin if all else fails?

 

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization


@reaper wrote:

Could there be latency on your DNS resolution...?

 


 

 

Might be a DNS/DHCP latency thing...resources over over two distinct links one is ~40ms the other ~11ms.

 

Network SVI is local ~1ms though

 


@reaper wrote:

mounting your nic 


 

 

Any pointer on where to look in OS-X for this?

 

 


@reaper wrote:

 

i'm on 10.14.3 also and don't have this issue on 4.1.8-2, may want to give that a spin if all else fails?

 


 

Hopefully won't come to that...I think the other two scenarios are more likely.  Is there anyway to tell GP to "retry" after it initially fails?

I found the problem, well at least it was relayed to me.  The WiFi doesn't start up until the user has logged in if the machine is a stand-alone machine.  This laptop currently isnt' domain joined.  So it makes sense why GP isn't working initially.

 

Is there anything that can be done in GP to get it to retry?

good question, i'm not sure honestly

there may be, i don't have that issue (but I also hardly ever shuit down my machine ...)

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

@reaper For this I'm being asked to "fix it."  I've currently got "pre-login" / "Always-on" with machine cert auth.

 

Since the NIC stack doesn't start until a user logs in can you explain a bit more for your config?  Is your GP setting an always on, or is it user prompt?

 

I was just going to create a new GP profile for OS-X that was based on user prompt ahead of the always-on profile to solve the problem, but if you had another suggestion I'd love to hear it.

mine is user prompt, which explains the big difference -_-

it only kicks in once i'm logged on

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization
  • 1 accepted solution
  • 2593 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!