Yep, the 'Unidentif​ied Network' problem. Very frustratin​g.

I have a Toshiba laptop, serial # XXXXXXXXX, it's running Windows Vista 32bit or whatever.
I bought a Belkin Router which has WPA-2 secured wireless internet.
Our Dell desktop computer can connect to the internet with ethernet, but my Toshiba laptop cannot with either ethernet or wireless.
My Toshiba laptop CAN however connect to my schools unsecured network and my parents WPA-Personal wireless internet.
After doing many things that worked for others, (check and uncheck IPV4 and 6, Uninstalling and reinstalling security, I dont have Norton Antivirus, etc) out of frusteration I reinstalled my Atheros AR5007EG Wireless Network Adapter and guess what!? It worked and I got my internet back!...of course after restarting my computer it was once again broken...and now it says something like "connecting is taking longer than usual..." which it never said before....
It says it has 'excellent strength' but it is a 'local access only' connection and an 'Unidentified network'.
Please help me figure this out, I need this laptop for school and I'm behind now.
[mod edit to remove serial number]

When you use the Toshiba Forum, use the model name and not the serial number. Unless you work for Toshiba and have access to the serial number database, it doesn't tell anyone which computer you are using.
If your computer connects with other wireless routers, but not yours, it sounds like a router issue. Drop the encryption on the router and see if that fixes the problem. Maybe the version of encryption you are using is not compatible or its something else entirely. If temporarily getting rid of the encryption fixes the problem, its the encryption. If not, it maybe something else.
See if your computer can see other wireless routers in the area. Always a good sign that the wireless antenna is turned on and sees other networks in the area.
Check your wireless router settings. It doesn't make sense that the computer can't connect up either wired or wirelessly unless the router settings are preventing it. Maybe you have MAC address filtering or a limited number of DHCP addresses. Consider resetting the wireless router back to its default settings and seeing if that fixes it. 

Similar Messages

  • The common Safari network problem - help!

    Hello
    I've been involved in a couple of other posts on this topic, but thought it would be easier to pull out my problem into a topic of its own, as it's still unresolved.
    The problem is a familiar one I think.
    It would be great to have some help and advice as it's driving me nuts!
    Here's the symtoms:
    Safari takes an age to load pages and often gets stuck trying.
    Tellingly, my airtunes stops and starts when I'm playing music over the network to my stereo.
    I've got a MacBook running 10.4.8 with AirTunes.
    So far, I've tried the following:
    - Made sure software is up to date
    - Emptied cache
    - Ran Firefox which is just as slow
    - Repaired permissions using Disk Utility
    - Changeed my primary cabel protocol (airport) to be first on the list and deslected others
    - Removed any superflous wi-fi locations I don't use
    - In the TCP panel>DNS servers, entered 4.2.2.2
    Can anyone think of anything else to try?
    I read something about 10.4.8 having a few network issues, so someone suggested redoing the update, but I'm not sure I understood what they meant about doing things with permissions before and afterwards?
    Can anybody help?!
    Many thanks in advance peeps.......

    Just reporting back on the weekend's testing.
    I ran the Hardware test, but it detected no problems.
    I also changed my network settings to Manual with fixed IP - but it hasn't made any difference at all.
    So I can rule out my netgear router/modem, airport airtunes, safari and my isp (I have exactly the same problems on other wireless networks and also using firefox) and now I suppose my mac's hardware.
    Does that just leave
    1. the configuration of my network and
    2. OSX 10.4.8
    then?
    Maybe I should just wait for Leopard?!
    Do you think it would still be worth trying it out using an Ethernet connection rather than wireless?
    If so, would you be able to give me a step-by-step guide, as I find the Network prefs very confusing.
    Thank you so much for all your help so far, I'm very grateful - I think this is my longest running Mac problem to date....
    I've included some info here from the system profiler:
    AirPort Card Information:
    Wireless Card Type: AirPort Extreme (0x168C, 0x86)
    Wireless Card Locale: Worldwide
    Wireless Card Firmware Version: 0.1.27
    Current Wireless Network: Ben Wireless
    Wireless Channel: 1
    AirPort:
    Type: AirPort
    Hardware: AirPort
    BSD Device Name: en1
    IPv4 Addresses: 10.0.1.2
    IPv4:
    Addresses: 10.0.1.2
    Configuration Method: DHCP
    Interface Name: en1
    Router: 10.0.1.1
    Subnet Masks: 255.255.255.0
    IPv6:
    Configuration Method: Automatic
    AppleTalk:
    Configuration Method: Node
    Default Zone: *
    Interface Name: en1
    Network ID: 65482
    Node ID: 151
    DNS:
    Server Addresses: 10.0.1.1
    DHCP Server Responses:
    Domain Name Servers: 10.0.1.1
    Lease Duration (seconds): 0
    DHCP Message Type: 0x05
    Option Overload: 0x03
    Routers: 10.0.1.1
    Server Identifier: 10.0.1.1
    Subnet Mask: 255.255.255.0
    Proxies:
    Proxy Configuration Method: Manual
    ExcludeSimpleHostnames: 0
    FTP Passive Mode: Yes
    Auto Discovery Enabled: No
    Ethernet:
    MAC Address: 00:16:cb:ba:09:8f
    Media Options:
    Media Subtype: autoselect
    Automatic:
    Active Location: Yes
    Services:
    AirPort:
    Type: IEEE80211
    BSD Device Name: en1
    Hardware (MAC) Address: 00:16:cb:ba:09:8f
    IPv4:
    Configuration Method: DHCP
    IPv6:
    Configuration Method: Automatic
    AppleTalk:
    Configuration Method: Node
    Proxies:
    Proxy Configuration Method: 2
    ExcludeSimpleHostnames: 0
    FTP Passive Mode: 1
    Auto Discovery Enabled: 0
    IEEE80211:
    AllowNetCreation: 1
    JoinMode: Ranked
    MAC Address: 00:16:cb:ba:09:8f
    Built-in Ethernet:
    Type: Ethernet
    BSD Device Name: en0
    Hardware (MAC) Address: 00:16:cb:8f:88:b1
    IPv4:
    Configuration Method: DHCP
    IPv6:
    Configuration Method: Automatic
    AppleTalk:
    Configuration Method: Node
    Proxies:
    Proxy Configuration Method: 2
    ExcludeSimpleHostnames: 0
    FTP Passive Mode: 1
    Gopher Proxy Enabled: 0
    HTTP Proxy Enabled: 0
    HTTPS Proxy Enabled: 0
    Auto Discovery Enabled: 0
    RTSP Proxy Enabled: 0
    SOCKS Proxy Enabled: 0
    Bluetooth:
    Type: PPP
    IPv4:
    Configuration Method: PPP
    IPv6:
    Configuration Method: Automatic
    Proxies:
    Proxy Configuration Method: 2
    ExcludeSimpleHostnames: 0
    FTP Passive Mode: 1
    Auto Discovery Enabled: 0
    PPP:
    ACSP Enabled: 0
    Display Terminal Window: 0
    Redial Count: 1
    Redial Enabled: 1
    Redial Interval: 5
    Use Terminal Script: 0
    Dial On Demand: 0
    Disconnect On Fast User Switch: 1
    Disconnect On Idle: 1
    Disconnect On Idle Timer: 600
    Disconnect On Logout: 1
    Disconnect On Sleep: 1
    Idle Reminder: 0
    Idle Reminder Time: 1800
    IPCP Compression VJ: 1
    LCP Echo Enabled: 0
    LCP Echo Failure: 4
    LCP Echo Interval: 10
    Log File: /var/log/ppp.log
    Verbose Logging: 0
    Built-in FireWire:
    Type: FireWire
    BSD Device Name: fw0
    Hardware (MAC) Address: 00:16:cb:ff:fe:d7:bd:94
    IPv4:
    Configuration Method: DHCP
    IPv6:
    Configuration Method: Automatic
    AppleTalk:
    Configuration Method: Node
    Proxies:
    Proxy Configuration Method: 2
    ExcludeSimpleHostnames: 0
    FTP Passive Mode: 1
    Auto Discovery Enabled: 0

  • Snow Leopard Network Problems

    Hi all.
    I'm setting up my second Snow Leopard Server machine and I'm having the most frustrating networking problems.
    I'm setting up a server with two NICs, and for some bizarre reason connection will NOT work. Trying to ping within the subnet of the inoperative connection produces "no route to host" errors. Switch the IP configurations between the two NICs, and the problem follows the primary configuration. The same network settings work correctly on a different machine, so the problem is definitely software.
    I can't help wondering if this is related to source-based routing in 10.6. But I've tried flushing the routing table to no avail.
    This exact same issue happened with the other Snow Leopard server I set up. After a few days of idling, the problems magically resolved themselves. Unfortunately, I don't have time for that to happen with this server.
    Any suggestions?

    The forums are littered with dual-controller subnet routing discussions; it's a very common issue.
    Easiest fix: don't use a Mac as an expensive (and slow) IP router (or NAT box). Use an external firewall.
    If you really want to wade into IP routing (and do you actually have enough network traffic to warrant lighting up two gigabit Ethernet connections right now?) then poke around for the existing discussions of setting up the ordering of the controllers and establishing subnet routing live and after each reboot.
    I'm probably going to end up writing an article and posting it, as this arises way too often, and folks are understandably having issues with locating the problem given that most (understandably) don't know they need to look for subnets and static routes and such.
    Existing threads including [this|http://discussions.apple.com/thread.jspa?messageID=10688941] and [this|http://discussions.apple.com/message.jspa?messageID=5697532] are reasonable starting points for your dual-NIC quest.
    One other related gremlin that crops up here is the subnet addressing assignments; you'll usually want to have the (co-resident) NICs using addresses in separate subnets or routing can get squirrelly.
    Or plug in the external firewall (which has other advantages) and use it as the router and firewall and NAT box for your LAN.

  • Rogers Network Problem?

    For the past two days my 3G and EDGE has been unstable. I have been constantly getting an error. Safari can't open the page. The error was: "Operation could not be completed. (kCFErrorDomainCFNetwork error 302.)"
    I am using Rogers and since July 11th I've had no problems with my phone. Do you think its a Rogers problem or can I do something on my phone to help?
    Thank you,
    Austin

    Rogers is working on the problem, They haven't given an ETA at the moment (most network problems are resolved within 48 hours of opening a master ticket). Unfortunately, since the problem seemed remote for the first 48 hours, the Ticket wasn't opened until late Saturday Aug. 23 2008. It's a good idea to give them a call, and add your account to the Master ticket. This will enable them to call you for any specifics on your particular problem if the issue isn't fixed past their own resolution and offers some insight into the troubleshooting of this issue. If any refunds, crediting or exchange issues come up, they will be able to refer back to the Master ticket and find who are eligible for this process.

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

  • Verizon Wireless Network Extender and the Terrible, Horrible, No Good, Very Bad Customer Service experience

    It was a dark and stormy night...
    For the past eight years, I had been happy with Verizon wireless service. Great coverage and rarely a dropped call. However, all of that changed when I moved into a lovely mid-century modern condominium. The solid concrete walls and ceilings were blocking my attempts to communicate with the outside world (i.e. order pizza).
    Enter the Verizon Wireless Network Extender! My own personal cell tower! Alas, the VWNE was $250, which was a lot of money. So, being the resourceful recycling advocate that I am, I procured a refurbished one and hooked it up to my network. Then I called Verizon to begin what would soon become one of the Bottom 10 Least Enjoyable Experiences in customer service history (note: obvious foreshadowing).
    The first technician I spoke with was Benjamin, who was actually quite helpful. He noted the VWNE's MAC address and other information before attempting to allow me to access my unit. But he could not. Why? Apparently the unit was still registered to another Verizon customer. He told me the matter would be forwarded to "Verizon Correspondence Support" who would contact the registered owner and get their approval to reassign the unit.
    A week later, I called in to ask about the status of my request, but was told by Darryl (another tech from the VWNE department) that the "Verizon Correspondence Support" department did not exist. Did. Not. Exist? Fine, I explained the situation again, and Darryl eventually told me he would submit a special access form which may resolve the problem. He apologized for the mixup, thanked me for my patience, and told me to wait 24-48 hours for his return call with the results.
    120 hours later, I called to ask about the status of the change access form because I had not received a callback. Michelle, another representative of VWNE support, told me there was no record of this form having been submitted. No. Record...? After which, she made no effort to help me after reading through my transcript. In fact, quite the opposite. To paraphrase...
    "I'm sorry we wasted two weeks of your time leading you to believe we had a solution. Actually, there is no Verizon Correspondence Department, there is no special access form, and no tech will be calling you back. Furthermore, I will not allow you to use our unit because the previous owner hasn't filled out Release Form 27B stroke 6. For all I know it might have been stolen. Perhaps by you? I guess we'll never know for sure, because I won't contact the owner for any reason. In fact, there is nothing I can do to help you whatsoever. But if you like, feel free to throw our network adapter in a landfill. Thank you and have a nice day."
    OK Michelle, here's the deal. I don't even WANT this doohickey. You see, all I want is for my phone to work. That's why I am calling you. To get THIS piece of your equipment working, at my expense, so that I can continue to be a Verizon customer. Seems like I'm doing my part. Why is this so difficult?
    "Sorry"
    Lesson of the story? DON'T BE A MICHELLE. If a customer is in trouble and you can't solve his/her problem, contact a supervisor and work out an alternative. In my example, perhaps Verizon could have provided me with an "official" VWNE? At a discount? Or have a technician sent out to examine the signal? Really, *anything* is better than being brushed off. After being brushed off.
    After being brushed off.

    Follow up: I acquired another VWNE from a local seller, just in case he had to be contacted for the Nuclear Priority Phone Release Code (geez). Ironically, it wasn't necessary, because said fellow had already left Verizon after too many negative customer service issues. Oops.
    The good news is that Verizon was able to properly activate the second unit. I was connected to a VWNE tech named Bertha who was VERY helpful and treated me like a human being. Which made all the difference and restored my faith in humanity. I requested that my story be relayed to upper management so that the hordes of secondhand VWNE buyers wouldn't also get burned by Verizon's "hands off and look elsewhere" policy. Bingo. Finally. Done.
    Epilogue: Until Verizon eases up on their needlessly stringent policy, beware the unchecked VWNE! Be sure to get the MAC code and check it with a local store/tech support before buying it.

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

  • 10.4.7 networking problem - corrupt files when we save on the Xserve

    I have upgrade 15 macs on my network from 10.3.9/10.4.4 to 10.4.7 - the Xserve was upgraded in 10.4.7 before. Now I have a lot of networks problems. When we save big files (quark Xpress 7, adobe illustrator CS, adobe photoshop), sometimes we lost our job, and we can't open the files (incorrect file format, postcript error in the illustrator file, lines in picture files...)
    Sometimes, we can't import PDF in quark files, but, if we copy pdf files from the server to the desktop, xpress accept to import the pdf.
    We also noted problems of refresh of the windows in the finder.
    The Quark technical support is certain that the problem comes from the update 10.4.7 on the desktop computers, and suggest to wait until the 10.4.8 or to downgrad to 10.4.6.
    Have you some infos about theses problems?
    Thanks for you infos

    Chatted with Apple re above. The guy was very patient and as helpful as he could be. Here's what he suggested:
    At Terminal type:
    sudo mdutil -s (drag the volume to here which enters the path)
    You will be asked for your administrator password; enter this and press enter.
    This commands returns the status of Indexing - namely my machine returned the following message-
    Status: Indexing Disabled
    Next I typed in:
    sudo mdutil -i on (drag the volume to here which enters the path)
    Press Enter
    The following message is displayed:
    Indexing enabled for volume.
    Since then the machine has been very active (fans and disk lights) which I hope is it indexing the volume.
    Spotlight works when the specific folder is selected but not across the whole volume. Sherlock still does not find any files. I remain positive, knowing that indexing takes plenty of time.
    Thanks Apple Support for help

  • 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

  • TS3694 good evening i have an problem with my iphone 4 the wif and network cant on now if i tray is showing iTunes i tray to reload the ios is showing an error -1 can you help me

    good evening i have an problem with my iphone 4 the wif and network cant on now if i tray is showing iTunes i tray to reload the ios is showing an error -1 can you help me

    No problem, glad to help!
    Update: my PC USB hub was connected to a USB 3 port, I connected the 30 pin cable directly to my PC, And the restore worked just fine. Restored phone from iCloud backup and seems to be working fine.

  • TS4611 Guys if you have these build: 12E3200 and your wifi is dropping, is not the your mid 2013 macbook air, is your router, I solve it by setting up my time capsule as a new network problem solved

    Here is what I have been doing:
    I got my new macbook air 11" two weeks ago, and have been haven problems with wifi connection dropping, I'm using verizon fioz at home, and their router
    I also have a time capsule not set up as a network just join it to my current one.
    After looking online all these days, I though, maybe is the verizon device that is updated..
    I then reset the time capsule, created a new network
    connected my system to the time capsule network, and there it is
    DONE, everything works now.
    So if you are haven the same problem,, that is the fix
    hope that helps.
    Oh  before I did these I try everything, the wifi update from apple don't work it keeps dropping it
    I try everything, so don't and delete the system as some people have done, I read somewhere.
    try my fix hopes that works.
    Message was edited by: rawreviewer

    I have seen lots of issues on Yosemite with Wifi (and have been having issues myself), but yours seem different. It is a pretty new computer, have you tried taking it in under Applecare (if you live somewhere this is convenient)? Maybe you just got a defective wifi card.  I won't defend Apple over this wifi mess, because it really is terrible, but your issue seems not the same as the ones I've read about while researching how to fix mine (unsucessfully....).

  • TS3694 Why can't I update my iPhone 4 to iOS 5.1? Every time I try it gets all the way done downloading it; however when it's processing the file the page tells me "There is a problem downloading the software for the iPhone. Network connection timed out.

    Why can't I update my iPhone 4 to iOS 5.1? Every time I try it gets all the way done downloading it; however when it's processing the file the page tells me "There is a problem downloading the software for the iPhone. Network connection timed out. Make sure your network settings are correct and your network connection is active. or try again later." and next to the file it has err = -3259. I have tried this 17 times and it won't work. My iTunes is completely up to date. I have made sure that my connection is fine and I have tried turning my firewall off with no avail. This has happened to me before but usually the update will go through after 2-3 tries, never to this extent. I don't know what to do. Help!

    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

  • Does anyone has a problem with the screen of the new ipad? (there's a part of the screen which the color in it is "very" bright) and when I move the aluminium part of the smart cover when it's attached to the ipad the colors change!! Help!!!

    Does anyone has a problem with the screen of the new ipad? (there's a part of the screen which the color in it is "very" bright) and when I move the aluminium part of the smart cover when it's attached to the ipad the colors change!! Help!!!

    I'd take it into my local APple store and have them look at it. There may be something wrong inside your device.

Maybe you are looking for