Home Forums Archive VaporSec Connecting to SonicWall with Manual Keys

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #356495
    Anonymous
    Participant

    Hello-

    1st off, I want to thank you for all the help and support you give everyone trying to get their software configured. You provide a great service. And onto my question…

    I can not for the life of me figure out how to connect using “Manual Keys”. My work network is a Windows 2000 server running SonicWall and the method they choose is manual keys (SSL). Being a Microsoft shop, I get little support trying to get a Mac on the network.

    My home computer is a PowerBook running OS X 10.2.8 and the latest VaporSec. Can anyone point me in the right direction for using these manual keys to get me in? I’d love to work from home on my Mac rather than a crappy-out-dated Win98 box…

    Thank you-
    Ray

    #356501
    Anonymous
    Participant

    That Joel…. guess I need to learn more about configuring first. I added the cert to the ID tab, but the program errors on trying to parse the racoon file. I’ll read up more to see what I am doing wrong.

    #356511
    Anonymous
    Participant

    No dice on these certs. I think it is beacause the way these things are being created. (Basically registry entries for a windows box). I am going to have to find another way in. Thanks for your help though…

    #356730
    MattBrink
    Participant

    Before I get started let me say that I’m far far from an IPSec expert. I was wondering if the “Manual” setup on the Sonicwall really uses a certificate. I have this setup working between my Sonicwall SOHO and the client software running on XP. I’d love to get it setup on X.3 but I’m not sure where to start.

    Here is a link to a page that describes the manual key setup on the Sonicwall. Maybe this will help in figuring out what needs to be filled out where on the Mac side.

    http://www.hornick.org/tutorials.php/tutorial/7

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Comments are closed