Jump to content
Welcome to our new Citrix community!

Client Issues on MAC OS


M Web

Recommended Posts

Howdy,

Running Netscaler 13.0 currently, we have a support tunnel established which is a split tunnel configuration. Connectivity to the tunnel is OK through Windows clients, but appear to be having issues with Mac OS users connecting.

Some of the log from a failed connection is showing:

 

[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Failed to create config dictionary.  Error = Error Domain=NSCocoaErrorDomain Code=3840 "Unescaped control character around line 1, column 423." UserInfo={NSDebugDescription=Unescaped control character around line 1, column 423., NSJSONSerializationErrorIndex=423}
[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Failed to parseConfig data.
[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Error parsing configuration.
[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: NSGAuthController - Auth failed status - 81. Possible misconfig on Gateway
[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: ConnectionMotherViewController - Got generic error

 

Anyone got any ideas of where I might start looking in an attempt to start troubleshooting.  We are primarily a windows shop, so I don't personally have a MAC to test and try and re-produce the issue on.  Windows clients are connecting fine with no issues, this only appears to be related to MAC using the SSL VPN connection.

Any suggestions appreciated.

Link to comment
Share on other sites

I don't really know what a Mac is (and I refuse to do), but as far as I can see, the client is unable to create a config file.

On 3/18/2024 at 1:23 AM, M Web said:

[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Failed to create config dictionary.  Error = Error Domain=NSCocoaErrorDomain Code=3840 "Unescaped control character around line 1, column 423." UserInfo={NSDebugDescription=Unescaped control character around line 1, column 423., NSJSONSerializationErrorIndex=423}

So the client can't create the directory needed to store the config file.

On 3/18/2024 at 1:23 AM, M Web said:

[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Failed to parseConfig data.
[Mar 15, 2024 at 10:55:05 AM GMT+10:30] <Error>: Error parsing configuration.

These ones don't surprise me: No config directory, no config data.

As far as I understand, MacOS seems to be just a custom shell for BSD, and BSD is UNIX. I guess, the user who installed this client does not have the right to create a subdirectory in the desired location (following UNIX best practices, this should be /etc).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...