Jump to content

29e592b6-6d49-4c32-91e7-4f054eaf5b85

Members
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About 29e592b6-6d49-4c32-91e7-4f054eaf5b85

  • Rank
    Unable To Browse Client
  1. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    So far so good! Thank you guys for your help. I now have a working solution. Now that it's not broken I shall try not to fix it
  2. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    I have just had a success experience. Did a clean 10.6.0 install on the mini and adding the NAS worked as it should. And with great joy I can report that the drives on the client were also listed correctly. I am just now running a full software update on the mini and will return with an update. Perhaps there's light at the end of the tunnel
  3. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    The Mac Mini uses only original Apple supplied RAM. I have no trouble adding the shares via CMD+K in Finder and accessing them this way. It works flawlessly. I have absolutely no problems running the engine on OSX 10.6 AND adding/using the NAS as a source. But the Engine on Intel+10.6 refuses to list the drives of the Client on the Xserve G5 (PPC)... Which brings it back to the OP of this thread. (No triangle in front of the client in the sources list, etc. etc.). As mentioned I'll be testing if SMB (or NFS for that matter) will fix it for me. I'm happy to know that it works for you on 10.6.8. But then that's opposite of what you post at the top of the page... Thank you. Edit: The Mac Pro is out of the equation for now as it has been put to use for other tasks.
  4. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    That's a good suggestion. I've just tested and the result was exactly the same. The share I tried to access is an AFP share on the Xserve G5 (OS X 10.5 Server). Exactly the same behaviour. First it says "invalid credentials" and then 5 seconds later I get Kernel Panic. :-( Did I mention that Cmd+K to the share works flawlessly? And that adding the share in Retrospect on 10.6 on the same machines works fine as well... Next I'm going to try adding SMB to the ReadyNAS share and see if that plays nicely. If that fixes it and I'm not in for yet another round of problems then that's what I'll use. All this trouble because Retrospect under 10.6.8 doesn't list the clients drives/shares.
  5. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    Network setup: - Netgear ReadyNAS with one share for backup - Cisco Switch - Machine running Retrospect engine Retrospect server 1 HW: (this is the only working one so far...) Dual-core PowerPC G5 3,5 GB RAM Mac OS X 10.5.8 Retrospect server 2 HW: Model Name: MacPro Model Identifier: MacPro1,1 Processor Name: Dual-Core Intel Xeon Processor Speed: 2,66 GHz Number Of Processors: 2 Total Number Of Cores: 4 L2 Cache (per processor): 4 MB Memory: 3 GB Bus Speed: 1,33 GHz Boot ROM Version: MP11.005C.B08 SMC Version (system): 1.7f10 Retrospect server 3 HW: Model Name: Macmini Model Identifier: Macmini3,1 Processor Name: Intel Core 2 Duo Processor Speed: 2,26 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 3 MB Memory: 2 GB Bus Speed: 1,07 GHz Boot ROM Version: MM31.00AD.B00 SMC Version (system): 1.35f1 Notes: When server 2 runs Snow Leopard (10.6.8) there are no problems adding the network share as a source. But it is unable to list shares on the client. When server 2+3 run Leopard trying to add the network share results in Kernel Panic. I've attached the Console Panic logs. As far as I could read they say "Retrospect"... Excerpt of a panic log: Thu Aug 18 11:42:15 2011 panic(cpu 2 caller 0x001AB0FE): Kernel trap at 0x0017f403, type 14=page fault, registers: CR0: 0x80010033, CR2: 0xc0070014, CR3: 0x39181000, CR4: 0x00000660 EAX: 0x00000001, EBX: 0xc0070000, ECX: 0x095605d0, EDX: 0x094abe38 CR2: 0xc0070014, EBP: 0x4a31f8c8, ESI: 0x00000000, EDI: 0x00000000 EFL: 0x00010286, EIP: 0x0017f403, CS: 0x00000008, DS: 0x012c0010 Error code: 0x00000000 Backtrace (CPU 2), Frame : Return Address (4 potential args on stack) 0x4a31f6c8 : 0x12b4c6 (0x45f91c 0x4a31f6fc 0x13355c 0x0) 0x4a31f718 : 0x1ab0fe (0x469a98 0x17f403 0xe 0x469248) 0x4a31f7f8 : 0x1a1713 (0x4a31f810 0xe00002d8 0x4a31f8c8 0x17f403) 0x4a31f808 : 0x17f403 (0xe 0x4a310048 0x4a310010 0x4a310010) 0x4a31f8c8 : 0x162d9a (0x94abe38 0x0 0x0 0x3) 0x4a31fa38 : 0x1aaeaf (0x1ec1d14 0x3d3f3000 0x0 0x3) 0x4a31fb18 : 0x1a1713 (0x4a31fb30 0x53d63c 0x4a31fbc8 0x4b01e670) 0x4a31fb28 : 0x4b01e670 (0xe 0x360e0048 0x4a310010 0x420010) 0x4a31fbc8 : 0x4b01ef09 (0x360e1000 0x3d3f3000 0x4000 0x4b019583) 0x4a31fc08 : 0x4b01f6f8 (0x360e1000 0x360e10c8 0x40000 0x4115eb) 0x4a31fc58 : 0x4b07711e (0x360e1000 0x360b6000 0x621bd80 0x621bd80) 0x4a31fc78 : 0x4b0375a9 (0x360e1000 0x360b6000 0x4a31fca8 0x4195d1) 0x4a31fc98 : 0x4b03bf99 (0x360e1000 0x360b6000 0x4a31fcd8 0x412a65) 0x4a31fcb8 : 0x4b03e349 (0x360e1000 0x360b6000 0x6cfc340 0x360e1000) 0x4a31fcd8 : 0x4b017aaf (0x360e1000 0x360b6000 0x74e2000 0x725708c) 0x4a31fd08 : 0x415e83 (0x360b6000 0x621fbe4 0x621fbe4 0x1) Backtrace continues... Kernel loadable modules in backtrace (with dependencies): com.apple.GeForce(5.4.8)@0x4b004000->0x4b09bfff dependency: com.apple.NVDAResman(5.4.8)@0x4aa9e000 dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0x4aa52000 dependency: com.apple.iokit.IOPCIFamily(2.6)@0x42a2e000 dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x4aa35000 BSD process name corresponding to current thread: Retrospect Mac OS version: 9L31a Kernel version: Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 System model name: MacPro1,1 (Mac-F4208DC8) System uptime in nanoseconds: 1741237063950 unloaded kexts: com.apple.driver.AppleHDAPlatformDriver 1.7.1a2 - last unloaded 92263018719 loaded kexts: com.apple.filesystems.afpfs 9.0.2 - last loaded 1429514116024 com.apple.nke.asp_tcp 4.7.1 com.apple.filesystems.msdosfs 1.5.5 com.apple.driver.AppleHWSensor 1.9d0 com.apple.driver.AppleUpstreamUserClient 2.7.5 com.apple.filesystems.autofs 2.0.2 com.apple.Dont_Steal_Mac_OS_X 6.0.3 com.apple.GeForce 5.4.8 com.apple.driver.AppleHDA 1.7.1a2 com.apple.driver.AudioIPCDriver 1.0.6 com.apple.driver.AppleMCEDriver 1.1.7 com.apple.driver.AppleHDAController 1.7.1a2 com.apple.iokit.IOFireWireIP 1.7.7 com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a17 com.apple.driver.AppleLPC 1.3.1 com.apple.nvidia.nv40hal 5.4.8 com.apple.driver.AppleHIDKeyboard 1.0.9b4 com.apple.driver.AppleUSBComposite 3.2.0 com.apple.iokit.SCSITaskUserClient 2.1.1 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1 com.apple.driver.XsanFilter 2.7.91 com.apple.iokit.IOATAPIProtocolTransport 1.5.3 com.apple.driver.AppleIntel8254XEthernet 2.1.2b1 com.apple.driver.AppleUSBHub 3.4.9 com.apple.iokit.IOAHCIBlockStorage 1.2.2 com.apple.iokit.IOUSBUserClient 3.4.9 com.apple.driver.AppleEFINVRAM 1.2.0 com.apple.driver.AppleFWOHCI 3.9.7 com.apple.driver.AppleIntelPIIXATA 2.0.1 com.apple.driver.AppleUSBEHCI 3.4.6 com.apple.driver.AppleAHCIPort 1.7.0 com.apple.driver.AppleUSBUHCI 3.3.5 com.apple.driver.AppleACPIButtons 1.2.5 com.apple.driver.AppleRTC 1.2.3 com.apple.driver.AppleHPET 1.4 com.apple.driver.AppleACPIPCI 1.2.5 com.apple.driver.AppleSMBIOS 1.4 com.apple.driver.AppleACPIEC 1.2.5 com.apple.driver.AppleAPIC 1.4 com.apple.security.TMSafetyNet 3 com.apple.security.seatbelt 107.12 com.apple.nke.applicationfirewall 1.6.77 com.apple.driver.DiskImages 199 com.apple.BootCache 30.4 com.apple.driver.AppleIntelCPUPowerManagement 76.2.0 com.apple.driver.DspFuncLib 1.7.1a2 com.apple.iokit.IOAudioFamily 1.6.9fc5 com.apple.kext.OSvKernDSPLib 1.1 com.apple.iokit.IOHDAFamily 1.7.1a2 com.apple.driver.IOPlatformPluginFamily 3.4.0a17 com.apple.driver.AppleSMC 2.3.1d1 com.apple.NVDAResman 5.4.8 com.apple.iokit.IONDRVSupport 1.7.3 com.apple.iokit.IOGraphicsFamily 1.7.3 com.apple.iokit.IOUSBHIDDriver 3.4.6 com.apple.iokit.IOBDStorageFamily 1.5 com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1 com.apple.iokit.IODVDStorageFamily 1.5 com.apple.iokit.IOCDStorageFamily 1.5 com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1 com.apple.iokit.IONetworkingFamily 1.6.1 com.apple.iokit.IOFireWireFamily 3.4.9 com.apple.iokit.IOATAFamily 2.0.1 com.apple.iokit.IOAHCIFamily 1.5.0 com.apple.iokit.IOUSBFamily 3.4.9 com.apple.driver.AppleEFIRuntime 1.2.0 com.apple.iokit.IOSMBusFamily 1.1 com.apple.iokit.IOHIDFamily 1.5.5 com.apple.iokit.IOStorageFamily 1.5.6 com.apple.driver.AppleACPIPlatform 1.2.5 com.apple.iokit.IOACPIFamily 1.2.0 com.apple.iokit.IOPCIFamily 2.6 Do note!: There are no Kernel Panics in 10.6.8 when adding the exact same share.
  6. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    Thank you for your reply. I'll get the complete machine details and post it. Reproducing the Kernel Panic overlay screen is pretty straight-forward on both machines. - Click "Sources" - "+ Add" - "Add share" button - Enter "afp://10.0.0.14/backup" and the user+password - Click "add" button a couple times while getting the "invalid credentials" error. - Kernel Panic My immediate suspicion is a conflict between Retrospect server 8.2 afp share login handling and the 10.5.8 network driver. As to whether it's a hardware problem I have to say a big no. Seeing as adding the share in Retrospect 8 while the machines run 10.6.8 is no problem. In 10.6 I can't see the shares on the client though... Hence trying to get this up and running on 10.5...
  7. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    And there's the culprit. Installed Leopard (10.5) on the server and set up Retrospect. This enabled me to correctly see and browse the client. Then I tried to add my NAS share in Retrospect and it kept saying "Invalid credentials".... Tried connecting to the share via Finder and everything was fine. Retried in Retro and OS X died with Kernel Panic. Oh well I thought to myself. Retrospect crapping its pants once is okay. So I rebooted, stopped the retroengine and tried transferring settings (/Library/Application Support/Retrospect/) from the old G5 (where the NAS share was added fine). Started Retrospect Engine and BOOM! Kernel Panic. Rebooted and... Kernel Panic as soon as Retrospect Engine came online. Set up a Mac Mini with OS X 10.5.8 and Retrospect Server. Tried adding the NAS... Kernel Panic! So far I'm unable to use Retrospect 8 with Intel machines with either OS X 10.5 or 10.6. This has to be the worst architecture move I've ever seen.
  8. 29e592b6-6d49-4c32-91e7-4f054eaf5b85

    Unable To Browse Client

    Hello Registered to say I'm seeing the same problem. My setup: Server: Intel Mac Pro (Mac OS X 10.6.8) Client: PPC Xserve G5 (Mac OS X Server 10.5.8) Having recently moved our retrospect server to an Intel based box I am no longer able to list/browse shares of our Xserve running the Retrospect client. There were no problems with share listing from the client to the server prior to the switch to Intel. (the problem was speed or rather the lack thereof). - I have tried reinstalling the retrospect client on the xserve, rebooting the xserve but still nothing showed up. - I have tried removing the client/share from the retrospect server. And re-adding it. Both via Discovery and via IP-address. - I've tried using a key pair and installing the client with the key included. None of this helped either. I contacted support the other day but was shun off today with a mail about me not having ASM... That has to be one of the most arrogant things I've ever experienced. The software performs terribly and is full of bugs for which fixes never come and we then have to pay $69 for "single issue support"... LOL I've been waiting 2 years for Retrospect 8 to be fixed and updating my hardware to better match Retrospect recommendations only lands me new bugs and a request to throw money at Roxio.... Nice.
×