LaCie MiniHD connect network problem

I have a LaCie MiniHD connect in my local network. Did everything LaCie told me to do so I could write to the USB attached LaCie drive.
Formatted the drive in OS X EXtended but not journalized.
Tried to connect via smb://MiniHD.smb.tcp.local and the network told me to enter my ID and Password, I don't know why.
So I brought back the disk drive to my mac and changed the whole drive permission to read and write for everyone.
Brought back the drive to my TV and now I could transfer anything from my mac to the drive.
I was glad of that, but having shut down the drive and the MiniHD connect, when I opened it again to transfer something from my mac to the drive, I still got the same problem again with the same message.
"One or more elements cannot be copied to "LaCie_750" because you don't have the permission to read. Do you want to copy the elements you are authorized to read."
I suspect the software on the Lacie MiniHD connect to block OS X when it initialises the drive on startup.
In particular I see a folder named _HF2VN~W appearing in the root level of the drive.
Can any one help me with thi samba network problem on Mac OX 10.6.5?

I have since had a reply from LaCie to say that this issue has been identified and is being worked on - however I'm afraid that I don't have any timeline for when this will be fixed.

Similar Messages

Direct connection network problem

hi. I've just set up a network using a direct connection cable between 2 computers. Currently the cable (15meters) is connected to the Realtek lan port with the other side connected to a SMS (100mps) network card in the other machine( pentium 2.4 GHz 640MB ram). Every few minutes or so the "network cable is disconnected" blob in the system tray appears. Also this problem persists when playing network games using a TCP connection. My IP addresses are manually set up to 197.197.197.1 & 197.197.197.2 on the other machine. All firewalls are off and both the nVidia & realtek ports give the same problem. What could be the problem?

slaska,
Just make sure you use the Port that you loaded the Drivers for. I would suggest using the nVidia one since when you load the nVidia nForce Drivers, it will active that NIC.
Are you sure you are plugging the CAT-5 Crossover into the correct NIC?
Take Care,
Richard

Hyper-V 2012 R2. RemoteFx. "The remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again."

After a Installation from Windows 8.1/windows 7 everything works fine. For example Install updates and Software. If I connect the first time a remotefx card i can use RDP as well. But if i restart the host I get the mentioned error. What can I do. These
Hosts are not in a domain configuration. I tried it too but there was no difference. I didn't discovered any errors in the eventlog, too. Only an actviex error. But same errors occurs with a succsefull rdp session.
Also strange is if i start the vm without a remotefx card it works fine again. Only session with a Remotefx card aren't possible anymore.
Is there a bug or something. I tried it many times with the same error.
Maybe someone can help me.
kind regards
Tobi

Hi Tobi,
Thank you for posting in Windows Server Forum.
For a workaround, please try to perform the two steps.
1. Do NOT enable RDP 8 on the Windows 7 SP1 VM. You should install RDP 8 and update the ICs though.
2. Change the connection setting on the client from "Automatically detect" to "LAN"
Please check again below thread for information.
a. "The remote session was disconnected
because there were network problems during the licensing protocol" after enabling RemoteFX Windows 8 VM
(Please recheck answer by “dgeddes”)
b. "The remote session
was disconnected because there were network problems during the licensing protocol" After Installing RemoteFX
Hope it helps!
Thanks,
Dharmesh

Sir you have replied for my question, and i updated my software and all those things, yet it is showing unable to connect network, but i can use internet by sim, is it the problem related with hardware? can you tell me a solution for it?

sir you have replied for my question, and i updated my software and all those things, yet it is showing unable to connect network, but i can use internet by sim, is it the problem related with hardware? can you tell me a solution for it?

you seem to be referring to an ongoing issue
click here to respsond -> sir help me to enable my network connection, my iphone 4s is not connecting with any wireless connection, what i should do for enabling network connection?
CCC

Network problems are preventing connection to Exchange when changing from Ethernet to Wifi

I have a user that connects to Exchange fine while their computer is docked and connected to the LAN by Ethernet, but once they undock they receive the error "Cannot open item. Network problems are preventing connection to Exchange server." They
are connected to the internal company Wi-Fi and nothing changes about their computer's status other than changing from being on the wired network to wireless.

Hi,
What's your Outlook version and Exchange version? Outlook 2007 or Outlook 2010/2013? Please check your Wifi settings and make sure your Wifi password is correct.
In Outlook, please click File > Account Settings > Security and
make sure the Encrypt data between Microsoft
Outlook and Microsoft Exchange is checked.
Regards,
Winnie Liang
TechNet Community Support

I have been trying to share file between my Mac Book Air and PC Laptop.Sometimes my Mac sees the PC and tries to connect but every time the connection fails. It says server may not exisit or network problem. I have apparently no network problem. Thanks fo

I have been trying to share file between my Mac Book Air and PC Laptop.Sometimes my Mac sees the PC and tries to connect but every time the connection fails. It says server may not exisit or network problem. I have apparently no network problem. Thanks for any help you may provide

hi,
somewhere on the windows machineshould be something like "network setup wizard". exactly where it is and what it is called i cannot remember off the top of my head, windows help is actually slightly useful here, it should have a link to it.
all the options checked on the mac are only what services the mac is offering to other machines, they have nothing to do with the services it can access (mostly...).
oh yeah, to actually connect to the pc after you have turned its sharing on, use the finder, or, when it does not show the pc (this happens on and off, possibly a refresh problem apple...) choose go --> connect to server and enter smb://<pc's name or ip>
to find the ip, the easiest way i think is
start --> run --> cmd ->> ipconfig
Andrew
Message was edited by: Andrew Dicker

3G network problems in DC: cannot connect to internet, but works with EDGE

I can load web pages fine when I turn off 3G in the settings tab (and use only EDGE), but when I turn on 3G I need to "reload" the page several times before it will load.
This is really annoying because it is clearly a AT&T 3G network problem. After spending about an hour on the phone troubleshooting the problem with Apple-iphone and ATT "customer support", they concluded that although I was having a problem, because ATT does not show a current issue in the Washington, DC area, there is nothing they can do.
Argh! ATT and Apple need to work things out to fix the network problems, I hate being caught in the middle of their animus relationship.
I guess I will have to continue paying for a service that is spotty, because as the ATT representative pointed out, they do not guarantee any service and will not recompense for any alleged outage.
Wow, now that is a prime example of why having no effective competition in cellular providers means the customer loses.

I appears to me that the problem is not related to whether you are on the phone or not. Generally, it seems like there is a problem with the 3G network being EXTREMELY slow and non-responsive. When I press the reload button several times, sometimes is loads very quickly as I would expect on 3G.
Still having this problem today.

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.

Odd Network Problem

Hi,
I have a strange network problem, can anybody help?
Basic configuration
I have three networks 10.190.0.0, 10.192.0.0 and 10.193.0.0 joined by a single server running Solaris 11 B64a with a dual port intel card and onboard intel card (e1000g0/g1/g2) each port is plugged into the gigabit port of a seperate Dell powerconnect switch.
they have ip addresses of 10.190.0.2, 10.192.0.1 and 10.193.0.1
The problem. I have connected from a remote machine through a solaris router machine on the 10.190.0.0 network to a computer on the 10.192.0.0 network (Beyond a switch).
The terminal works fine!
if I ping the 10.190.0.1 which is the other router beyond the box with the three network interfaces packets are not seen by the pinging box. However, if I snoop the interface on the three interface router I see both the ICMP echo requests and replies.
After a considerable length of time 10-30 seconds, a load of the packets suddenly appear on the pinging machine and then continue normally.
I would like to understand:
a) where were the packets during the time between the snoop seeing them leave and them arriving at the destination?
b) why does the terminal not suffer any delays?
We are suffering with a lot of strange network issues at this new site and I am trying to figure out if its the new dell switches, the solaris network stack or something else entirely!
Anybody got any idea whats going on?
Please Help I am baffled.

It may just be the pinging machine has received the packets, but it will not display them on screen until it has found a name for the remote IP address (or until it times out waiting for one).
Do you get the same behavior with 'ping -n' ?
Darren

Mobile network problem in my lumia 520

Once network gone, I have to Restart it then again mobile network come.calling proble occurs many times even network is dispayed. Network problem sshould be rectify.

Hi mbkrish,
Do you experience the network issue regardless of your area? Aside from calling, are the other network services working fine like SMS messaging and mobile data connection? Is this for a Lumia 520 as well? If so, I hope you're using a standard microSIM and not a cut one as this is what the phone is designed to use.
BTW, the reset that the Nokia Care Center recommended is the one under Settings > about, is that right? After the reset, have you checked if the system apps are updated? Go to Settings > swipe to applications > store > check for updates.
Let us know how it will go.

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?

Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance

Windows Server 2012 R1 with Exchange 2013 SP1
Windows XP SP3 with Outlook 2010 (14.0.4760.1000) computer is on the same network, but not a part of the domain.
When I try to configure Outlook profile for the user, I manually enter exchange server name and user name.
Check User button underlines server name and user name and profile gets created successfully.
Once I try to open outlook for the user I get
Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance
If I search the content of the log files under
X:\Program Files\Microsoft\Exchange Server\V15\Logging\RPC Client Access
I can’t find any records indicating a connection attempt from the client’s IP or references to the version of the outlook used, however I can see a 3 way handshake followed by a 4 RCP packets and then 4 nspi bind requests and responses when outlook opens
up and then connection is torn down.

Windows Server 2012 R1 with Exchange 2013 SP1
Windows XP SP3 with Outlook 2010 (14.0.4760.1000) computer is on the same network, but not a part of the domain.
Hi,
That version of Outlook 2010 (14.0.4760.1000) is not supported with Exchange 2013 and will not be able to connect. It need to be on at least SP1 +
Outlook 2010 November 2012 update (14.0.6126.5000)
See: Exchange 2013 System Requirements -
Client Support
Martina Miskovic

Networking problem after a zone is created and installed

Hi all,
I've got a networking problem after a zone was created and installed on a Solaris 10 box. The box was configured with two NICs, one (e1000g0) with a public IP address, the other one (e1000g1) with a private IP address and connected to a local switch. All worked fine so far.
Then I created a local zone with shared networking (e1000g1). The zone has a private IP address which is in the same subnet as e1000g1 on the global zone. After some time, I noticed that I could not access (ssh, ping) the global zone. Then after some time, the global zone became available. The problem happened quite frequently.
Also I observed that: 1) When the global zone was unavailable from outside, it was available (ssh, ping) from another box within the same subnet (e1000g0); 2) If I shutdown e1000g1, the problem was gone.
Any idea what caused this problem?
Many thanks,
Xiaobo

It was a route problem.

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.

LaCie MiniHD connect network problem

Similar Messages

Maybe you are looking for