IChat over slow network

Hello,
I'm not really good with network stuff, so I know very little about my problem here. I'm working on an offshore drilling rig and they've recently set up a wi-fi system for personal use. It's very slow and governed by the nanny Websense.
I know some people are able to use their IM chats and I was wondering if there is a way to set up my iChat to work on such a slow network. It won't connect at all when I'm here. I know I won't be able to video or audio chat, but I should at least be able to text chat, shouldn't I? Or is it possible that Websense has blocked certain IM's and not others?
Any suggestions would be appreciated!
Lawrence

Hi,
In iChat go to the Preferences > Account section
GO to the Server Settings tab
Whilst logged off of AIM chnage the port to 443
Log in to AIM.
This is because the regular Login port is 5190.
The AIM Application on a PC or in fact the AIM for Mac application will automatically try other ports including the web browsing port (80) to make a connection.
The port 5190 is above a Threshold of 1024 where ports have to be opened specifically. Using port 443 is below this and also used fro Secure Mail by mail applications so is likely to be open.
6:55 PM Saturday; December 15, 2007

Similar Messages

Problem with iChat over wireless network

iChat with AIM account has always worked fine, but from the moment I installed a netgear router over a wireless network it enters a loop of disconnection/connection until I get the message "you have been connecting and disconneting too frequently". Someone else ? What to do ?

Can you marked this thread as Finished then please ?
10:35 PM Sunday; January 25, 2009

IChat over Uni network

I use my laptop the most over my university wireless network. Now, I have seen plenty of people using MSN Messenger etc. on their own laptops and on the same network but I can not get iChat or Mac Messenger to connect. The only think that does connect for me is Skype.
Can anyone suggest how to overcome this?

You should be able to get iChat to at least login if you go to iChat > Preferences > Accounts > Server Settings and change the port to 443
MSN and Skype try other ports below the 1024 threshold (where ports above need to be open)
Changing the port in iChat should get you to at least Text chat.
As the A/V ports iChat uses can not be changed it is unlikely you can Video or Audio chat without getting the IT guys to open the ports.
5:49 PM Saturday; May 24, 2008

Outlook 2010 performance much slower than 2007 and 2003 when used with POP3 mail provider over slow network connection

When received messages include embedded pictures, Outlook 2010 does not persist those pictures in the .pst file with the message text. Instead, it redownloads the pictures every time the message is rendered for viewing or printing.
Send/Receive to replicate a message with multiple embedded pictures from POP3 mail server (not Exchange server)
Select and view the message - notice all the x placeholders for the embedded pictures
Right-click any x placeholder and select to "download pictures"
After some delay, the pictures are rendered, replacing the placeholders, to form the complete message
Now, select "File" and "Print" -- notice that the preview is not immediately displayed. There is a delay while thos same embedded pictures are downloaded, again. Sometimes there will be a pop-up notification that Outlook is "communicating with
the server"
Eventually the message is fully rendered with all embedded pictures
Now, select a different printer -- notice that the preview disappears and it takes time to .... yes, redownload those same pictures, again.
Finally, click on "Print" -- notice yet another delay for a final download to rerender the message for the printer.
Having done all that, close Outlook, disconnect from the network (turn off wireless or disconnect wire), open Outlook and view that same message. The x placeholders are shown instead of the embedded pictures. Although those embedded pictures
were downloaded multiple times already, they were not persisted locally.
Outlook 2003 and 2007 correct ask for confirmation to save the pictures locally then does so. Printing and viewing is then possible without having to redownload those pictures.
Is there going to be a fix for this Outlook 2010 defect? I've been waiting, applying updates, and waiting.....

Please do not close this thread. The issue remains. I apologize for not checking back sooner. I thought I would get pinged by email when this tread was updated; I did not. I'll monitor more closely in the future.
First, please note that I explicitly set Outlook to NOT download pictures automatically. I want to be prompted to download. However, after confirmed that I want the download, I expect pictures related to the message to be downloaded only once,
immediately after I confirm that I want them downloaded.
I have confirmed many times that the behavior in this area is NOT identical between 2003, 2007 and 2010. In particular, 2007 does download once and store locally (if user confirms to save changes when prompted), as expected, and 2010 downloads each
view/preview/print.
This is quite easy to verify -- simply unplug any network cable, disable wireless, etc. In other words completely detach from the networked world. 2007 will correctly view/preview/etc. from local storage whereas 2010 always reverts to showing
placeholders for any embedded images. This is 100% repeatable.
As an additional verification, simply move the .pst file to another system that is not connected to any network. Open the .pst file with 2007 and any embedded images that were already downloaded (and saved) are there, with 2010 they are not.
With 2010, it is bad enough that embedded images are not saved for viewing when disconnected. Worse than that, the repeated downloads can be a significant disruption to performance. Just get on a really slow wireless connection as is typical
in some hotels. Then try to view and print messages with lots of embedded pictures. Slow takes on a whole new, even slower, meaning.
This 2010 defect has been reproduced. Is there a KB article, Windows Update, hotfix,.... anything available to eliminate this problem of repeated downloads of embedded pictures?

Ichat screen sharing - "slow network"

Hi
I am trying to use screen sharing between an intel imac and a mac book pro over the internet. Both running latest versions of Leopard. The enable screen sharing menu item is greyed out. Connection doctor has a red cross next to "share my screen" with the message "(slow network)". Same for host multiperson video. Share remote screen has a green tick.
I have enable upnp on my router as recommended elsewhere. No change. Similarly, I have also set Quick Time streaming speed to 1.5 Mbps. No change.
I have tested by internet speeds at www.auditmypc.com:
download: 9782Kbps
upload: 526.4 Kbps
Is the upload speed causing the problem? Any tips on how to fix this pls (Virgin Media cable broadband)?
Thanks

QT is still on 1.5Mps, which I had set before trying the tips suggested here. iChat video still has the 500Kbps setting I gave it as advised.
Oddly, screen sharing is now available even though I am back on wireless not ethernet. This all seems a bit unpredictable and unreliable for something which is supposed to be 'easy' screen sharing!
Thanks again for the help people have given which has (hopefully) fixed this.

HP Laserjet M1132 MFP is too slow over the network!

Hi,
My HP Laserjet M1132 MFP is too slow over the network!
I have connect the printer to a windows XP 32bit SP3 using UBS port. The printer works fine on the local computer but when sharing it over the network it works too slow, for example with print test page it takes about 45 seconds to print and for other documents it takes much longer time.
I have installed the latest driver form HP website and upgrade the firmware it the latest version.
It happens on other Windows XP machines as well.
I connected the printer to my laptop (Windows 7 64bit) and it works fine (No delays over the network) and it seems that this problem have some relations with the windows XP Driver.
I have used local port trick on remote machines (instead of regular method) like this:
''add a local printer;
'new port'
'localport'
\\XPcomputer\HPPrinterName as port name
but still nothing!
There is nothing wrong with the network, we use to use a Samsung printer on the same machines over the network with no problem.
I Really appreciate your HELP!
This question was solved.
View Solution.

BEHZAD_T, how is the printer connected to the network (wireless or Ethernet)? If it is slow wirelessly, I would suggest trying to connect the printer to your router with the Ethernet cord and install it to the networked computer that way.
Another question is, relatively speaking, how close to your router are the Samsung printer and the HP printer? Depending on the distance (and what stands between the devices) there can be a lag between sending a print job and it being received by the printer.
Let me know!

Very slow working with eps files over new network

Please help!!!
Our IT has recently upgraded us from a OSX server to a 2 Terabyte SNAP SERVER 520.
I am using the only INTEL Mac in the department (we have another 10+ G5 PPCs running 10.4), and the only one using OSX 10.5. Since changing to the new server, I am also the only one with several file saving/opening issues.
I believe this is a network issue.
It is with mostly ADOBE products and we all know they will not support, working over the network. Due to the volume of files, I simply cannot drag files to my HD, and work locally. It is not practical. I also know that we have not had any issues in the past, and don't see why I can't get to the root of the problem.
**The most obvious issue is Illustrator .eps files.**
I can open and save .ai files in good time both locally, and over the network. There is no difference either way. HOWEVER, if it is an .eps file working over the network is not practical. I get the spinning wheel for about 2 minutes each time I open, save, or make a change. It is VERY slow. Working on eps files locally is fine (about the same speed as .ai files), but as soon as it hits the server, it is painfully slow to do anything.
Additionally, when saving Photoshop, Illustrator, InDesign AND Quark 7 files (direct to the network), I am regularly getting "Could not save because write access was not granted", or "Could not save becasue unexpected end-of-file was encountered", or "Could not save because the file is already in use or as left open" type errors.
I simply then click 'OK', and then hit save again, and it either gives me the same message, or it goes into 'save as' mode which lets me save the file (same name, and same location, but the original file has disappeared).
I am connected to the server IP address through afp:// but have also tried cifs://. IT have removed all access to the server through smb://, so I cannot try this.
ANY help is appreciated.

With regard to the EPS issue, I think I may have found the source of the problem for SMB users: the Suitcase Fusion plug-in.
Did you make any progress on these issues?

Time Machine over the Network: Terribly Slow

Hello,
I've been using Time Machine for over 3 years now with no issues over the network; the destination being a 2TB external Seagate connected to another iMac connected through gigabit ethernet. Everything has been working flawlessly: Every hour Time Machine would MOUNT the sparseimage it created on the disk, BACKUP the data and UNMOUNT the disk image when finished.
Until I upgraded to Lion. The above process is still working per se, however it is PAINFULLY slow! A 50MB backup can take up to AN HOUR! Searching around on the net, advised that there could be an issue with Spotlight as well, however this is not the case for me, since Spotlight finished a new index in under 30 mins. Followed every tutorial I could find on the issue, to no avail..
I then upgraded to Mountain Lion with the hope that the issue will clear itself. Cleared my old backups, resetted Time Machine by erasing its .plist file, restarted my iMac just to make sure and connected Time Machine to the network share anew, creating a "sharing only" account on the host iMac, i.e. the one that has the external HD connected through USB. Still no luck.
I painfully realize that I still have the same issue. While backing up, network traffic is under 100KB, and activity monitor does not show any backupd or mds or any similar processes taking anything over 3% of CPU time.
What could be wrong?

Hello again,
Tries on the other iMac (also running 10.8.2) and things are exactly the same: Image creation takes almost half an hour, and copying crawls at under 1MB/min. While time machine image is mounted and Time Machine is "backing up", accessing ANY disk on the host Mac is VERY slow. Seems like something hogs up appleshare when Time Machine is in use. Mind you, there is insignificant network traffic as seen by Activity Monitor, as well as insignificant CPU usage while backing up.
Stopping backup and using tmutil to set the Time Machine destination to the mounted image as mounted by Finder, solves the issue again, revving up Time Machine throughput to over 20MB/sec! There is also no issues acessing the other Mac as well, under this scenario.
Up to this point, the only way I have managed to use Time Machine over a networked external HD is through the NAS server. Both configurations where I am using a Mac running 10.8.2 as a server of the external disk have failed with very low throughput while backing up. Something must be wrong in 10.8.2's afp when Time Machine is mounting the image by itself.
I may need to remind you that I have been successfully backing up to the external HD for 4 years now; something broke a few months after the client iMac was upgraded to Lion and at the time when the host iMac was upgraded to Mountain Lion. Will try to locate a Mac running some later OS X version to do some more testing.
Also reminding that I have used two distinctive iMacs and two external HD drives for my tests so far. The client iMac has remained the same, however 10.8.2 has been reinstalled on it a couple of times. Have also used an afp-enabled NAS server which worked fine with Time Machine.

(Slow Network): iSight camera not working in iChat since Leopard upgrade

I have a different type of iChat video issue. My Power Mac G4, 867 MHz, 1 GB DRAM is a supported Mac for the Leopard upgrade. I've successfully installed OS 10.5.
Also my Power Mac meets the iChat Conferencing Requirements for 1-on-1 Video Chat per the OS 10.5 system requirements and the application note here:
http://docs.info.apple.com/article.html?artnum=301050
My iSight camera is connected via Firewire to an Apple Cinema Display, which feeds back to the Power Mac G4.
1) When I boot from my 10.3.9 Carbon Copy Cloner backup my iSight works in iChat (at least locally to see myself) without any issue. Green light comes on and shows me locally on video and audio sound bars. Before the OS upgrade the iSight worked fine for live video conferences with iChat 2.1.3 under Mac OS 10.3.9
2) Running OS 10.5 when I go to iChat 4.0's preferences video pane the following message is waiting "This computer does not support video conferencing."
3) With Leopard iChat 4.0 the Connector Doctor under "capabilities" says "(Slow Network)" for 1-on-1 Video Chat and won't even show video locally or turn on the iSight's green light.

Fixed!
My Power Mac Quicksilver G4, 867 MHz. problem with (Slow Network) in the iChat Connection Doctor, no video preview or video iChat since upgrading to OS 10.5 Leopard and iChat 4.0 has been solved with the following posted towards the end of the thread below. I can finally see my video preview with iChat 4.0 and have also video chatted successfully with one other user.
Topic : Macbook - iChat says "This computer does not support video conferencing"
http://discussions.apple.com/thread.jspa?threadID=1197506
Fixed by Apple Article: http://docs.info.apple.com/article.html?artnum=307035
Products affected
Mac OS X 10.5 Leopard
iChat
PowerPC-based Mac with a 867MHz processor
Solution
Quit iChat.
Open Terminal (it's in the Utilities folder, in the Applications folder).
In Terminal type or paste this command on a single line:
defaults write com.apple.iChat newbwdup 300000
Press Return.
Quit Terminal.
Open iChat.

CS3 slow over local network

I'm on a MacBook Pro 2.33GHZ Core 2 Duo w/2GB RAM.
Websites are shared from a Windows XP machine using normal
built in file sharing.
In Dreamweaver CS3, opening a document takes a while. And
once it's open and everything looks good, I can click on an image
and count out 2 seconds before the image actually highlights. Click
on another image or in a table cell to type text, and it's another
two seconds.
This site website, copied to my own hard drive, responds as
fast as it should - near instant.
The website and images aren't large by any means, 43k with
HTML, images, and css. It seems weird that it'd be slower over the
network than locally. Once Dreamweaver has the document open and
everything loaded, just selecting different elements shouldn't take
a performance hit.
I didn't have this problem with Dreamweaver 8.
Anyone else having this issue? Any suggestions?
Thanks,
Ryan

Hi theand
Thanks for going through the Mac troubleshooting TechNote.
Sorry it didn't
help.
1. Can you please send us a bug report so we can get your
contact info?
Please let us know that you are "theand":
http://www.adobe.com/go/wish
2. Can you reproduce this problem on another Mac connecting
to your same
server?
3. On your Mac, in the Site Definition, how do you have the
Local Info and
Remote Info sections filled out?
4. Do you have any sites that use an FTP server? Do those
sites have the
same problem?
5. What kind of server are you connecting to in your local
network?
Thanks,
David Alcala
Adobe Product Support
"theand" <[email protected]> wrote in
message
news:f0db3f$rgk$[email protected]..
> I've followed every suggestion on the general Mac OSX
troubleshooting tech
> note
> and none of them helped.
>
>
2. Can you reproduce the problem in a new site definition using
a new
> local
> root folder that only contains one file? Setup this site
so it has no
> remote access (i.e. no FTP, Local Network, etc.)
>
> I have an existing site which is on my hard drive and
does not produce the
> problem. If I then go back to a site served across our
local network the
> beachball appears as soon as I open a file, not before.
After about 30
> secs to
> a minute it will free up then if i click anywhere or
scroll it will beach
> ball
> again and so on.
>
>
3. Does your site have a lot of files and subfolders?
>
> The sites on the network have a lot of files and
subfolders. DW8 worked
> with
> them fine however.
>
>
4. Does the problem only happen if you have DW open for a long
time or
> can
> you reproduce it right after opening DW?
>
> It happens as soon as I open a file immediately after
launch.
>

Mac painfully slow over mixed network SMB/CIFS

I am using a Mac mini over a mixed office network. Several network operations are painfully slow. I posted a previous topic when I was using my G5 over the same network. Nothing has been resolved. G5, Mac mini or any Mac are slow over the network.
-photo previews take at least 2 minutes each to view while on a PC the whole drive of previews are instantly seen.
- Entourage common network calendar takes 5-10 minutes to view/update while the same common calender on a PC takes a few short seconds.
- Browsing folders on network drives is slow.
- Transfering files is slow
Basically any work done over the network from the Mac is tediously slow. Burning CD's and hand carry the files to other offices would be faster. The PC's instead all work fine over the network.

This looks very interesting and worth looking into. I've got the info in the hands of our net administrator.
I am making progress. I switched the mac mini from ethernet to airport. That has helped dramatically. A folder of 175 mb that was going to take hours and hours to copy to my local drive (I finally gave up) only took about 2-3 minutes over wireless. Previews of photos now happen in a few short seconds. The Entourage common calendar still takes a while to upload but that's probably an Entourage issue.
Our network administrator is going to string new cable to my office and we'll check the switching as well.
Thanks everyone for your continued help as we solve this issue and rescue the Mac's reputation in a windows environment.
This sounds alot like a duplexing issue, whereby
your macs are connecting eventually to a switch, that
isn't properly auto-negotiating your ethernet speed.
You can try going into the Network preferences and
forcing your mac to either 100 full duplex or 100
half duplex and do some testing. Some Bay
Network and Cisco switches must be set (if they are
managed switches) for fastpath operation where they
will autonegotiate better with equipment like our
Broadcom manufactured network interface cards. I
had the same issue at home with a Netgear switch, I
replaced it with a Dell gigabit switch and the
problem went away.
Power Mac G5 Dual 2Ghz/iBook G4
1.42Ghz Mac OS X (10.4.8) 2.5 Gig, Rad
9800 Pro 256M

IChat 4.0 - Share Remote Screen - "Slow Network" Problem

The iChat Connection Doctor shows that I don't have the capability to "Share Remote Screen" due to "Slow Network." I am able to have someone else share my screen, but not the other way around. The "Ask to share users screen" option is grayed out. I've tried it on two different cable modems, which are not slow. Does anyone know a fix for this?
I'm running a 867 MHz PowerPC G4 with OS 10.5.1.

http://docs.info.apple.com/article.html?artnum=307035
7:36 PM Saturday; December 8, 2007

Finder extremely slow over Airport Network after updating to 10.4.11

Hi, I have a problem with 10.4.11. Since I upgraded, about two weeks ago, I experienced an intolerable slowdown of the Finder over my Airport network. When trying to access folders and files located on my Powerbook (PowerPC G4) from a Mac Mini (also PowerPC G4) over the network the Finder stops, sometimes for minutes before opening a folder or copying a file.
When I tried the reverse, e.g. accessing the desktop Mac Mini from the Powerbook (which still runs 10.4.10) all worked fine, in reasonable time.
Do anybody have a similar problem? How can it be cured?
Thanks for helping.
Piero

I have the exact same issue, and so does my sister, who has an iMac on the same network. Did you ever find a solution?
At this point, it's so annoying that I'm thinking of downgrading to 10.4.10. Does anyone know if this will fix the issue and what the ramifications of downgrading might be? Anyone know where 10.4.10 can be found?

Slow network with Time Capsule

Hi There!
We have a network at home consisting of a Time Capsule (to provide wireless to the house as well as to hold all of our iTunes content and use as a file server), two Mac Pro towers, a MacBook Pro, an iMac, and two Windows-based notebooks, and an Apple TV. We are NOT using the Time Capsule for backup.
The problem we're having is that the network is incredibly slow. Trying to copy a large file over the network can take hours when it should only take minutes. And we can't stream shows/movies in iTunes from the Time Capsule because it pauses every one or two seconds to catch up. We also have business grade cable modem service but we can't do iChat videoconferencing without the audio/video completely dropping.
We tried purchasing an Airport Express to extend the range of the signal (and even purchased a second one!) but those didn't help, either. The firmware on all devices it up-to-date. And the network is closed (no one is leeching).
Are there any tools, either built in to OS X or another source, that can help us diagnose what's wrong with our network? What other things can we try to diagnose the slow network?
Thanks!

First of all, be aware that the more devices you connect to a wireless network, the slower it goes. In addition, if you have devices that only work at B or G speeds, all devices on the network slow down to the slowest device.
For example, when you have a 300mbps N device and a 11mbps B device connected to the same network, they'll both go at a maximum speed of 5.5mbps. You are limited to 11mbps because of the B device and then further limited to 5.5mbps because there are two devices sharing the total (11mbps) bandwidth.
As far as testing out your current connection, try these:
1. On a mac, you can hold down Option and click on the airport/wireless icon. This will show transmit rate and other information. The maximum transmit rate for N devices is 270, G: 54, B: 11. If the transmit rate is very low, this indicates a poor wireless signal
2. Change the wireless channel used by your time capsule to something else. Try them all to see what gives you the best wireless signal
3. In the airport utility, select the time capsule, go to manual setup, go to advanced, click on Logs and Statistics, then click Wireless Clients. This shows the transfer rate, noise, and signal for each device connected to the time capsule.
4. Download iStumbler. This mac application will show other wireless networks in the area and what channel they're using. It is typically not good to set your network to use the same channel as others in your area.
5. Download some sort of application that shows transfer speeds (like iStat Pro). Test transferring large files between computers to see how fast it goes with different setups.
There's a few things you can do to improve wireless performance when bogged down with too many devices:
1. Turn off any wireless devices not in use. If it's on, it's using bandwidth space even though it's not transferring data.
2. Use multiple routers or a dual-band router to create separate networks. For example, you can make the time capsule make a 802.11N-Only network which will only the new N devices will connect to. Plug an express into it and make it create another network (G-only or B/G-only). Keep plugging in additional routers and make new networks as needed.
3. Replace older B/G devices with N devices if possible.

Time machine running slow and slowing network access

I have had and continue to have issues with wifi on my MBP. Those are pretty well summarized in https://discussions.apple.com/thread/5535320?start=30&tstart=0. I've been able to make mt system usable with some of the less dodgy workarounds in that thread ( like keeping a ping on my router running )
That thread really doesn't mention the issues I've been having with time machine though, so I thought I'd bring this up here. Whenever time machine starts up, Safari and mail become unresponsive. It's worst when TM is "preparing" of "cleaningup", though barely usable during the actual backup. Mostly, I can work around that too, but occationally, TM will find GB of data to be backed up and lock up my mac for a day. Here's a recent example:
2/16/14 12:30:27.952 PM com.apple.backupd[11557]: Starting automatic backup
2/16/14 12:30:28.466 PM com.apple.backupd[11557]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:30:33.866 PM com.apple.backupd[11557]: Mounted network destination at mount point: /Volumes/TimeMachine using URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:31:44.678 PM com.apple.backupd[11557]: Disk image /Volumes/TimeMachine/sparky.sparsebundle mounted at: /Volumes/Time Machine Backups
2/16/14 12:31:46.613 PM com.apple.backupd[11557]: Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
2/16/14 12:34:07.904 PM com.apple.backupd[11557]: Will copy (1.66 GB) from Macintosh HD
2/16/14 12:34:08.004 PM com.apple.backupd[11557]: Found 83487 files (1.66 GB) needing backup
2/16/14 12:34:08.738 PM com.apple.backupd[11557]: 4.16 GB required (including padding), 445.21 GB available
2/16/14 1:32:33.579 PM com.apple.backupd[11557]: Copied 534.6 MB of 1.66 GB, 28317 of 83487 items
2/16/14 2:40:02.513 PM com.apple.backupd[11557]: Copied 564.1 MB of 1.66 GB, 30225 of 83487 items
2/16/14 3:46:20.853 PM com.apple.backupd[11557]: Copied 593.2 MB of 1.66 GB, 31631 of 83487 items
2/16/14 4:48:19.461 PM com.apple.backupd[11557]: Copied 621.8 MB of 1.66 GB, 33182 of 83487 items
2/16/14 5:00:31.968 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 5:54:51.036 PM com.apple.backupd[11557]: Copied 658 MB of 1.66 GB, 34773 of 83487 items
2/16/14 6:17:20.839 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 6:56:27.566 PM com.apple.backupd[11557]: Copied 688.2 MB of 1.66 GB, 36246 of 83487 items
2/16/14 7:57:07.076 PM com.apple.backupd[11557]: Copied 704.8 MB of 1.66 GB, 37267 of 83487 items
2/16/14 8:58:52.469 PM com.apple.backupd[11557]: Copied 730.7 MB of 1.66 GB, 38724 of 83487 items
2/16/14 10:09:42.807 PM com.apple.backupd[11557]: Copied 760.5 MB of 1.66 GB, 40291 of 83487 items
2/16/14 11:21:25.825 PM com.apple.backupd[11557]: Copied 803.8 MB of 1.66 GB, 42462 of 83487 items
2/17/14 12:30:58.322 AM com.apple.backupd[11557]: Copied 834.1 MB of 1.66 GB, 43513 of 83487 items
2/17/14 1:45:28.495 AM com.apple.backupd[11557]: Copied 846.1 MB of 1.66 GB, 44160 of 83487 items
2/17/14 2:45:36.010 AM com.apple.backupd[11557]: Copied 868.6 MB of 1.66 GB, 45485 of 83487 items
2/17/14 3:57:29.939 AM com.apple.backupd[11557]: Copied 890.6 MB of 1.66 GB, 46729 of 83487 items
2/17/14 5:07:30.971 AM com.apple.backupd[11557]: Copied 926.7 MB of 1.66 GB, 48695 of 83487 items
2/17/14 6:15:49.283 AM com.apple.backupd[11557]: Copied 963.7 MB of 1.66 GB, 50583 of 83487 items
This is on an AC router. My peak throughput shows 19 Mb/s on menu meters, so, not great, but not this slow. Mostly, the network activity is nothing with short bursts of higher throughput.
I'm hoping this will be addressed in 10.9.2. In the mean time, are there any workarounds to get past this issue short of turning off TM?
Thanks,
Horst

These instructions were taken from Mac OS X Hints at:
http://hints.macworld.com/article.php?story=20050302225659382
The Unix program dd is a disk copying util that you can use at the command line in order to make a disk image. It makes a bit-by-bit copy of the drive it's copying, caring nothing about filesystem type, files, or anything else. It's a great way to workaround the need for Norton Ghost.
Normally, in order to make a disk image, the disk you're copying from has to be able to spin up and talk -- in other words, it's OK to make a copy if the disk is healthy. But what happens when your disk is becoming a doorstop? As long as it continues to spin, even with physical damage on the drive, dd and Mac OS X will get you out of the fire.
We had a situation recently where a friend sent a disk to us that had hard physical errors on it. It would boot in Windows, but then it would hit one of these scratch marks and just die. We fired up dd, and it started OK, but stopped at the same physical error location -- complaining about a Hard Error.
So the workaround was to designate the dd mode as noerror -- which just slides over the hard stops, and to add the mode sync, which fills the image with nulls at that point. We did it on BSD Unix, but as long as you can get the hard drive attached to your Mac, the command is the same:
dd bs=512 if=/dev/rXX# of=/some_dir/foo.dmg conv=noerror,sync
The bs=512 designates block size, and the if=/dev/rXX# is the UNIX path to the actual disk device. Make sure that the chosen directory (some_dir) has enough room to take the entire disk image -- which will be equal to the size of the drive. Since dd doesn't care about the contents of the drive, it copies every bit on the thing, so you get an image equal to the disk's capacity. A really big file. One workaround is to put it on a RAID array.
Once you've established the disk image (in this example, foo.dmg), you're almost home. Here's where your Mac OS X box is far and away the best thing to have. In this example, the dd output file is foo.dmg. You have to realize that this is an exact copy of a busted drive, but the "holes" are filled with nulls. As long as the damage isn't to the boot sector, though, when you double-click on it, Mac OS X mounts it without breathing hard ... who cares if it's FAT32, NTFS, whatever.
Due to the size of the image that we were copying, we put it on a RAID array, and had to access the image over the network -- it still mounted fine. In straight UNIX, if you try to mount a disk image, it complains that there is "no block device" and fails. Once your image is mounted, it appears in your Finder, and then it's easy work to retrieve the critical files from the image -- usually things like .doc files and .xls files and the lot.
Finally, since your disk is actually dying, once you have your image, you can drop it to tape or something and you've not only recovered your files, you've made a viable backup as well. Once again, that which destroys a Windows box becomes a play thing to a Mac OS X box.

IChat over slow network

Similar Messages

Maybe you are looking for