ISight, viewing over network problem....

I am trying out a piece of software called "On Air" by Equinox which allows one to view all iSight/Webcam cameras attached to your network. The software is installed on my MacBook (which of course has a built in iSight). I have another iSight attached to my iMac. Supposedly, if your computers are networked together, you can see all cameras attached to the network. I realize that probably no one here will know of this software...however, how does one assure that their iSight is attached and working through their network? Both iSights work perfect independently through iChat. Thanks.

HI Terry,
Believe you were in control of multi video sources, from Web and DV cams to IP cameras and the iSight, which you could view, record and publish with a click of a button. Well, On Air does all this and more!
This implies the other cameras have to be IP cameras. I.E. They are broadcasting that they are there.
The page about the network cams does not seem to make it any clearer.
The Support page might as well say "send your info anywhere but here as there is no-one at this desk even though the phone is red"
This would imply other software that iChat to make a cameras appear on line. (local net)
Just my first slant on it.
8:19 PM Friday; June 9, 2006

Similar Messages

File Transfer Over Network Problem since 10.4.9 Update

Since the update I've had this problem. Here's a typical operation:
In a finder window, from my PowerMac G5, I click on Network and mount a disk from another Mac on the Network (Intel Mac Mini). I navigate to that mounted disk and drag a 1.5GB file from it to a directory on my G5.
This used to take a couple of minutes before the update. Now it takes over 4 hours! My network looks like this:
Intel mac Mini (10.4.9) hard-wired to new Airport Extreme 802.11n
PowerMac G5 (10.4.9) hard-wired to new Airport Extreme 802.11n
Pwerbook (10.4.8) Wi-Fied to new Airport Extreme 802.11n
I don't understand why this is happening or how to correct this problem. Any help would be greatly appreciated since I do this operation frequently and 4+ hours is totally unacceptable.
Thanks!
G5 2.5gHz PowerMac, Mac Mini Core Duo, G3 400mHz Powerbook Mac OS X (10.4.9)

I found out that about the same time as the update one of my five external hard drives started going south on me. When it got to the point of no return where it wouldn't mount any more I took it off the Mac. The network is running fast and fine now. For some reason the drive was slowing everything up. Weird.

CS4 "Already in use cannot delete" over network problem

Hello,
I am having a problem with a Mac on OS X not being able to open or delete any .ai files over a network on a Dell Server running Windows Server 2008. If we try to open or delete the file I get an error message "Already in use cannot delete". Also, I get a "cannot complete copy" error too. Whats weird is that both machines can see each other over the network and the Mac can read and write to all other files over the network. The server does not have anything adobe products installed at all. There is no other machine on the network that is causing these files to be in use. I have checked when the backups are done using Windows Server 2008 Backup and they are finished before anyone gets into the office, so I dont believe its the Backup program holding the files hostage. I have read in some areas that this may be a known flaw with NTFS formatting over a network, but im not sold on that idea yet.
Any and all suggestions would be as useful to me as insulin right about now.

Sorry one last thing. I can delete the files on the Server itself.

Media Managing over network problems

I am encountering a problem with FCP6 of when I try to media manage a project to network drive, I frequently get an error that there is not enough drive space when there is plenty, eg I am copying about 6 Gigs at a time to drives that have more than 1 TB free!! It happens on random clips, you can just select skip clip and it will keep copying some more then will just stop again with the same error. Copying via finder works but not within FCP. Any one got answers? Thanks!

Drives formated to macos extended. Files are genereally under 2gig. I get the problem when moving a whole project or when consolidating a sequence with no handles. The way around it atm is to Media manage to a local drive and then copy it over using finder.

Sharing external drive over network - problem

Hey guys,
I searched the forum, but nothing posted to other threads helped.
I want to share a LaCie external USB drive over my network. It consists of two macs: a mac mini and a macbook running OSX 10.4.9.
The external drive is formated in FAT32. I enabled sharing in the system pref. but I don't see it when trying to connect. I installed SharePoints and shared it from there, still nothing. I tried connecting using the "afp://..:" stuff, but I get an error message, saying I cannot connect.
Got some ideas?

Thanks for your reply
Did you use the little "Show File System Attributes" yet?
Yep, it's r&w
Did you use the enable Windows(smb)Sharing to Shared?
Yes
Did you add Users yet?
Yes, my username which i use to connect is added.

Sharing over network problems

hey everyone, trying to share all my music, movies, photos over a network from my imacC2D (running tiger) with my new mpb. I can only see the mbp's hard drive over the network and NOT the imac's which is where all the goods are at. here's what i did:
personal file sharing is enabled on both computers.
i click on Go > Connect to server > Browse, and from here is where it gets grey... I only see the mbp's harddrive (server) and not the imacs. What do i need to do on the imac in order to get its contents off it? I guess i could always use migration assistant but i dont have a firewire cable and im too lazy to go get one : P

WOW I GOT IT!

Problems with open an Indesign-Document over Network

Hallo,
we have a specialized problem with opening indesign-documents over network. Our users works with windows-pc (windows7) and adobe CS5 and CS6 and they will use there documents which are on our macserver 4.0 which works on OS X 10.10.2.
Sometimes the usurers become this Message
Wouldn't work indesign proberly on windows with documents which are on a macserver?
Please help me.
best regards
chris mueller

@Naga Sai J – you cannot open an InDesign CS4 file in the previous version.
But you can export an exchange file format for InDesign CS3.
Go to File/Export and chose INX for export: "InDesign CS3 Interchange-Format (INX)"
That .inx file could be opened with InDesign CS3.
After opening the .inx file, examine it well!
Some things might have changed (things regarding to newer or changed features from InDesign CS4).
Uwe

Can't scan over network with a laserjet 1217 on a Mac

Hi
My set up:
Mac with Yosemite
Laserjet M1217 over wireless
Problem description:
I can't scan. From preview, or the control panel, or image capture, I get the same error saying "can't open a session"
I have installed and re-installed the drivers/printer around 100 times.
I have tried adding the printer/scanner as airprint, or with the name of the printer as a post suggested.
Everything result in the same error.
I have version 2.0 of the driver installed right now. Tried with 1.7 as well, same result.
I can print without a problem from my Mac and from my iPad.
Tried with an ethernet cable and have teh same issue in case someone ask.
I've looked everywhere in google and doesn't seem like anyone else have the same issue? Many people have issues printing over wireless, but that's ok for me. Is the scanning I can't get to work.
HP pages doesn't offer any different driver than what Yosemite has. HP doesn't offer any extra program for Mac and scan.
Don't know what else to try.
Some help? Anyone?
This question was solved.
View Solution.

Hi @juancgallardo ,
I see that you are experiencing issues scanning over the wireless network and hardwired network on Yosemite.
I would like to help you out with this issue today.
The drivers for Yosemite are installed by the Apple Updates.
Installing Your HP Printer Driver and Software for Mac OS X.
Did you add the printer as a Bonjour printer or IP Protocal?
IP Protocal won't allow you to scan, just print.
You can also download and install the HP Printer Drivers v3.0 for OS X.
If you are still having issues then check that the scanning ports on the router to make sure that they are open. You can contact the router company to check and open these ports 9220/9500/427 on the router.
If you still can't scan, connect the printer directly to the Mac with a USB cable and see if you can scan. Just to rule out a network issue.
What kind of router do you have?
Please provide in detail the results if you are still having issues.
Have a nice day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

WVC80N - Internet Gateway UPnP discovery failure message \ unable to view over the internet

I have the WVC80N. I recently got the new Comcast modem \ wifi but the Wifi is junk and had a lot of problems (loss connection, range etc) so I had Comcast "bridge" it so I just use my old wifi (LinkSys E1200). I have TZO to handle remote viewing. Everything was working great for about two weeks and we had a power outage. Since then, I have been getting UPnP discovery message (in the status tab of the WVC80N camera site) and I am unable to view over the internet. I get a 502 error usually but today I got extra info: "The socket connection to www.dfgehring.mylinksyscam.com failed.
ErrorCode: 10060. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."
I had Comcast do a "repair / reset" transmission to the modem and still get the problem.
I found these step on the forum:
1. Home Wirless Rounter administration page, find the UnPn settings and Turn off UnPn and save it. Wait for atleast 30 sec and go the same page and Turn it back on.
2. On your wireless camera Adminstraion page, go to "Options" and find the UnPn if it is already disabled go ahead and "enable" it also "enable" the "Alternate web connection" and save it. If it was already enable please disable it save the settings and enable back on.
The above 2 steps resolved my issue and I could able to view my camera from outside of my home network.
Still no luck. Tried it several times.
Could the power outage reset something on the modem or router to change this?
Thanks
Darren

That's what I thought. The power outage may have set the modem, router or camera settings back to factory defaults causing it to loose connection. First thing first, call comcast and check if the modem is still on bridge mode. The modem may have been set back to a modem/router mode due to power outage.
You may test if the remote access is properly set up in the network by going to http://ping.eu. In that site, you will see your internet ip address, take note of that. Click on port check, enter your internet ip address and the port number you used in the alternate web access port then click Go. If it says closed, there something wrong in the settings of either the router or camera. In that case, I suggest you reset the router and camera and then reconfigure them.
I found these articles online which could help you reconfigure your router and camera settings:
How to set up your router
How to set up router wireless setting
Connecting camera to wireless network
How to set up remote access on linksys camera
How to set up TZO on the linksys camera
Hope these helps.

Time Machine and Time Capsule - Failing with Network Problem

My problems with TM/TC have been ongoing for a couple of months now and I am going round in circles - need help.
This is the second post I have made, the first got lost in people suggesting the obvious - so I will try to be a little more specific if I can.
I will detail the current state first - i.e. where I am now - after I will list what I have done so far to get to this point.
Currently, my iMac (intel) is directly connected by Ethernet 1GB to the Time Capsule. The TC is then connected to a Netgear router which in turn is connected to Internet.
I have no network problems at all - internet connection is fine. the Netgear Router has the latest firmware version and is working fine. The porblems i have are nothing to do with this.
The time Capsule is in Bridge mode and getting a reserved dhcp IP address from the Netgear router.
The Time Capsule has been fully reset - i.e. power cable out, hold the reset button, plug in power cable (spark, spark), hold reset button, fast blink for 20 seconds or so, light goes out, release button.
I have re-applied the latest Time Capsule firmware.
I have renamed the disk on the Time Capsule.
I have renamed my iMac and deleted all the time capsule entries from Keychain.
I have re-installed Mac OSX and re-updated to the latest 10.5.6 release.
At the moment I have kicked off a backup with a lot of large files - like music folder, video folder etc excluded. I also have parallels and have excluded the disk image. I have 1 other 50GB disk image which is also excluded.
I am expecting the first initial backup will complete successfully.
I will then remove music and video from exclusions and allow them to backup. I am expecting this will complete no problem. (I do this because the upcoming problem will happen if I move away from the machine - and I dont want to sit there for 2 days).
So up to this point TM and TC have performed flawlessly. The issue that follows started happening before the 10.5.6 update after backing up with no issues for months. At this point I will be able to use TM to browse the backup and restore files. I will be able to mount the sparse bundle and browse files. Spotlight reports no issues and indexes quickly.
If I leave my machine after a successful backup and the hourly update kicks in it will fail with 'A Network problem' basically saying the backup has filed because of a network problem, but is not any more specific, logs show far too much to put the whole thing here, but the following is an excerpt
Dec 23 05:19:49 MickMac /System/Library/CoreServices/backupd[1499]: Backup destination mounted at path: /Volumes/Backup
Dec 23 05:19:50 MickMac hdiejectd[1519]: running
Dec 23 05:19:51 MickMac kernel[0]: jnl: disk1s2: replay_journal: from: 28864512 to: 30084096 (joffset 0x1d0f000)
Dec 23 05:21:49 MickMac kernel[0]: jnl: disk1s2: journal replay done.
Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Disk image /Volumes/Backup/MickMac_001ec215ce76.sparsebundle mounted at: /Volumes/Backup of MickMac
Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
Dec 23 05:21:49 MickMac com.apple.launchd[1] (com.apple.netauth.sysagent[1500]): Stray process with PGID equal to this dead job: PID 1503 PPID 1 check_afp
Dec 23 05:21:55 MickMac fseventsd[38]: event logs in /Volumes/Backup of MickMac/.fseventsd out of sync with volume. destroying old logs. (3627 125 5482)
Dec 23 05:27:33 MickMac /usr/sbin/ocspd[1539]: starting
Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 5 reqID 5400 flags 0x9 afpCmd 34 so 0x7e78cc0
Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x7e78cc0
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot -1 error 89 reqID 1 flags 0x9 afpCmd 0 so 0x7e78cc0
Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d00000a', dead
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Open Session failed 57 /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: max reconnect time reached 60 > 30 /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEAType IO] [ErrNo 5] [IOType Read] [PBlkNum 1248] [LBlkNum 155] [FSLogMsgID 501572642] [FSLogMsgOrder First]
Dec 23 05:31:26 MickMac kernel[0]:
Dec 23 05:31:26 MickMac fseventsd[38]: failed to unlink old log file /Volumes/Backup of MickMac/.fseventsd/0000000000ccb02b (Input/output error)
Dec 23 05:31:26 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED)."
It goes on and on and is repeated every hour. For each one I get an error message on screen saying backup failed due to a network error. However I have tried a manual download over the same period set at an extremely slow rate so that it was downloading during this time and it showed no errors. I.e. the network connection from imac, through TC to netgear and out to internet - and monitored this while time machine showed these errors (i.e. at the same time) and this showed no connection problems at all and completed succesfully.
I know TM uses an internal address to do backups, but uses the same cable and network card to get the job done. I am simply removing the cable as a source of issue although I have also replaced this making no difference.
Applecare are involved and have so far been sent 2 sets of logs and so far have not been able to find the cause. New TC is on its way to try that, although they think it is something on the imac that is causing this.
Sleep mode is turned off although screen sleep is on. The tick is not in the box for putting hard drives to sleep whenever possible.
Now, after this has happened, and back at the machine. I restart both imac and TC. Try running a backup, spotlight starts to re-index - i.e. will mount the backup volume and start the index process, gets to about 90% then fails - again excerpts from log
"Dec 23 09:18:50 MickMac /System/Library/CoreServices/backupd[161]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
Dec 23 09:18:50 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/li ve.0.; needs recovery
Dec 23 09:18:57 MickMac com.apple.launchd[67] (com.apple.netauth.useragent[147]): Stray process with PGID equal to this dead job: PID 152 PPID 1 check_afp
Dec 23 09:19:48 MickMac mds[32]: (Error) Server: machmsgdispatch: (ipc/send) invalid destination port [msgh_id 14016]
Dec 23 09:29:35 MickMac /usr/sbin/ocspd[197]: starting
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 11 reqID 3204 flags 0x9 afpCmd 60 so 0x8051b28
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 12 reqID 3205 flags 0x9 afpCmd 34 so 0x8051b28
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x8051b28
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 11 error 35 reqID 3204 flags 0x19 afpCmd 60 so 0x8051b28
Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 12 error 35 reqID 3205 flags 0x19 afpCmd 34 so 0x8051b28"
And later....
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: hfs_clonefile: cluster_read failed - 5
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d000005', dead
Dec 23 09:45:49 MickMac kernel[0]: HFS resolvelink: can't find iNode791959
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]: ore-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431/store.db] [FSLogMsgID 1580919258] [FSLogMsgOrder Last]
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 found 1 filesystem(s) with problem(s)
Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: dojnlio: strategy err 0x5
Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 49664 bytes to the journal!
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexSDB in dbcheckdatastore:store.db : dbgetdatastore: ERR: could not read 4096 bytes
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoSync:write err: 5
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in adddirtychunk:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : ERR: Can't write DST header (Input/output error)
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in dbflushdatastore:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : dbsyncdatastore: write-errors flushing cache/writing map.
Am I the only one having these problems? any help from anybody please...

Got the same problem with a 3 months old TC.
The replacement TC, does it work now flawless?

I try signing into iMessage and it takes about 45-50 seconds to do. When that happens it tells me there is a network problem. I am positive I don't have a network problem and I need help on this problem please??

I try to sign in and it just takes forever to do I try and try and do it over and over and it brings me the same results. Created a new Apple ID and when I did it still tells me there is a network problem. But the thing is I am still able to use the Internet I need help?? And it does the exact same thing for FaceTime so I don't know what to do??

Error -3259 is a network timeout error, usually. This article might help:
http://support.apple.com/kb/TS2799

Screen Sharing/network problem seems confined to 1 volume. What's the fix?

I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
(Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

CORRECTION #2:
Ignore the previous "CORRECTION" post.
Oops, excuse me, I wrote that sentence correctly the first time.
I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

Time Machine couldn't complete the backup due to a network problem

Firstly apologies for the long post, I've been bottling these problems up and could now use some expert advice.
I have a MacPro (10.6.3) with four internal drives (320GB system/apps. + 3x 750GB data, images etc) and a MacBook Pro (10.6.6) with a 320GB internal. With so much accumulated data (Mac user since SE FDHD) I wanted a reliable means to backup all my projects, books, papers, research, images etc. I had several bad experiences using Iomega drives (Ultramax and Storcentre) which were not very Mac compatible and shifted over to a 10TB LaCie 5Big Network 2 which is promoted as Time Machine compatible. Set up Time Machine (with a few hiccups) in Sept 2010 and it ran perfectly, backing up both main computers until March 2011. I have now experienced a string of problems backing up the MacPro, some of which have been resolved speaking to people, some by checking forums and some by using my own noddle to figure it out. The latest error message I am getting is "Time Machine couldn't complete the backup due to a network problem. Make sure your computer and the backup disc are on the same network, and that the backup disc is turned on. Then try again to back up."
The circumstances of this are as follows: TM seems to be trying to completely back up everything already backed up from previous months so I am using the "exclude" option to do this in manageable chunks (5.54TB of 7.99TB is available so there is a lot of stuff on there, hence my reticence to erase and start again). I started a backup last night which said it was 242GB and when I came back hours later (I estimate 30GB and hour or 500MB a minute) it has failed with the error message above. I asked it to back up again and it said it now had 191GB to backup, at the next failure it was 142GB, dropping by approx 50GB a time (if there a maximum it can manage in one go?), the next time it was starting again with 242GB.
I checked the disc it was backing up to, discovered it was now selecting Public-1, re-selected Public which houses the macpro.sparsebundle, dropped the backup size (Options) to 73GB and set it off again and it is backing up as I write. I am hoping it will complete and permit another chunk to be backup but the fact it looses network connection (seemingly) or has a maximum backup in one go, is annoying because it means you cannot leave it overnight and trust it to do the backups.
The other problem seems to be a shut down by LaCie 5Big because several times (and once this morning) I have had this message "The file server "LaCie 5Big" has closed down, followed by a complete Lacie shut down and auto-reboot with all lights and whistles. Lacie think this could be a power supply problem and say they are sending me another power brick. They also say they do not support Time Machine (they should check their own literature) and suggest I use LaCie 5Big for 'drag and drop' backup. If I wanted to do that I could pick up a cheap and nasty HD from PCWorld, not this high end 10TB drive which cost over £1,000 !
For a while y'day I could not even find the Lacie on the network but after changing the ethernet cable from Lacie to router (Linksys) it miraculously re-appeared so that problem may have been the original Lacie blue ethernet cable had developed a fault. Checking cables is an oft-overlooked option.
A catalogue of errors, some solved, others still all pervading, so any words from the wise would be gratefully accepted.

I verified the macpro.sparsebundle and Time Machine backups in Disk Utility and it said both appeared to be Okay in green type. So that did not solve the issue. I did a Disk Utility repair a day or so again (despite Verify saying everything was fine) and said there was nothing to repair. I suspect two problems, the power brick may be faulty producing intermittent power and maybe causing the drive to close down (hopefully Lacie will send me a replacement to try) and second, I am thinking the network connection is getting dropped causing crashed backups without the Lacie shutdown/reboot sequence. The 73GB back up failed, I started it again at 54GB and it failed again, just started it again at 45GB - this is no way to progress!
Perhaps the relatively new (last year) Linksys router is the problem, I find my MBP says AirPort is active but it fails to appear in Go>Server unless I switch it off and on again and perhaps a similar problem drops the connnection to the Lacie.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

Accessing shared files over network

I am having some problems with a couple of database files that I access with a Java program over network. Different computers running this program all need access to these files, and my question is if anyone know of a good way to make sure that only one user have access to these files at the time. There is no server software running were the files are stored, they are simply reached through file sharing. Currently I am creating a lock file indicating that someone is editing the files, however if I am unlucky 2 users create that lockfile at the same time and then both get access to the file corrupting it. Anyone experienced this and know of a nice solution to avoid it?

I am having some problems with a couple of database
files that I access with a Java program over network.
Different computers running this program all need
access to these files, and my question is if anyone
know of a good way to make sure that only one user
have access to these files at the time.Use a database server instead.

ISight, viewing over network problem....

Similar Messages

Maybe you are looking for