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

Similar Messages

  • Odd network (and Firewire) problems cured by unplugging iMac

    I experienced a weird problem with my May 2005 20" iMac G5 running 10.4.2. In October I suddenly lost the ability to connect with one of my computers but not the other. I could connect just fine to the G4 Powerbook running 10.4.3, but could no longer connect to my G4 tower running 10.2.8. The iMac would spend several minutes trying to connect and then the message I got was that the server did not exist or something similar, or sometimes it would say that the version of AFP on the G4 tower was incompatible (I hadn't changed anything). I could still connect from the Powerbook to the G4 tower without any problem so I knew that the tower was OK, and all of the computers were able to print normally through the laser printer on the network. My workaround was to transfer data between the iMac and the tower by going through the Powerbook, but this was a pain since it took twice as long.
    Of course I tried rebooting the iMac a number of times, but this did not help. I was thinking it was a software corruption of some sort, and was thinking of wiping the hard drive and reinstalling the whole system (fortunately I hadn't gotten around to doing that yet).
    This problem persisted for about 2 months until I also realized that my Firewire ports weren't working either when I tried to hook up a new external Firewire drive. The Firewire ports did not even appear under system profiling. I had a very hard time locating info about troubleshooting the Firewire ports, but finally came across the suggestion to unplug everything from the computer, unplug the iMac from the power and leave it off for a while.
    This unplugging cured the Firewire problem and also cured the networking problem!
    (I don't know why this worked. I keep the iMac plugged into a UPS to protect it against power outages if that makes any difference.)
    (The network configuration: iMac and Powerbook connect to Airport Express via Airport extreme, and the Airport Express is connected to the G4 "Digital Audio" tower through an 8-port Ethernet switch (which also connects to laser printer, a PC, and another very old Mac.))

    Chime,
    Good news for you. Actually, it's an emphatic YES!
    Every ISP I've ever used had fine print explaining that multiple computers require multiple accounts. The interpretation of this is: Every computer you want to have assigned a PUBLIC IP address from your ISP requires it's own account. If you try to get clarification, your ISP will argue it, they want you to pay them more money for unnecessary accounts!
    You only need one PUBLIC IP address from the ISP in order to establish internet sharing throughout your house. Your gateway will establish PRIVATE IP addresses for the computers on your home network.
    Plug the phone cord into your Base Station (if it has a dial-up modem), the base station then becomes the one PUBLIC computer allowed on your ISP. Configure it to dial out on demand. It becomes the gateway between the internet connection and your internal network.
    This is completly legitamate as long as you are sharing over an "in-your-own-home-for-personal-use-only" PRIVATE IP LAN behind your ONE gateway connection.
    Not familiar with the new Base Stations, all the older ones had modems. The base station with a modem IS the most convenient way to do this (esp. for dial-up) and provides the best firewall security for the whole network. However, if yours doesn't have a modem, it's still possible to establish internet sharing using one of your computers as the gateway to dial-out and share the connection.
    BTW - if BB options are limited, have you considered satellite options (DirecPC, etc.)?
    Mark

  • 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.

  • Help troubleshooting networking problem...

    I apologize for calling this a "networking problem," I just don't know how to title it...
    Basically, I'm looking for help tracking down an odd problem on my MacBook. It mostly manifests as incomplete web requests.
    I'll try to explain.
    I'll go to a website, which starts a browser downloading images and what not. Most times, I never get the entire web page. For instance, on this very page, the bottom of the browser (Firefox) says, "Waiting for images.apple.com" and the circle is spinning at the top. This unresolved request, whatever it is, is unlikely to complete.
    Here's what I've tried:
    1. Updating my wireless router. (Netgear G. I honestly don't notice this problem on other systems in my office, though.)
    2. Changing web browsers. (It affects others, too.)
    3. Creating Mozilla profiles.
    4. Surfing in different Mac accounts.
    5. Clearning browser caches/cookies/etc.
    6. Turned on/off interference robustness on the AE.
    I'm not looking for a solution (unless you have one). I am looking for some new ideas on troubleshooting the problem.
    What's most annoying is that the problem is GASP intermittent. I may do one of the above things, for instance, and it seems like the problem goes away, but it comes back eventually. And it also eventually leaves for a period of time if I do nothing.
    It feels like a networking issue, something outside the Mac -- wireless interference or something, but ... I just don't know.
    Thanks.

    I should have mentioned that I tried that.
    There are a couple of APs in the neighborhood, one is a Belkin Pre-N with Airgo's chipset. The only reason I mention the Belkin is that there have been some news reports that suggest Airgo's wireless management degrades regular B/G wireless devices in the area. I don't know how true that is.
    Anyway, it seems like I've solved it.
    I surfed wired for about two days and was able to determine that the problem was related to wireless communication. Now, whether it was my Airport Extreme or my Access Point...
    My Access Point was one that was given to me by a customer. She didn't need it any longer. It was used and I didn't really know how it performed. I can say that one of the things I did before all these problems started to take place was install that AP.
    I replaced the AP this weekend. I decided I would just try a new one.
    That seems to have fixed it. I do get the occasional hangup. (I do an awful lot of surfing.) Mostly I see the hangups now on pages that have an abnormally high amount of connections to external sources. An example of this is the dynamically generated Newsgator RSS feed page. This page goes out to all manner of websites to grab images and what not and I sometimes see hangups there, but that's about it.
    This is good news. I was worried my Airport Extreme was to blame. But, you know, even my wife's laptop (PC) is performing better wirelessly. There was a problem in that Access Point. I had updated the firmware just the week previous to see if that would fix the problems I experienced, but no...
    Anyway, I kind of needed to talk this out. I appreciate your help!

  • Networking problem from Mac running Leopard to Mac running Yosemite

    I have a curious networking problem and I would love some suggestions about what might be causing the problem and how to cure it.
    I have a PowerMac G5/1.8DP running Mac OS X 10.5.8 Leopard with a number of external drives attached that I use as backup for all my RAW files. These are mirrored on three drives.
    When I mount the drives on my iMac desktop, running OS X 10.10.1 Yosemite, over a gigabit ethernet network, two things are happening - 1. some of the folders are invisible (although they are actually there and populated on the PowerMac) and 2. spurious, empty, folders with odd names appear on the Yosemite desktop.
    I have checked on the PowerMac to see that the folders all contain files - they do - yet over the LAN they appear as empty folders with gobbledygook names. This happens on all my Macs running Yosemite so it appears to be a Yosemite problem, rather than a Leopard problem. To further reinforce that I have also checked the PowerMac from three other Macs, running Tiger and Leopard, and they can see exactly what is on the drives, with no missing folders or oddly named folders.
    The images show 1. the folder as it appears on the PowerMac running OS X 10.5.8, with two folders RAW Files 26 and RAW Files 28 highlighted, 2. the same folder seen on the Yosemite desktop with two folders, RAW Files 26 and 28, missing and 3. the same folder on Yosemite with three oddly named empty folders.
    I am at a loss to know how to cure it and hope that someone will be able to help.

    You can never, never, never transfer any installed version of PSE on any platform. You must always install from scratch on a new machine. By trying to do so you have made more work for yourself. You will need to download and run this:
    Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
    which will not seem to do anything, but is a necessary step to break the links within the program. Then you can go around and manually remove everything related to PSE that you can find, not only from Applications, but also from your username>library>preferences and the library at the top level of your hard drive>application support>adobe. You must go to these locations manually; spotlight will not help you with this type of search.
    Then you can reinstall from your original media or from the download here:
    Download Photoshop Elements products | 13, 12, 11, 10

  • Can't install HP Color LaserJet 2600n to my new macbook pro with Yosemite ? Message error : "Can't download the software because of a network problem."

    Hello,
    I'm trying to install my HP Color LaserJet 2600n (USB) to my new macbook pro with Yosemite ? It detects the printer but when I try to install it, I get the message error : "Can't download the software because of a network problem."
    I tried to install the software via the HP website. It's not working.
    Can someone help me with this one ?
    Thanks,

    HP Print Drivers

  • 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. 

  • Network problem with vodafone in india, noida

    network pronlem in my iphone 5 for last 8months, please advise what to do?.

    What problem?
    Any network problem with your cell phone carrier you need to take up with the carrier.

  • 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.

  • 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

  • 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.

  • 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.

  • How do you get them to take a network problem seriously?

    I have a couple of websites that I need for work.  For some reason They stopped working with Verizon phones, 3G and 4G, at least in my area around the 28th of march.  They work if you make a wifi connection and with other carriers.  When I finally got to a human she couldn't go off script and kept telling me that I needed to reboot the phone.  The only way that was going to work was if I hung up and rebooted and then went through their voice jail system again.   So I went to a franchisee and had them deal with it.  the only advantage they had was a number to get straight to a real person and they were on another phone so they could go through the rebooting sham.  They gave me a trouble ticket number >(Ticket number deleted)< and the problem is still unresolved.  Although it did briefly work yesterday.
    I can't find any place on their site to check the status of this trouble ticket and haven't heard from them since.  How do I check the status of the ticket and light a fire under them.
    It would be nice if people from around the country could check one of the sites; fsmstamps.com just so I could know if it is my area or everywhere.
    Message was edited by: Verizon Moderator

    It doesn't matter now.  They finally fixed it but the time was far too
    long for me not to have all the service I'm paying for.
    Nevertheless the phone # is <Personal information deleted per the TOS>
    What you really need to resolve is why it is so difficult to report a
    network problem.
    BTW the I posted the ticket number and someone at your end scrubbed it.
    <Personal information such as the phone number and ticket number is not to be posted on the public forum per the Verizon Wireless Terms of Service and should only be shared through a private "Direct Message" (DM for short).>
    Message was edited by: Verizon Moderator

Maybe you are looking for

  • I have given up on BB & Mac

    When I got my Curve last May I was told that it was 100% compatible with Macs. Wrong, wrong, wrong. I have tried PocketMac and basically just given up. They have tried to help me and RIM has tried to help me but have been unable to fix the problem. I

  • Kms is broken on a mac mini (bios emulation mode)

    kms shows up scrambled video on 320m nvidia using the open source nouveau drivers. nomodeset fixes this, but makes you use vesa so that breaks a whole other things. i'm using the the hdmi output with a dvi adapter. how can i go about in troubleshooti

  • The edit button in the widget animation properties is un-clickable

    the edit button is un-clickable , i cant click to edit the widget from the animation properties, and its causing me a problem because if i edited the widget from flash it works fine and no errors , but it has related objects in captivate , please if

  • Ipod won't sync with outlook

    My Ipod video 30 Gb wont sync with MS Outlook 2003. I keep getting an message that says: "iTunes can not copy contacts to ipod" then i get an error message then itunes shutsdown. Everything is up to date ipod is ver.1.1.1, itunes is ver. 6.0.4.2

  • Msn Messenger for Nokia n97

    Hi guys i cant find msn messenger on ovi store anymore, was it removed? thanks