FirePass etwork access client Mac OS X

I'm wrestling with this problem as well. I can't figure out how to get it to trigger the installation of the network access client on any Mac browser. I've copied the urls that a windows browser gets and is displayed to a user, and loaded them on all the Mac browsers and each one always spits out an error message saying that the browser is not supported.

 

 

This site claims that Firepass version 5.5 automatically installs what it needs on Safari, but that a stand-alone network access client installation is required for other Mac browsers (like Firefox):

 

http://it.emory.edu/showdoc.cfm?docid=6389

 

 

Let me know what you find? I'll do the same.

I don't have a Mac so I am unable to test. Safari should be supported but you probably don't want to use the link you get from IE on a windows machine. You should just log in and then click on the Network Access link. The alternative is to have the Firepass admin do a manual client download from the admin page and place it somewhere you can download and install it.

I just double check the client downloads and realized that the client downloads are for x86 and WinCE. I suppose the only way to get the client is from the network access link. If this does not work you should open a case with support.

 

 

Fuzz

 

I just had the same issue with a user running a Mac OS X 10.4.x and if they right clicked on the access icon and chose "run with Rosetta" the client would install.

I am new here opn these forums and a new customer of the Firepass VPN solution. I thought I'd chip in on this because I had no problems whatsoever gettng the right plugins to download with OSX 10.4.x. This was with Safari, Firefox and Camino. There were 2: InspectionHost.dmg (a mountable disk image) and F5 SSL VPN Plugin.plugin/f5_sslvpn.bundle. They installed correctly, however, since I upgraded to 10.5 Leopard the bets are off. They installed okay, the InspectionHost plugin worked correctly, by the SSL VPN tries to start up and then gives the error 'pppd service cannot be started' or some such. The Firepass is build URM-6.02-20071001 on a 1200.

 

What can the problem be? Maybe the plugin is incompatible with this new OSX version?

 

 

Willem

The plugin is incompatible with new OS(10.5) and Product Development is working on support for Leopard.

Thanks for the quick reaction! I'll just have to wait then. Luckily most of our Mac clients are still on 10.4 and that works correctly.

 

How am I going to know when it's solved by the way? Here in this thread or elsewhere?

 

 

Willem

There are two ways you can stay informed:

 

 

1) In a day or two there will be a solution on askf5, SOL8076.

 

 

2) You can contact F5 support and inquire about the status of CR88338. Doing this is a good idea in general because the more customer inquiries there are for a given CR the higher priority the CR becomes.

 

 

--Jared

Small update. I installed the hotfix (see my earlier post) and a reboot the problem still exist (Firepass closed connection (code 38)).

 

At the second try I got the 'pppd daemon did not start' error.

 

 

It seems to me that the hotfix does not work for this problem. I found the following detail info:

 

 

'Fixes for 1.PPPD not closing on link down; 2.DNS issue on MacOSX Leopard'

 

 

Well, pppd does *not* close on exit.

That's interesting. Have you reported this to technical support yet? If there is an issue with the hotfix, it needs to be reported to them and passed up the chain to development to get fixed.

 

 

Thanks for letting us know your results, but make sure to notify Technical Support as well if there is indeed a hotfix issue.

 

 

Colin