Connecting Home PC to Max OS Leopard VPN

Hi,
I'm wanting to work out how to connect my Windows XP PC at home to the Mac OS X leopard Server VPN at work.
Could someone help?
Cheers,
Johnny

Here are the instructions that have worked for me in the same situation. A colleague found these but didn't provide a link to the source, so I'm not sure where they're from.
Windows VPN Settings
Step 1 - Edit the registry
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Services\IPsec
3. On the Edit menu, point to New, and then click DWORD Value.
4. In the New Value #1 box, type AssumeUDPEncapsulationContextOnSendRule, and then press ENTER.
5. Right-click AssumeUDPEncapsulationContextOnSendRule, and then click Modify.
6. In the Value Data box, type one of the following values:
• 0 (default)
A value of 0 (zero) configures Windows so that it cannot establish security associations with servers that are located behind network address translators.
• 1
A value of 1 configures Windows so that it can establish security associations with servers that are located behind network address translators.
• 2
A value of 2 configures Windows so that it can establish security associations when both the server and the Windows XP SP2-based client computer are behind network address translators.
7. Click OK, and then quit Registry Editor.
8. Restart the computer.
Step 2 – Set up the VPN Client in Windows
Open up control panel
Click on Network Connections
Create a connection
Crate a connection to connect to my business (VPN)
IP address is xxx.xxx.xxx.xxx
On security tab click on IPSec Settings
Shared key is xxxxxxxx
Start up the connection and enter userid and password information.

Similar Messages

  • Using the native Snow Leopard VPN Client

    Hello,
    The company I work for recently began using ciso anyconnect for vpn connections. Before the switch I was able to use the native snow leopard vpn client to connect to the cisco vpn. I would like to know if this is still possible with cisco anyconnect. Thanks for the help.

    Actually, we just answered our own question.
    The cisco router is an older 2600 now slated with EoL.
    Cisco IPSec protocol in the newer current Cisco IOS may not be compatible with OSX 10.6.4
    The 2600 IOS is no longer supported, hence older IOS, hence the conflict.
    So there ya go ... stay with current Cisco equipment and 10.6.4 native will probably work. 10.6.4 is dead to older Cisco.
    Message was edited by: Walter Johnson

  • Leopard VPN open ports

    Hello,
    I use standard Leopard VPN for connecting laptop to my office network. Web and Exchange mail work fine but I cannot get connection to Perforce server (port 1666). Changing firewall settings didn't help. My Windows environment uses same VPN and Perforce servers and doesn't have this problem.
    Thanks

    Hello avilt,
    VCA stands for Virtual Cluster Agent. This is basically used when the VPN 3000 pair is configured for load balancing... when doing this the boxes talk to each other on VCA and we normally need to allow this on the filters ..
    My question is, have u enabled this filter on the public interface ?? are u seeing the ports going through the VPN concentrator or are u doing a VA scan and seeing these ports (like FTP) open on the VPN concentrator?
    Raj

  • Windows 8 crashes when trying to connect to a Remote Desktop or a VPN

    Hello, 
    When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network
    machine).
    Useful PC specs:
    - i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board)
    > All latest drivers and Windows updates installed.
    > Ran Memory Diagnostic. No errors.
    Event Log:
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a
    Exception code: 0xc0000005
    Fault offset: 0x00000000000027ee
    Faulting process ID: 0x994
    Faulting application start time: 0x01cdf16f9b46e882
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\DUI70.dll
    Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a
    Faulting package full name: 
    Faulting package-relative application ID: 
    WinDbg: (RDP Crash dump with procdump)
    Loading unloaded module list
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (994.1118): Access violation - code c0000005 (first/second chance not available)
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> .ecxr
    rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000
    rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0
    rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000
     r8=0000000000000001  r9=000000989f3afa28 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=00000098a1d29401
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> !analyze -v
    *                        Exception Analysis                                   *
    GetPageUrlData failed, server returned HTTP status 404
    URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    FAULTING_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    DEFAULT_BUCKET_ID:  NULL_POINTER_READ
    PROCESS_NAME:  mstsc.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    READ_ADDRESS:  0000000000000000 
    FOLLOWUP_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    MOD_LIST: <ANALYSIS/>
    NTGLOBALFLAG:  0
    APPLICATION_VERIFIER_FLAGS:  0
    FAULTING_THREAD:  0000000000001118
    PRIMARY_PROBLEM_CLASS:  NULL_POINTER_READ
    BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ
    LAST_CONTROL_TRANSFER:  from 000007fec5be7db8 to 000007fec5be27ee
    STACK_TEXT:  
    00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe
    00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98
    00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689
    00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e
    00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20
    00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37
    00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69
    00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2
    00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66
    00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8
    00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56
    00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242
    00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc
    00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113
    00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b
    00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151
    00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc
    00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310
    00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b
    00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159
    00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5
    00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4
    00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af
    00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f
    00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104
    00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc
    00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6
    00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20
    00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19
    00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219
    00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113
    00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69
    00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168
    00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12
    00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec
    00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7
    00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9
    00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63
    00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8
    00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56
    00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72
    00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a
    00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b
    00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695
    00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f
    00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375
    00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    STACK_COMMAND:  ~0s; .ecxr ; kb
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  dui70!DirectUI::Element::_SetValue+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dui70
    IMAGE_NAME:  dui70.dll
    DEBUG_FLR_IMAGE_TIMESTAMP:  50108e6a
    FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue
    BUCKET_ID:  X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    Followup: MachineOwner
    Any ideas what could be the problem and how to resolve this?

    Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.
    I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that
    provides a program that'll hash the password for you. I used it so I can say its safe:
    http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/
    I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for
    those in a bind this will work for you.
    This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

  • There was a problem connecting to the server "Max Time Capsule"

    Disclaimer:  Previously posted here (Ask Different) and similar to this.
    I'm trying to use my MBP inside and outside my office, and having it backup to my 2TB Time Capsule when on its wireless network, or defer backups when not on the Time Capsule's wireless network.
    Unfortunately, if I've been on a different wireless network for a few hours worth of backup attempts, bringing the machine back onto the Time Capsule's wireless network doesn't resume backups, and Time Machine never recovers. I can select the disk as a backup drive in the Time Machine preferences, but the disk remains unavailable from the Finder, and any backup attempts yield the standard:
    There was a problem connecting to the server "Max Time Capsule"
    Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.
    My WiFi connection is through the same Time Capsule that hosts the backup drive, and its name and IP address have decidedly not changed. The only thing that seems to help is restarting the Time Capsule, but that is an inconvenient workaround at best.
    The problem sounds similar to Backup Disk Not Available, but the answers to that question are either to restart or change the disk name or turn off the 5 GHz network (which didn't help). I also looked at /Library/Preferences/com.apple.TimeCapsule.plist, but found nothing that seemed relevant.
    Any suggestions would be greatly appreciated. My MBP is running OS X 10.7.5, and the Time Capsule firmware is 7.6.1.

    There was a problem connecting to the server "Airport Time Capsule".
    The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.
    I still have internet connection, and have tried other suggestions across internet but really the only fix has been to power cycle the ATC. This unfortunately is only a temporary remedy for a day or so until it returns.
    Any suggestions on how to fix this problem?
    There is no fix.. I have written a bunch of suggestions to try.
    https://discussions.apple.com/thread/6106750?tstart=0
    It is very common on Mavericks.
    How long did it take from when you set it  up till it went bad??

  • On my windows 7 machine, itunes won't connect home sharing with apple tv

    On my windows 7 machine, itunes won't connect home sharing with my apple tv.  This problem started about two itunes updates ago.  Any thoughts?

    Try a search of the forums or the "More Like This" section to the right.
    Also might have better luck posting to the Apple TV forum.

  • Trying to connect Airport time capsule to my leopard iOS mac.  Downloaded software for time capsule for snow leapard/leopard but still says I need more software.  What do I need?

    Trying to connect Airport time capsule to my leopard iOS mac.  Downloaded software for time capsule for snow leapard/leopard but still says I need more software.  What do I need? I have a 10.5.7 iOS (Leopard).  It connects to wifi at speeds in the airport and has plenty of storage capacity and memory.

    If your Time Capsule looks like this..
    Please review the System Requirements to set up and administer the device.....
    Setup and Administration
    iPhone, iPad, or iPod touch with iOS 6 or later and AirPort Utility 1.3
    Mac with OS X Lion v10.7.5 or later and Airport Utility 6.3 or higher
    http://www.apple.com/airport-time-capsule/specs

  • Connect to a local server whilst using VPN

    I have SABnzbd+ running on my MBP.
    Since my Linksys WAG320N router supports NAT Loopback, I can connect to it's web UI using my local IP, 192.168.0.2 OR my ISP-assigned static IP, 72.xxx.xxx.xxx.
    However when I'm connected to the VPN, using OpenVPN & Viscosity, I can't connect to the SABnzbd+ server on either address.
    I tried setting up DynDNS with their auto-updater, and using a host name instead of IP address, still no luck.
    I use SABnzbd+ as an example, it's the same problem with ANY locally runnining server (uTorrent UI, etc).
    Thanks

    I use the built in VPN for company access. However, by default it "sends all packets to VPN route", which I do not like. I put together a script to set only the networks I need to go through that route using the "route add" comment. I set my default route whatever my ISP default route is at the time of my connection. This allows me both worlds (vpn connections and internet). Not sure if that helps you or not.

  • I can't connect home sharing or I can't longin iTunes

    I try to connect home sharing or ITunes I can't login on my pc windows7

    I try to connect home sharing or ITunes I can't login on my pc windows7

  • WRVS4400N - MAC OS X LEOPARD VPN

    i've called linksys on different issue, but i also mention i had some problems connecting from my mac os x leopard to my linksys wrvs4400n, and they said i shouldn't have any problem doing so
    i was wondering if anyone had a successful connection between those two
    thanks

    alexus wrote:
    i've called linksys on different issue, but i also mention i had some problems connecting from my mac os x leopard to my linksys wrvs4400n, and they said i shouldn't have any problem doing so
    i was wondering if anyone had a successful connection between those two
    thanks
    You can also download IPSecuritas and set it up that way. I've been using that for some time and it works like a champ. Don't know the link off hand but do a Google on it and you will find it right away. BTW its free.

  • Is it possible to connect home cinema new iMac?

    As in title
    Is it possible to connect home cinema harman kardon bds to new iMac through thunderbolt-hdmi or other way?
    Thanks,
    A.

    are you trying to hame your imac play out of your stereo
    or are you trying to input audio from your stereo into your imac?

  • Problem connecting iChat client 10.6 (Snow Leopard) to iChat server (Lion)

    Hi guys,
    I'm fairly new to the Lion server, but it's all working fine with my Lion client(s) so far 
    However, my wife's best friend's MacBook is still running Snow Leopard ( and she is not willing to upgrade her MacBook as of now due to severak reasons) and I'm trying to connect her iChat client from Snow Leopard to the iChat server running on my Lion server.
    If I try to set up the account manually in the iChat client, I can't find an option for Mac OS X Lion server and trying a work around with the Jabber account settings didn't work either (on the server's log: credentials failed). Then, I tried to create a profile on the server and downloaded it to the Snow Leopard system, but it wasn't recognised (in System Settings, there is no Profile option ).
    So, can someone please, please, please give me any idea about it or is it simply not possible to connect a an older iChat client (5.0.3, Snow Leopard) to the latest version of the iChat server (Lion) ??
    Again, any idea is very appreciated!
    Many tx in advance.
    Cheers
    Kai

    Hi there,
    A simple suggestion , please make sure both MacBook Pro clock and the server clock are the same meaning the hour/Min/ sec both should match. A least difference of 3 seconds is fine.
    I had faced this problem in many place and only solution was to match the time and it will bind immediatly.

  • Finally got my Globe Trotter Connect Rocket Stick to work Snow Leopard

    On Sept 29th at 10:00 pm I wrote this email to Rogers.
    Please pass on this very important information. The Rogers download for icon 322 from your site for Globe Trotter Connect does not work with Snow Leopard. Snow Leopard is 10.6 version . Recommend download for Snow Leopard by Rogers is 10.4, icon 322. Which is for Leopard and Tiger so this is the wrong download for Snow Leopard. Believe me when i tell you that i have devoted 10 hours to figuring out what the problem is. I have worked with Technical Support at Rogers, Apple Care Specialist and Options Tech Department. Here is how I finally fixed the problem. Please share this information with your Tech Support Department. Customers calling in with the same problem. They should go to the ATT website. ATT has the version 10.6 which is the right download for Snow Leopard and it listed in red on the left hand side of their site. Once customer has removed the wrong application for Globe Trotter then downloaded the 10.6 version for Snow Leopard (off the ATT website) then instruct your customers to go to Globe Trotter Preferences. Under roaming then enter the following: Under 3G/EDGE/GPRS change to read APN: internet.com. username: wapuser1 Password:wap. IMPORTANT do not press reset, or it will not work. Just ask customer to close that window. Now the Globetrotter will initialize and ask to connect. After a few seconds internet will now work on Rogers Network. Hope you use this information and hopefully Rogers will install the link that ATT has onto their site and save everyone a lot of valuable time.
    Regards,
    Colleen Williamson

    Here is the right link. look on the left hand side in it will read New (in red) GT connect for 10.4 10.5 10.6- (10.6- is the right version for Snow Leopard)
    http://support.option.com/att/i
    Then simply go to Globe Trotter/ Preferences. then change the settings to Rogers. ie type in under APN: Internet.com etc.
    Gt2go. good luck.

  • Juniper networks VPN: Network Connect will not install under Snow Leopard

    Created different thread based on the topics from http://discussions.apple.com/thread.jspa?threadID=2130935.
    With new install of Snow Leopard i get the following when trying to log into SSL VPN "Could not launch. Please restart the web browser and try again"
    can not do the workarounds from the above thread since none of the directories exist. Has anyone found a fix for this?

    I ran into this too (made matters worse by cleaning out the old juniper install). What I understand clearly now, which other discussions with all the happiness from people saying they fixed it seem to miss completely: Juniper only works if you installed it prior to upgrading 10.6. If you did not, you are possibly hosed.
    Now, I was hosed, but I found a workaround. Find a stand-alone installer .dmg out there. As of a couple days ago it was there. I'm sure it still is. Google it. NetworkConnect.dmg.
    It is version 6.0.0. It installs correctly. My company runs 6.4.0, which means the first time you open NetworkConnect after installing it prompts you to upgrade. The upgrade worked fine, so long as I was running as root.
    Which brings me to my original problem which I've not seen anyone else complain about, which has me worried: after installing, NC only actually connects and functions when I run as root. I'm not talking about su - root or using sudo, I mean having to graphically switch users and log into the computer as the root user (after enabling it...using the scenableroot I think, something like that).
    Has anyone else seen this behavior? I can launch Network Connect as my real user but it immediately fails with a software error. 'ncproxyd.error: Failed to gain root privileges'. Driving me batty.

  • Snow Leopard VPN will not let users connect consistently

    I did a clean install to Snow Leopard, and now my VPN is completely odd. It randomly does or doesn't let users connect.
    Setup:
    - Snow Leopard 10.6
    - OpenDirectory has been added to (vpnaddkeyagentuser /LDAPv3/127.0.0.1)
    - Firewall is off for these tests to rule it out as being the problem
    - IP address and FQDN are the same as they were when server was 10.5
    - DNS, DHCP, and all other services are working fine
    - To rule out password problems, all of the passwords in the test are the same
    - All tested accounts have the same password
    I attempted 3 connections with each account in each scenario
    Round 1 - Access set to all users and all groups, and admins have access to all services.
    Test1 - local admin: worked, failed, failed
    Test2 - od normal : worked, worked, worked
    Test3 - od admin : worked, failed, worked
    Test4 - local admin: worked, worked, worked
    Round 2 - Access set to only those in the group "Test Group", and admins have access to all services. "Test Group" only includes the users: Test2 and Test3
    Test1 - local admin: failed, failed, failed
    Test2 - od normal : failed, worked, worked
    Test3 - od admin : failed, failed, failed
    Test4 - local admin: failed, failed, failed
    Is anyone else having these odd VPN problems?

    I figured out the problem with the VPN, but is stretched well beyond VPN.
    I'm not sure exactly how everything melted down, but somehow the installer messed up massive amounts of things. I won't even go in to it other than to say...
    - Certain programs wouldn't install to the primary drive (they'd show the drive, but with a "!" on it)
    - Mean while when booted normally, Disk Utility would not see and drives except the CD rom
    - No two programs saws the same set of hard drives or cds
    - If you booted from CD, Disk Utility saw all drives, but Start Disk only saw the CD
    - Software Update (even from the command line) would fine no new updates, even though none had been applied
    - If you blessed the primary hd, it would boot, but if you tried to boot normally you'd get a flicker "?" folder and Apple symbol
    - etc...
    The weird thing is, all of the other services were working fine (Web hosting, VPN, AFP, SMB, firewall, ical, ichat). But obviously something dreadful had happened during the install, which is odd because it was a clean install.
    I reformatted the drive, reinstalled, and all is fine now.
    Weirdest installation problem I've ever encountered.

Maybe you are looking for