IOS networking problem

Hello,
I have an iPod touch 4G updated to ios 5.1.1
In my home i have 2 routers connected together and spaced
1 of the routers is connected to the internet. The DHCP is disabled from  both routers and also from the internet modem ( it is a must )
So i have to assign IPs manually on the iPod and all other devices. After i assign IPs manually on ipod and moving from a router to another router, the ipod will connect to the nearest router and will send a DHCP request and the router will give it a dumb useless IP knowing that the IPs are already assigned on the ipod manually. I have tried other devices such as Nokia phones they had no problem when moving from one router to another. The weird part is why the ipod is sending a DHCP request while the IPs are already entered manualy. I believe that this is a bug from the ios. Any ideas?
What i have tried to do: 1. Forget the network then redefine it again
                                      2. Upgrading from 5.0.1 to 5.1.1

that's nice.  Do you have a question you would like to ask?

Similar Messages

  • What cause searching network problem after updating iphone 6 from iOS 8.1.2 TO iOS 8.1.3?

    what cause searching network problem after updating iphone 6 from iOS 8.1.2 TO iOS 8.1.3?

    SSince Apple does not support downgrading the iOS I suggest you start a new question that gives a good title to a specific problem. Then in the body of the thread describe the problem in detail, tell us what steps you have tried so far to correct the problem, what happened, and what error messages you received.

  • 3gs no service after updating to ios 5 tried network reset, reset all settings and even restoring from back been with out phone for 3 weeks now need help telus cant find network problem and apple has bad customer support please help!!!

    my 3gs has no service after updating from ios 5 tried resetting network settings, resetting all settings and restoring from back up on itunes.
    telus cant find any network problems and apple is difficult to deal with.please help 3 weeks with no phone and $70 a month not happy.

    I have been having a similar problem for the last few days.Without warning the signal will just completely duck out leaving the device searching for several minutes before settling on a no signal message.
    Sometimes restarting the device, toggling data and 3g settings or toggling Airplane Mode will set things right. However, a lot of the time I've been left without a working phone.
    I don't believe this is a SIM issue, as I had to change my SIM only one month ago for another signal related problem. Again any help would be appreciated here as well.

  • Battery & network problems after upgrade to ios 5.1.1

    The day I upgraded my iPhone 3g to iOS 5.1.1 It started to given me Battery and Network problem.
    Battery Problem Details :
    1. Battery life last for only 2 to 3hrs after being full charged (i.e. to 100%)
    2. If i use the phone example try to use a App or browse a website in 1 min the battery life drops down by 20 to 30 %
    Network Problem Details :
    1. I keep lossing network connection
    2. I have to go to setting and choose it manually each time. Keeping it on Auto doesn't work
    Note when my phone was on iOS 5.0.1 it use to work without any of these issue
    Please Help

    My network problem has been resolved after i did a Reset (all Setting) but the battery life is still a problem.
    I have read on other post that 5.1.1 has caused many user battery life issue. I have tried the resolution that people are saying resolved their issue i.e. to drain the battery and then charge it to 100% leaving in on Charge for more 1.5 hrs but this too did n't work for me.
    I did a Restore and Reset and other trouble shooting step but none has help till now.
    Hope Apple is listening.

  • Facing network problem with iPhone 5s after updating it to iOS 7.1.2 .

    Facing network problem with iPhone 5s after updating it to iOS 7.1.2 , using Vodafone in india. if at one place network is full then after few minutes at same place i get no network ? what can be done ?

    Hi srikka,
    I'm sorry to hear about the issues you've been having with the iOS 8 upgrade on your iPhone 5s; I know how frustrating that can be, especially on a device you use every day like a smartphone. If you continue to have issues with your WiFi and cellular data connections, you may find the troubleshooting steps outlined in the following articles helpful:
    iOS: Troubleshooting Wi-Fi networks and connections - Apple Support
    iPhone cellular data connection issues - Apple Support
    Regards,
    - Brenden

  • Network problems with Apple TV 3 - streaming / home share etc

    My setup:
    iMac (21", mid-2011) running OS X 10.7.3 and iTunes 10.6
    Apple TV 3
    Apple Airport Extreme router
    BT HomeHub 3
    HomeHub is used as a modem (ADSL), wired connection into the Airport Extreme which then provides my wireless network.
    Apple TV set up last Friday (launch day). I have it set to use home-sharing with iTunes, and have tried the YouTube channel. Not tried using the iTunes Store direct.
    Initially had problems with 'streaming' video from iTunes using home-sharing, buffering either took a VERY long time or simply didn't happen at all. After a reset, updating OS X, iTunes, Airport Extreme firmware etc etc it started to work fairly well. Also tried streaming video direct on the YouTube channel (very fast, no buffering delay at all) and using AirPlay from an iPad (again, no problem).
    Tonight, everything appears to be broken. Home sharing from iTunes has taken 2 minutes to buffer 30 seconds of video; YouTube similar; AirPlay from the iPad doesn't appear to be streaming at all.
    Have tried re-starting iTunes; re-starting the Airport Extreme; re-starting the Apple TV. Nothing changing.
    Help?!

    I don't have an answer for this, unfortunately. I've even had my Apple TV replaced (yesterday), and after about an hour of normal operation, it now fails to connect to servers, or connects intermittently and poorly, and it can no longer connect to the iOS Remote app. These are the exact symptoms that prompted the Genius Bar to replace the original unit.
    Either there is a basic flaw in Apple TV, or I'm extremely unlucky. All my other Mac and iOS devices have positively no network problems. Very frustrating.
    WiFi is provided by a late-model AirPort Extreme.

  • 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

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

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

Maybe you are looking for