10.4.6 AFP CONNECTION ISSUES

After upgrading to 10.4.6 I am having trouble connection to our Windows 2003 server via AFP. Has anyone had any similar issues/solutions. This only affecting one of the 3 servers that I connect to.

PROBLEM SOLVED!
I have discovered that with 10.4.6, user names and passwords are now case sensitive, whereas they were not in 10.4.5 and earlier. I went to the Windows Server and looked at how the username and password was set up for access, and saw that they were set up with both having initial caps and the rest lower case. In 10.4.5 and earlier, we were logging in over the network with all lower case on both without a problem. With 10.4.6, we have to type them both with initial caps. I banged my head against the wall and spent several days on these forums looking for this answer with no results. Today our part time PC IT guy was in and I asked him if he had any suggestions, and within 3 minutes he had solved my problem.
Thanks, Apple!

Similar Messages

  • Xsan clients error "afp connection status"    looking up "wildlife"

    Hi,
    I am facing a problem that in some of my clients after about every 2 to 3 sec. a massage pop up on finder that *"AFP CONNECTION STATUS"* LOOKING UP "WILDLIFE"
    and it keeps on coming .
    First it was coming on My Xserve (after i delete some footage from my Xsan volume) but now it also coming on the clients
    *log of my client (mac pro 2.66 , os - 10.4.9, Fcp 6.1, xsan 1.4)*
    2008-01-12 09:43:16.755 afp_mount[2459] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:43:16.756 afp_mount[2459] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:44:34.093 afp_mount[2461] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:44:34.093 afp_mount[2461] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:49:50.950 afp_mount[2469] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:49:50.951 afp_mount[2469] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:50:00.627 afp_mount[2470] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:50:00.628 afp_mount[2470] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:51:17.654 afp_mount[2482] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:51:17.655 afp_mount[2482] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:52:25.149 afp_mount[2485] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:52:25.150 afp_mount[2485] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:52:34.864 afp_mount[2486] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:52:34.864 afp_mount[2486] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 09:52:46.724 afp_mount[2488] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 09:52:46.725 afp_mount[2488] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    Jan 12 10:00:35 fcp4s-computer dashboardadivsoryd[2496]: fetch-parsers: unable to fetch data from read stream
    Jan 12 10:00:35 fcp4s-computer dashboardadivsoryd[2496]: fetch: unable to fetch data from read stream while fetch advisory list
    2008-01-12 10:16:54.766 afp_mount[2521] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:16:54.766 afp_mount[2521] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:16:55.848 afp_mount[2522] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:16:55.849 afp_mount[2522] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:16:56.399 afp_mount[2523] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:16:56.399 afp_mount[2523] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:18:12.712 afp_mount[2529] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:18:12.713 afp_mount[2529] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:18:13.720 afp_mount[2530] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:18:13.721 afp_mount[2530] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:18:14.273 afp_mount[2531] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:18:14.274 afp_mount[2531] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:19:29.784 afp_mount[2533] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:19:29.785 afp_mount[2533] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:19:30.765 afp_mount[2534] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:19:30.766 afp_mount[2534] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:19:31.271 afp_mount[2535] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:19:31.271 afp_mount[2535] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:20:46.794 afp_mount[2537] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:20:46.794 afp_mount[2537] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:20:47.782 afp_mount[2538] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:20:47.782 afp_mount[2538] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:20:48.265 afp_mount[2539] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:20:48.265 afp_mount[2539] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:22:03.737 afp_mount[2551] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:22:03.738 afp_mount[2551] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:22:04.779 afp_mount[2552] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:22:04.780 afp_mount[2552] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:22:05.240 afp_mount[2553] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:22:05.241 afp_mount[2553] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:26:00.283 afp_mount[2554] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:26:00.284 afp_mount[2554] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:27:17.337 afp_mount[2561] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:27:17.338 afp_mount[2561] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:28:34.347 afp_mount[2562] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:28:34.348 afp_mount[2562] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:29:51.324 afp_mount[2563] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:29:51.324 afp_mount[2563] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:31:08.280 afp_mount[2564] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:31:08.280 afp_mount[2564] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:32:25.319 afp_mount[2571] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:32:25.320 afp_mount[2571] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:33:42.324 afp_mount[2572] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:33:42.325 afp_mount[2572] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:34:59.414 afp_mount[2573] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:34:59.414 afp_mount[2573] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:36:16.381 afp_mount[2580] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:36:16.381 afp_mount[2580] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:37:33.377 afp_mount[2581] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:37:33.378 afp_mount[2581] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:38:50.380 afp_mount[2588] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:38:50.381 afp_mount[2588] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:40:07.546 afp_mount[2595] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:40:07.547 afp_mount[2595] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:41:24.846 afp_mount[2602] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:41:24.846 afp_mount[2602] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:42:42.004 afp_mount[2603] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:42:42.005 afp_mount[2603] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:43:58.892 afp_mount[2604] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:43:58.893 afp_mount[2604] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:45:15.938 afp_mount[2605] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:45:15.938 afp_mount[2605] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:46:32.869 afp_mount[2612] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:46:32.870 afp_mount[2612] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:47:49.919 afp_mount[2613] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:47:49.920 afp_mount[2613] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:52:44.945 afp_mount[2620] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:52:44.945 afp_mount[2620] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:53:14.328 afp_mount[2621] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:53:14.329 afp_mount[2621] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:53:15.071 afp_mount[2622] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:53:15.072 afp_mount[2622] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 10:54:01.918 afp_mount[2624] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 10:54:01.918 afp_mount[2624] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:39:08.814 afp_mount[2691] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:39:08.815 afp_mount[2691] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:39:09.867 afp_mount[2692] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:39:09.868 afp_mount[2692] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:39:10.787 afp_mount[2693] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:39:10.788 afp_mount[2693] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:40:27.172 afp_mount[2696] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:40:27.173 afp_mount[2696] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:40:27.647 afp_mount[2697] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:40:27.648 afp_mount[2697] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 11:40:28.637 afp_mount[2698] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 11:40:28.638 afp_mount[2698] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:51:35.887 afp_mount[2887] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:51:35.888 afp_mount[2887] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:51:36.674 afp_mount[2888] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:51:36.675 afp_mount[2888] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:51:37.760 afp_mount[2889] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:51:37.761 afp_mount[2889] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:52:52.875 afp_mount[2891] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:52:52.875 afp_mount[2891] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:52:53.890 afp_mount[2892] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:52:53.891 afp_mount[2892] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:52:54.807 afp_mount[2893] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:52:54.808 afp_mount[2893] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:57:04.467 afp_mount[2901] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:57:04.468 afp_mount[2901] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:57:11.736 afp_mount[2903] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:57:11.737 afp_mount[2903] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 13:57:12.955 afp_mount[2904] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 13:57:12.956 afp_mount[2904] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:05:20.903 afp_mount[2911] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:05:20.904 afp_mount[2911] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:05:21.370 afp_mount[2912] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:05:21.370 afp_mount[2912] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:05:21.900 afp_mount[2914] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:05:21.901 afp_mount[2914] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:06:38.924 afp_mount[2921] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:06:38.924 afp_mount[2921] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:07:57.893 afp_mount[2924] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:07:57.893 afp_mount[2924] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:09:14.954 afp_mount[2926] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:09:14.955 afp_mount[2926] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:10:31.964 afp_mount[2929] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:10:31.964 afp_mount[2929] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:11:49.068 afp_mount[2940] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:11:49.068 afp_mount[2940] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:13:05.944 afp_mount[2942] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:13:05.945 afp_mount[2942] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:14:22.975 afp_mount[2944] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:14:22.975 afp_mount[2944] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:15:41.269 afp_mount[2945] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:15:41.269 afp_mount[2945] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:17:00.012 afp_mount[2953] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:17:00.012 afp_mount[2953] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:18:58.704 afp_mount[2954] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:18:58.705 afp_mount[2954] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:18:59.959 afp_mount[2956] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:18:59.960 afp_mount[2956] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:19:00.326 afp_mount[2957] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:19:00.327 afp_mount[2957] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:20:16.510 afp_mount[2961] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:20:16.511 afp_mount[2961] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:20:17.020 afp_mount[2962] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:20:17.021 afp_mount[2962] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:20:17.696 afp_mount[2963] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:20:17.697 afp_mount[2963] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    Firewall Tool: Apple Firewall is off, but there are 2 rules in IP Firewall!
    2008-01-12 14:21:33.479 afp_mount[2992] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:21:33.480 afp_mount[2992] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:21:33.970 afp_mount[2993] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:21:33.970 afp_mount[2993] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:21:34.981 afp_mount[2994] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:21:34.982 afp_mount[2994] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:22:51.855 afp_mount[2996] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:22:51.856 afp_mount[2996] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:22:53.081 afp_mount[2997] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:22:53.082 afp_mount[2997] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:24:10.171 afp_mount[2999] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:24:10.172 afp_mount[2999] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:24:20.225 afp_mount[3000] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:24:20.226 afp_mount[3000] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:24:20.770 afp_mount[3001] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:24:20.771 afp_mount[3001] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:25:27.615 afp_mount[3003] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:25:27.615 afp_mount[3003] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:25:43.152 afp_mount[3005] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:25:43.153 afp_mount[3005] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:25:44.014 afp_mount[3006] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:25:44.015 afp_mount[3006] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:26:59.681 afp_mount[3013] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:26:59.682 afp_mount[3013] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:27:01.193 afp_mount[3014] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:27:01.193 afp_mount[3014] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:27:01.779 afp_mount[3015] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:27:01.780 afp_mount[3015] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:28:18.577 afp_mount[3017] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:28:18.577 afp_mount[3017] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:28:19.022 afp_mount[3018] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:28:19.023 afp_mount[3018] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:30:02.943 afp_mount[3031] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:30:02.943 afp_mount[3031] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    2008-01-12 14:30:03.175 afp_mount[3032] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x2d03, name = 'com.apple.afp_mount.ServiceProvider'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2008-01-12 14:30:03.176 afp_mount[3032] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.apple.afp_mount.ServiceProvider)
    Jan 12 14:31:33 fcp4s-computer loginwindow[68]: sendQuitEventToApp (qmasterqd): AESendMessage returned error -1712
    Jan 12 14:31:34 fcp4s-computer loginwindow[68]: sendQuitEventToApp (compressord): AESendMessage returned error -1712
    thanks
    rishi

    I do not think this is an xsan issue. DNS or AFP is more suspicious, I think. Do you recognize "Wildlife"? Is it a share or system on your site?

  • AFP Connection Status box shows each time I launch Photoshop

    I am on a 2-computer network and whether I am off the network or on, each time I launch PhotoshopCS the AFP Connection Status box pops up with the message: Looking up "[name's] computer" (the other computer on the network). Why is this appearing and how do I get rid of it? It's the only application this happens in. I'm on a PowerBook G4; the other computer is a G5 tower. Both run OSX 10.4.xx. (When this happens I press Cancel in the dialog box and Photoshop continues to launch.)

    BDAqua, Thanks for trying to help; you're the only person who responded. I have read the two threads you sent, but I'm not seeing the similarities between these issues and mine. I don't think I changed a user short name; I went to the Users folder as suggested in one of the posts and there are three users: me, the other person who's computer I connect to sometimes, and a shared folder. The other thread looks like it has to do with someone who's ON a network and can't see the other computers. That's not my problem.
    Any other suggestions? It only happens when I launch Photoshop, and naturally I have saved something from the other computer to mine in that program, but in lots of others too.

  • LogMeIn Hamachi: AFP Connection Error

    Hi Community,
    I'm currently trying to set up an AFP connection between two computers that are both connected to my Hamachi Server. I have three computers on the free server, the two I need to connect, and the third being my personal computer. Whenever I try to connect the two computers (either way, from computer A to computer B or vice versa), I get the error:
    "The server "x.xx.xxx.xx" may not exist or is unavailable at this time. Check the server name or IP address, then check your network connection, then try again."
    Both computers are returning a ping regularly, so I'm not sure why this is happening. Furthermore, both computers can connect to my personal computer via AFP, but my personal computer can not connect to either of these computers. All three computers are on different networks, so I'm suspecting a network-side firewall issue, but after going about opening ports on the 2wire and Netopia 3000 (the two routers I'm dealing with), I'm still getting the same error. Does anyone know where this error is originating from? Or even better yet how I can fix it? Thank you so much,
    ~Josh

    Hamachi provides a VPN connections between the system, which unless the firewall (and or router) is actually blocking Hamachi, will NEVER see your AFP traffic and ports on the Hamachi network, except as encrypted packets using the Hamachi port(s).
    Hamachi tends to use a 5.x.x.x based IP address.  Have you tried finding the Hamachi assigned IP address for the remote servers and connecting using that?
    Finder -> Go -> Connect to server -> afp://5.x.x.x
    I think Hamachi will distribute Bonjour messages, so in theory you should be able to use a utility such as Bonjour Browser to see if the remote Hamachi system's Bonjour services are visible.

  • 10.3.9 Server slow/Dropping/Refusing AFP connections

    Over the past 48 hours, our 10.3.9 unlimited server has been sporadically dropping or refusing AFP connections, or providing connected users extremely slow service. After a restart it will appear to function normally for a few hours, then continue to act up. There have been no configuration changes recently, all the disks appear healthy, the network traffic is light to moderate, and the CPU usage is low. Does anyone have any suggestions on where to start troubleshooting this?
    -1.25 G4
    -768 MB RAM
    -1000BT ethernet; clients connected via 1000BT switch

    This is mostly a "me too" but I've got similar issues. Our Panther server will suddenly become very slow. Not just file transfers; using remote desktop to attempt a login at the "console" is also slow. Stopping and restarting AFP service clears it up temorarily, as does rebooting the server.
    The coincidence here is that it started happening when we upgraded a lab of Windows 98 boxes to Windows XP. You would think this would only affect SMB service, but it's AFP that gets hit.
    Again, server shows light CPU and Network loads, but transfers perform like I would expect from 10Mb hubs instead of 100/1000Mb switches.
    Was your performance drop just a sudden occurence or did it happen after a significant change somewhere in your network?

  • Time capsule losing AFP connection

    Need technical help.   I was hopeful that the 7.6.1 firmware upgrade would fix but it does not appear to the case.
    On network with several OS X 10.7 computers, the time capsule will lose AFP connection (causing Time Machine to fail) to all computers on the network after a period ranging from a few hours to several days.  When the AFP connection to the disk is lost, the time capsule is still functioning as a air wireless base station and will accept an SMB connection.
    The only cure appears to be to power cycle the time capsule which restarts the AFP capability within the time capsule.
    This is either a fault in the time capsule AFP capability or some network issue that impacts AFP and not SMB.
    Has anyone else suffering similar

    Check this: http://discussions.apple.com/thread.jspa?messageID=8306744&#8306744

  • Max Simultaneous AFP Connections

    Hello,
    This problem may be answered already, but I couldn't find it through a search.
    Current Setup:
    Xserve (slot-load) Dual 1.33Ghz G4 (2MB L3 cache per processor)
    1.5GB RAM
    Mac OS X Server 10.3.9
    connected to Xserve RAID with about 3.5TB of space.
    3700 User Accounts (School District)
    Running only AFP and Open Directory services. Strictly used for file sharing.
    Problem:
    We are having a problem with the AFP connections being very slow (on the client side). Often you will have to wait 30 minutes for the AFP connection to get past authenticating. The problem is a little random, but we think it is narrowed down to when there are around 150 - 200 simultaneous users.
    From what I have read 100 - 150 simultaneous users is about the reasonable limit for Mac OS X Server. During this time the console is also slower then normal. We have increased the threads for the AppleFileService process to 400.
    Here's the question: is that limit due to Mac OS X server, or it is because of hardware. So, if I order a brand new Intel Xserve (whenever they ship) would that increase my limit, or would be the same due to the server software?
    We are upgrading the RAM to 2GB tonight, but I doubt that will fix the problem. Is there anything else we can try? Would upgrading to 10.4 server help?
    Thanks in advance for your time and responses
    Xserve (Slot-Load)   Mac OS X (10.3.9)   Dual 1.33, 1.5GB

    Just to add another user into the fire, i have the same issues, but......
    We have 25 Users, all are running 10.4, and all now have Appletalk turned off, even thought they were only using it for printing.
    IP has always been used to connect to the server, and there were no issues. We've recently upgraded the server to 10.4, and applied the full 10.4.8 update, and we are getting really, really slow response times opening files.
    At the same time the Network department decided to change from a singular VLAN to multi Vlans. Were pretty sure its a network issue, as the xserve is sitting there doing nothing too taxing.
    We've recently forced 100, on both the Macs, and the switched, which are cisco, that also have spanning tree and all oter rubbish turned off.
    Once thing that i have seen on our server is multiply 'Open Fork' messages for the same file that is being opened by each user in the AFP logging.
    I'm running some tests on our own server, which hasn't got the same loading, but i'm looking at the logs today.
    I know this doesn't help you directly, but are you at the same stage as i am, in regards network/VLans, etc, etc??.

  • HP PhotoSmart 7510 suddenly has severe connectivity issues

    I have a HP PhotoSmart 7510 printer since about 2 months. Initial setup worked like a charm and the printer has been working pretty much perfectly for the last 2 months. Wireless printing, scanning and internet access on the printer (e.g. for Facebook photos) all worked. Just from time to time i would get the occasional (mildly annoying) message on my computer saying "scan to computer is currently unavailable" but it usually worked itself out and whenever I needed it to work, it did work.
    But since a few days ago, it has some severe connectivity issues. I didn't change any settings on the printer, router or computer - the issues just started appearing by themselves. I startet getting much more frequent messages on my computer saying "scan to computer is currently unavailable". I noticed I couldn't print anymore, and restarting computer, printer and/or router didn't help at all. The only thing so far i managed to print wirelessly since the problems started were the first 5 pixel rows of an image I tried to print, the rest didn't transmit.
    It seems the printer still connects to the WLAN but printing and scanning no longer work, and whenever I try to access a web service on the printer (like Facebook) it says it has no internet connection, even though the WLAN light is lit up (not blinking) and all the wireless status reports say "congratulations, no problems found" and display IPs etc. just like normal.
    I looked at the threads "PhotoSmart 7510 connects to router, but not to the web.", "Wireless printer (HP Photosmart 7510) not connecting to network" and "Photosmart 7510 won't connect to Web Services" but they weren't a big help. Activating EWS didn't work because even though the printer showed its IP address to be 192.168.1.3, when I entered this in my web browser it didn't find the printers configuration page.
    I tried the following steps from one of the threads:
    1. Restore the Network defaults
    2. Unplug the printers power cord while it is still on. Leave it unplugged and walk to the router.
    3. While the router is still on, unplug the power cord from the router, leave it unplugged for 30 seconds, then reconnect the power cord to the router. Once plugged back in the router should power on automatically.
    4. Plug the power cord back into the printer. Once plugged back in the printer should power on automatically.
    5. Run the Wireless Setup Wizard to reconnect the printer to your wireless network.
    6. Try enabling Web Services.
    I followed these steps exactly. Interestingly, even though I had done step 1 and restored the network settings to factory defaults, after turning back on, the printer somehow still had its old settings saved and reconnected to the network.
    It seemed to have fixed the problem, the printer finally had internet access again (Facebook app showed my photos) and scan to computer found my PC. But after just about 3 minutes, the printer had lost its internet connectivity again. When opening the Facebook app, it displayed the same error message it did before. And printing no longer worked as well.
    So, what is wrong with this printer?! It has the newest software update by the way (I checked during the 3 minutes it had internet access.) My computer is a HP Windows 7 x64 machine (EliteBook 6930p) and the router I'm using is a Netgear WNDR3700.
    I specifically bought this printer for my studies at university. In one week i have my exams and in order to study I REALLY need to be able to print some of my course materials! So any help as quickly as possible would be greatly appreciated. Or do you think this is a case for a warranty replacement, considering the printer's really strange and error-prone behavior?
    Thanks a lot!

    I can assure you that it is not a router issue.  It appears to me that it is a driver compatibility with Windows OS.  After trying to get to the bottom of this since my Photosmart 7525 was new and reading just about every forum and blog, I have come to the conclusion that the issue must be related to the HP driver itself.  
    The issue does not seem to affect any Mac systems, and from one forum someone was able to fix it by downloading new drivers compatible with 64-bit systems (which seem to not be affected by the glitch).  But that leaves us 32-bit people stuck with the current driver which does not work.
    The printer is connected with good signal to the wireless router (no matter who's router it is and what configuration is made).  The printer can be pinged from the router and any computer on the network which is not currently being affected by this issue.  However, the affected computer fails pings by either request timed out, or destination host unreachable.  Pings are successful from the affected computer to any other device on the network.  The only way to recover (at least for a few days) is to reboot the affected computer.
    Also, from the display on the 7525, the network tests pass without issue.  I can also download and print content from the internet with no issues.  
    Please do a quick google search of this issue and you will see several THOUSAND entries of people with the same request.  This is a serious issue that people are having and everything is pointing to an HP problem (not routers, improper installation of software or drivers, etc...).  I agree with several other customers that HP should be on the hook for this fix.  I will give it another couple weeks, then back to the store for a reliable unit from another competitor (Canon, Lexmark, etc..)
    Thank you in advance for escalating this issue to product engineering,
    S. Hunn
    There are 10 kinds of people in this world... Those who understand binary and those who do not.

  • Connection doctor and connection issues

    I have nothing blocking  my internet connection, however mail is a nightmare for me. I continually receive connection issues via the connection doctor for imaps, pops, and icloud.
    Are my settings wrong? I have checked with each of the settings and they are set per instructions provided. Some are google, some yahoo, icloud, etc.
    This is really annoying and I could really use some help.
    Here is a typical message: Could not connect to this Google IMAP server. Check your network connection and that you entered the correct information in the Account preferences. Also verify that the server supports SSL. If it does not, deselect the 'Use SSL" checkbox in the Advanced tab of Account Preference"
    I have done all of this and am still having troubles.
    I am also receiving SMTP connection issues - "Trying to log into this SMTP account failed. Verufy that the username and password are correct."
    I have checked and all are correct. Even more confusing, these issues are not present all the time - however I have not changed anything between when times are good and bad.
    Sigh - I hope someone has an idea to help me out.
    Thanks in advance for your time and thoughts.
    Patti
    I am running osx 10.8 mail 6.2 and use xfinity for my internet (as I mentioned, I disabled their firewall trying to fix this)

    Hi there Japps1,
    You may find the troubleshooting steps in the article below helpful.
    OS X Mail: Troubleshooting sending and receiving email messages
    http://support.apple.com/kb/TS3276
    -Griff W.

  • Excel ODBC Connection Issues

    I'm having some issues importing external data from an Oracle 9i database.
    Here is what is happening:
    I am initially able to import data from the table I want to into Excel.
    I do this through "Data -> Import External Data -> New Database Query" where I have my .ORA data source. I'm able to log in using my user and password and import the table. My problems come after I import this first set of data.
    If I try to "Edit Query…" I get an error box that says "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
    If I try to "Refresh Data" I get two error boxes. The first is just: "[Microsoft][ODBC driver for Oracle][Oracle]" and the next says: "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed". It then prompts me for the User name and password of the DB I'm connecting and after I enter the information, I get the same two error messages.
    Also, if I attempt to establish another connection following the "Data -> Import External Data…" steps I run into a different problem. Upon entering the information for the User Name and password prompt I get two error messages. One says "!" and the next box says "Couldn't read this file". Once I click "OK" in those boxes, the Microsoft Query window automatically opens with nothing in it.
    I can't seem to figure out why I can initially pull down data and then cannot succeed afterwards. I'm unable to connect to the DB I have through Excel until I completely closed all Microsoft Excel instances.
    I also use this data source in Microsoft Access without any problems.
    My Excel version is 2003.
    I'm using Oracle Drivers I'm using are from an "Instant Client" package.
    Any thoughts why I'm having these connections issues?
    Thanks in advance.

    This issue is closed.
    The solution was:
    "Data -> Import External Data -> Import Data"
    Select "New Source" and select the "Oracle" data source and filled in the appropriate information. This was similar to the database query but it actually works.

  • My brand new mac pro always had Internet connection issues at school. WHY is that? I see the school's Internet working perfectly fine on other PC's, but there is never a day where my mac doesn't have Internet connection issues at school. How do I fix it?

    I got my mac pro in the middle of August. School started the week after. Internet was working perfectly fine at home. But at school, I never had a good connection. Sometimes on the good days I get a connection when I'm sitting at the exact spot in class I always sit at. It's ridiculous and it's frustrating. I invested my money into this laptop and I'm beginning to regret it. I thought it was the school's Internet, but I don't see Internet issues with other PC users. It's most frustrating on registration days and I'm trying to register for my classes before it gets taken, but again... Internet connection issues. It's random. Majority of the time, it doesn't work at all. I've done Network Diagnosis and turning WiFi off then turning it on again. I've done everything I could. I put my money on this laptop and it was a lot of money. I could have bought an 800 dollars laptop and I would have Internet connection anywhere on campus. So, I don't want to continue everyday to regret on buying this laptop every time I try to connect to the Internet at school or Starbucks or anywhere else. How do I fix this? What's the problem ?
    At school, I heard this guy had a problem with Internet connections too and he owned a new mac book pro. He said something like Apple messed up on something, but he fixed it. If I knew mac book pro's had these issues I wouldn't have bought it in the first place. It's freezing on me every other day. It's ridiculous. But what concerns me the most is the Internet connection. So someone please tell me what can I do next to prevent the problem? Am I doing something wrong maybe?

    Hi Kevin,
    I'm using an XLR input mic which is connected to the phantom power enabled XLR mic socket on a USB M-Audio M-Track. The M-Track is connected by USB to the Mac Pro - so effectively I've got an M-Audio USB soundcard with a mic input.  I've also tried a microphone that is a straight XLR to USB cable (guessing with some soundcard chip buried in the usb plug) but that also yields the same effect of bad latency, intermittent quality, stuttering and repeating and echoing (without the speakers on during record so its not feedback).
    The mic works absolutely fine with other recording applications I have on the mac at the moment - albeit non-adobe ones (tested it on the EasyAudioRecorder - and it lives up to its name. it's easy)
    I will try with Audition and report back, but sitting here right now I can imagine it would work fine with audition too - it just seems to be the way premiere is set up for recording into the timeline is a bit sketchy.  I'm willing to accept it might well be a quirk with the new Mac Pro trashcan - I'm not weighting all the woes on premiere.
    Any thoughts or am I out of luck to sit with my fingers crossed for a fix in the next round of updates?
    Nathan.

  • Connection issues with Safari 3

    I'm having some connection issues with Safari 3.
    When I connect wirelessly, Safari won't load any web pages. I go and use Firefox and everything is just peachy.
    I've reset Safari, emptied the cache and whatnot. I went in and checked the permissions, everything checks out.
    When I connect with Ethernet, there's nothing wrong, which is my dilemma.
    Help would be greatly appreciated.

    There are a number of posts in the Leopard forum from people with direct experience with upgrading from Panther to Leopard. Here is a relevant thread from there that should reassure you.:
    http://discussions.apple.com/thread.jspa?threadID=1418714
    Your system should be fine for Leopard, but you will probably need a current version of Photoshop if you don't already have it. See this download:
    http://www.adobe.com/support/products/pdfs/leopardsupport.pdf
    Also, Leopard doesn't run Classic (OS 9) apps.
    One caveat - first make a bootable backup "clone" of your present system onto an external firewire drive so you can recover if anything goes wrong. You can use the "Restore" tab of Disk Utility to make such a clone, and there are also Panther-compatible versions of Carbon Copy Cloner (v 2.3) and SuperDuper (v 2.1.4), both excellent for this.
    It's even possible to a create second Panther clone on a different external volume to create a "dual-boot" system, using that volume to continue to run old applications that you can't run with Leopard.

  • Connection issues with EA4500

    I had bad connection issues with my mobile device, so i pressed reset on my EA4500 router, and now when i connect to my network, it gives my limited connection even though i have 5 bars of signal. Not sure what to do now...

    Resetting the router will erase all the settings you configured on the router since the initial setup. You manually configure the router's wireless settings so your wireless devices can have internet access again.
    Procedure: http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=cfb50c0dc992443ab2405a782cca60f7_19073.xml&pid=80&...
    Make sure to use a computer that is hardwired via Ethernet cable to the router.
    For bad connection issues: http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=cf6ed888ce144d06905af4987887fd1b_KBxxxx_EN_v1.xml&...

  • X1 Carbon (20AX series) wifi connectivity issues

    Dear Lenovo Support and all others,
    I am posting this in hope that someone can help with my problem and also to share my unpleasant experience with a new Lenovo product.
    Lenovo Thinkpad X1 Carbon
    Model: 20A8A00VSG
    OS: Windows 7 Pro 64bit
    Purchase date: 27th February 2014
    Since the first day I purchased the system, I have been having an issue with my wireless connection:
    1. I am unable to reliably get a wireless connection to wireless access points (e.g. free wifi coffee outlets or malls) and personal mobile hotspots (mobile phone hotspots). It constantly says "LIMITED CONNECTIVITY". In other words, I cannot get internet access. Even when it does connect to the network and get internet access, there is a tendency for the connection to drop back to "LIMITED CONNECTIVITY".
    The only time I can get a reliable connection is when I am connected to my home wireless router. The system does not seem to have problems on home wifi networks. Since the problem seems limited to wireless access points and hotspots, I believe its a hardware/software problem.
    Please note that I have other  wireless devices (laptops and mobile phones) that can connect to the same networks that I am trying to connect to and have no issues.
    I have tested the networks with my friends' wireless devices as well and they have no issues accessing the internet so I am fairly certain that there is no issue with the networks themselves.
    2. I have already called in twice and been given advice on both occasions but the problem still persist. I have updated all drivers, uninstalled and reinstalled and updated the BIOS for the system and also performed a system recovery but nothing has worked so far.
    I have also tried disabling and/or deleting any anti-virus software and firewalls but it does not fix the problem.
    I have also been advised that I need to go down to the Lenovo service center to have my laptop checked out by the technicians and that there MIGHT be a firmware upgrade for the wireless card itself.
    NOTE: MIGHT? The support staff doesn't even know for sure whether there is an upgrade available.
    3. Rebooting my computer, the wireless card or the hotspots does not solve the problem. It might work for a shortwhile before it reverts back to it's non working state or stops working again once I reboot the system.
    I am really unhappy with the purchase so far. It's actually a good laptop per se when all is working, but without internet access, it is pretty much like a dead fish. And thats 90% of the time.
    Like I said, this problem has been happening since day one and I've tolerated it long enough.
    I hope someone can help me with this problem.
    Thanks all.
    UPDATE - 3/24/2014
    I borrowed an ASUS Wireless USB adapter from a friend and installed it on the laptop. Lo and behold there are no connectivity issues to my iPhone wireless hotspot.
    INTEL DUAL BAND WIRELESS AC 7260 - NO CONNECTION/LIMITED ACCESS
    ASUS USB N10 WIRELESS ADAPTOR - CONNECTIVITY AND INTERNET ACCESS
    I think this narrows it down to the software/hardware in the computer....

    Hi, all
    there is an issue bugged driver or even card firmware related. Intel confirmed that. Wait some time for the new release.
    For the test purpose only disable 2,4 ghz band support and switch to 5 ghz. N-band seems unstable so switch to G-band. As the Linux users report the same issue it's firmware bug basically.
    x220 | i5-2520m | Intel ssd 320 series | Gobi 2000 3G GPS | WiFi
    x220 | i5-2520m | hdd 320 | Intel msata ssd 310 series | 3G GPS | WiFi
    Do it well, worse becomes itself
    Русскоязычное Сообщество   English Community   Deutsche Community   Comunidad en Español

  • Macbook air Mini DisplayPort to VGA Adapter connectivity issues

    Hi pple,
    Would like to ask if anyone is facing connectivity issues with Mini DisplayPort to VGA?
    I am currently using the 2nd Gen Macbook Air with Intel HD Graphics 3000 384 MB. Sometimes when I connect to a montior (Viewsonic VA1918wm) it works fine, sometimes it just does not work and the laptop just shows me a blue screen.
    I tried with out with my friend's Mini DisplayPort to VGA adapter, it has the same problem. Does this means that my macbook air mini disoaly port got a problem?
    Thanks
    Bryan

    I am experiencing the same kind of problem... only with projectors. Some projectors will display the screen and then others wont even register with the MacBook Air.
    Using an Apple Min Displayport to VGA adapter. It's hit or miss if it works. Firmware has been updated on the adapter but this did not help.
    Anyone help with this?
    Thanks,
    Nathan.

Maybe you are looking for