ATV Kills My Network Connection

Everything has been working fine until all of a sudden. Now when I launch iTunes and i begins to synch with ATV it knocks out my wireless connection. Any ideas? I maintain the connection UNTIL itunes synchs with ATV.

UPDATE:If I turn the security off on my router it works-obviously not a long term solution. I was using WPA Shared Key security. Any ideas?

Similar Messages

Latest Apple TV Kills entire network connection

I was super excited to purchase my first Apple TV, until I hooked it up. I have found if I use it wirelessly, it will kill my entire network within a short amount of time. 10-15mins. After that time, no computer can access anything on the internet, and the Apple TV will not find the library again after I finish watching whatever was playing. But, everything runs smoothly until that point. It finds the library, internet access through ATV is fine, remote app on my iPhone works fine, it's beautiful! …for a short time.
Through troubleshooting that issue, I found if I connect via ethernet, it will not find my iTunes library at all, but it will connect to the internet just fine. ????
I've found a few random things on the web related to this, but they are all in reference to old ATV models, and I cannot seem to come across any posts mentioning my exact problem. So far, I've tried doing the following on both wired and wireless connections:
-made sure my Linksys router has the latest firmware version available
-tried increasing the client lease times on the router to roughly 1 week.
-tried manually configuring the ATV IP to maintain a static address, but it still kills the entire network when running wireless, and will not find the library when wired in.
I've never had problems with my network before; it's been running smoothly for 5 years. I've also been streaming Netflix to my LG Tv for about a year now with no issues. I am totally happy to invest $99 in an ATV-love the concept, love the convenience. But if Apple has something going on where it will only work with an airport extreme, I am not happy with investing $278 in an apple tv when my current wireless setup works just fine. Does anyone have any ideas on what I may be doing wrong or how this can be resolved? I really do love the idea of having access to my media wirelessly, and would hate to have to return the ATV.
Tech details:
Latest little ATV model, library hosted on a mid 2011 MBPro Core i7 running OS 10.6.8 with latest iTunes version. My library has about 65gigs of music and about the same in movies. We have that MacBook and 1 PC runing on the network. I am using this Linksys router: http://homesupport.cisco.com/en-us/wireless/lbc/wrt54G
Many thanks in advance to anyone who can help!

Very similar situation here. My ATV3 is connected via WiFi, but it loses its network connection if the following two conditions are met: it sleeps, and my Aiport base station is turned off any time afer the ATV sleeps. When I power up the Airport again, the ATV does not find my network without either restarting or selecting the network manually from a list of nearby networks.
In other words, sleep is OK only if the network is never powered off.
-dan

Get File/Put File Kills Home Network Connection

Recently encountered a problem with Dreamweaver CS5 where when I try and put or get multiple files to my server, I lose internet connection. I don't just mean wireless connection, but my entire home network fails. I have to reset my router to regain connection only to have it happen again. I have tried hardwiring the laptop to the router, same thing. I have tried hardwiring the laptop to the cable modem, same thing. When the network fails, my PC that is hardwired to the router also loses connection. I am currently using the newest generation 17" MacBook Pro, 2.66GHz, 8 GB, with Mac OS X 10.6.4, running Adobe Creative Suite Design Premium CS5. My home network setup includes a Comcast cable modem, hardwired to a Linksys router that provides my wireless network as well as a hardwired connection to my PC. I can connect to my server fine and upload and download multiple files with other FTP programs such as Filezilla, but whenever I use Dreamweaver it kills my internet connection every time. I have tried to find other information on this and have only come across a few others who are experiencing this issue and can not find a solution. Please see the following links:
Seems it was a CS4 problem too: http://forums.adobe.com/message/2448960#2448960
Another person thinking it was a Windows issue: http://social.answers.microsoft.com/Forums/en-US/w7programs/thread/88a38e07-f050-4800-a1f7 -7b0570f88eaa
Between these threads and my problem I have narrowed it down to a Dreamweaver issue but can not find any solutions besides using another FTP program which greatly hinders my workflow. Any advice would be appreciated.
Thanks,
Brian

the problem for me was my network cards driver. I dont know how mac handles drivers but when i changed back to the previous version
of the driver it started working fine. Before that i had to restart my network when i tried to put a big file with DW.

10.5.6 has killed my network connection

10.5.4 Leopard upgrade completed yesterday and found that it wouldn't recognise the WEP passowrd to my network. Had to manually "assist" for it to find network, annoying but at least it worked.
When it persisted I called Apple Care today who suggested various things which didn't work and concluded by suggesting I upgrade to 10.5.6 as "lots of this sort of issue have been ironed out'. You guessed it...WORSE, It can find the network but just will not connect to it. despite resetting-up the connection etc etc. Anyone else suffering from this. known issue?

Did you use the manual combo update?

ATV keeps disconnecting and losing network connection

I konw this has been posted on seval discussion boards, but the answers are all over the place. I have been watching Netflix over the last several weeks and noticed that almost routinely my ATV will stop playing and go back to the home screen. Sometimes I am able to resume where I left off but more often it loses my network connection. I have to unplug ATV or go through the menue and reset.
I have not had this problem until recently. I have done all of the disconnecting, checking cables, restarting router, etc. Nothing seems to work. I even cancelled my Netflix subscription because I thought it was their issue. However, I have learned that it must be the ATV itself. I love my ATV, but I can't seem to figute out why this is happening. I don't have any other issues with WiFi in my house or with any other devices.
Any ideas if this is a software update issue? I did read that people were having issues after the latest software update.

We've had our ATV for about a year and it's always worked perfectly. But every day for the last five days it has needed to be reset each day. Doesn't matter if we are trying Netflix, YouTube, or Podcasts it will say "can't connect to server, try later." So we will either unplug it and plug it back in or select reset from the general menu then everything works again. Can't figure out why it's doing this. All software is up-to-date.

Going to cabin Th, want to take ATV. Can I play w/o network connection?

I'm heading off for some isolation time tomorrow and had a last second idea of taking my ATV with me. I have a macbook and Touch (2?) that i am taking. Can i control/run the ATV w/o a network/internet feed? I just tried to here at home with no success but was wondering if there were a setting i can use to do this.
Thanks for any help.

If u want to watch the movies on a TV, then just take the ATV and the little remote that came with it and u will be good to go. If u don't have a TV where ur going and u use ur MacBook to backup all the content in ur ATV, then all u need is the MacBook. U would need a network connection if u were to do any syncing to the ATV, but if all u want is watch movies that are already in it, then ur cool.
Out of the subject here, u can rent movies on the ATV right now that u have a network connection and watch them where ever u go. Just make sure they download 100%. U provably already know this though.

ATV looses network connection if PC reboots or iTunes closes and reopens.

ATV looses network connection upon iTunes closing (i.e computer turning off or going to sleep.) I'm then required to re-input the network password (p.i.t.a.) every time I come home from work, or the power surges, or iTunes closes, etc.
Thoughts?

Hi Lucy,
To address the suggestions you made:
There's too much code, performance needs to be
improved. - Does anybody know of useful utilities to monitor cpu
performance as a sort of watch dog.
There is a software package called the Execution Trace Toolkit you can use to monitor the performance of your Real Time applications. If you have access to this software through a developer suite or a site license it would be worth installing that.
If not there are a number of other things you can try first.
The network or vi server is shutting down - Again, I'd appreciate some help on how to monitor this.
To determine if the problem is caused by the network you should connect to the cRIO with a cross over cable and see if you see the same behaviour. This will help determine if the problem is down to the network or the cRIO system.
Once you've isolated the source of the problem (ie the crio or the network) we can investigate the cause and hopefully come up with a resolution.
Kind regards
Sarah
Applications Engineer | National Instruments | UK & Ireland

Itunes 6.0.1.3 is killing my network!

The last time I updated all my podcasts was 12-8-5. I had not run Itunes since then. I fired it up this past weekend and something really strange happened.
It was unable to update any podcasts. Also, my laptop had disconnected from my wireless network. I closed Itunes but my system still was unable to see any wireless network. I rebooted and was able to connect again. I then left the wireless properties open and started Itunes. My wireless connection began to drop in speed over the course of 1 minute from 54 -> 36 -> 24 -> 11 -> 1 -> 0 Mbps when it again disconnected and would not see wireless. I rebooted and started all over again. This time I closed Itunes before it killed the connection and within 1 minute my speed is back up to 54 Mbps.
This is also happening on my hardwired Desktop! As soon as I fire up Itunes, the lights on my switch and router and every AP start flashing like crazy! I am talking about three switches and a wireless bridge. The activity lights on all devices go crazy until I kill Itunes on my desktop. As soon as I do, the activity stops, but I am forced to reboot all my network devices to get the network up again.
No, I am not the only person in the world seeing this behavior. I just listened to Leo Laporte's KFI Tech Guy podcast from the first week of December and a caller was describing the exact same issue:
http://leoville.tv/radio/ShowNotes/Show201#toc3
I have also found another reference to the same thing here:
http://forums.macnn.com/archive/index.php/t-246946.html
And another here:
http://groups.google.com/group/microsoft.public.windowsxp.networkweb/browsethread/thread/12be291b47a65868/04144bc0accb23f8#04144bc0accb23f8
Basically, running Itunes kills my network!
I have turned off all automatic network functions in Itunes, like automatic podcast updates and search for shared music. Turning off search for shared music seems to have solved the need to reboot every network device in my house, but running Itunes still causes the death of my wireless connection on my notebook.
I can only postulate that this MUST be the result of a recent XP update since Itunes was working just fine a few weeks ago. To test this theory, I will be doing a parallel OS install of XP SP2 on my laptop with no additional updates and Itunes the only installed application. I might try doing this in Virtual PC first, but I am not sure I could trust its results.

OK,
I just installed Itunes 6.0.1.3 on a fresh install of XP SP2 in Virtual PC.
Simply starting Itunes, No subscriptionsn no podcasts to update, and the same results.
Within 1 minute, the network connection on the VPC was dead and reported limited or no connectivity. Before it died, the wireless on my laptop began to decrease in speed. As soon as the network connection in VPC died, it began rising again. As with my desktop, my network devices activity lights lit up almost solid! The ethernet bridge that connects my ReplayTV to the network went solid on activity and my Replay was knocked off the network. It would appear the 6.0.1.3 is spewing a bunch of garbage on the network to the point that it is killing all my devices.
Whenever Itunes is open on any system on the network (In its default config), ALL devices lose network connectivity.
Now I will try an older version on the virtual PC and see what happens..
Stephen TN

Mac Mini *half* loses all network connections

Cheers folks, new one on me. I have a Mac Mini 2.26Ghz Core 2 Duo. It's running a fully-updated 10.6.8. It's connected via ethernet to an Airport Extreme which is extending an 802.11N network from another Airport Extreme elsewhere which is connected to the router. The network is set with IPv6 *off* and is configured to run over Ethernet normally (this is because a wired-only NAS is connected to the same Airport Extreme as the Mini).
Here's the symptom, and it's an odd one for me: Every couple of days, the entirety of the Mac OS X layer (not the BSD layer) will lose network connectivity. More specifically:
No web browser will work ('Not connected to the Internet').
Home Sharing, served on this Mini, will cease to be visible from elsewhere in the house (AppleTVs lose it).
No internal services can be reached by name, either DNS or BonJour.
The App Store says 'can't connect.'
iTunes will say it can't connect to the ITMS.
This is true on Ethernet *or* on Airport (the Mini usually runs on ethernet alone with AirPort off; bringing up Airport once this has occurred doesn't seem to help anything).
Running the Airport Utility, it sees *no devices* (there are 4 on this network)
BUT!
If I go into the Terminal, I can not only get clear network traffic anywhere I want at the TCP layer, DNS seems to work as well. So the following is true also:
'ping cisco.com' (or any valid DNS name) works fine - resolves DNS, pings.
'traceroute cisco.com' works fine - resolves DNS, traceroutes out across the internet, no problems.
'ping <IP address of NAS>' - works fine.
'dig <name>' - works fine.
pinging the gateway (the router airport) works fine.
Also:
Other Macs in the house (on wired OR wireless, connected to any of the AirPorts including the same one as the Mini) work fine.
Other Macs can see the NAS connected to that same AirPort fine.
iOS devices in the house connected to any AirPort work fine.
netstat -r shows what look to be proper routes - i.e. the default gateway is the router address (10.0.1.1) and the route to 10.0.1.1 is shown to be the MAC address of the router's Ethernet interface (anyway, as I mentioned above, network stuff from the shell works fine<!?!??!
Steps tried:
Turning off ipv6 - nope.
Applying all firmware/software updates (OS X 10.6.8) - nope.
Tried manually setting DNS to Google public DNS servers - nope. Those work fine, and are still set when the network drops out, and then don't work, nor does setting new DNS servers in the Network prefpane.
Logging out/back in - nope.
Restarting the computer: YES. This works, all three times this has happened (all this week). Serious PITA.
I tried going through the system log, but I don't see anything notable that changes or is logged when the network connection drops.
Every time the connection has stopped working, the computer *has* slept at some point since it was last known working, but if I sleep the computer manually, everything seems fine.
.....waaaaaaaah! Help, this one is making me crazy. :-) Thanks. I'm terminal-savvy, and fairly OS X savvy.

I still have this issue. About every one hour - two days the DNS layer will stop working and only a restart will fix it.
Killing mDNSResponder only resolves the issue sometimes and even then for a few seconds.
I have now found and created the following bash script, to see if this will be a more reliable non-restart fix that killing mDNSResponder in the terminal:
#!/bin/bash
#Script to unload and reload mDNS as it is a bit crappy
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
echo "mDNS unloaded"
sleep 5
sudo launchctl load /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
echo "mDNS loaded"
sleep 5
echo "Hopefully you can get on with browsing again"
I saved the above as mdns_reload.command, and then in Terminal ran "chmod u+x mdns_reload.command". This makes the script executable.
The next time the problem occurs I am going to test how good this script is as a resolution.
The second time the problem occurs I am going to try the following, from a different thread from 2011:
I don't know if anyone will be helped by this, but the Macbook problems connecting to the internet are directly related to DNS issues. I discovered this after an upgrade to the OS X Lion preview.
The symptoms are as follows: a macbook (pro, mini, etc) can get an IP address from a DHCP server on any given network, but can not connect to the internet, even though other computers on the same network have no issues. If this sounds familiar, read on.
The problem is not related to 3rd party products, routers, Airport settings, locations or public vs private DNS servers, and you don't need to reset SMC or PRAM.
You will need to use terminal and you DO NOT want to use disk utility to repair permissions.
The most direct way to fix this is to copy the com.apple.mDNSResponder.plist and com.apple.mDNSResponderHelper.plist files from an internet connected Mac into your /System/Library/LaunchDaemons directory.
(You should know that it probably doesn't matter what version of OS X you have or the other Mac has, you just need the files.)
Next you will need to change ownership of the files just copied (ex: chown root:wheel /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist and chown root:wheel /System/Library/LaunchDaemons/com.apple.mDNSResponderHelper.plist)
Then, you will need to set correct permissions (ex: chmod -R 755 /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist and chmod -R 755 /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist)
The last thing you'll want to do is to verify that the ownership of the files copied is set to system (and maybe wheel) using "Get Info." (Conversely, you can use ls -l /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist to verify owner and permissions.)
You should not have to restart to connect immediately to the internet.

Losing network connection in 10.5.4

I have a recent problem with my internet connection. I have used the same computer (macbook) for 18 months in same address without other major problems; only change i can see have been the updates in the os X.
I'm writing to these forums only because i think i have excluded other alternative explanations and i'm pretty sure the problem must be in my computers settings.
The problem appeared as I re-activated my broadband connection and tried using torrent softwares such as Transmission and Vuze. My connection dies several times in hour when i am using such programs, all traffic in and out from the computer is brought to 0. obviously all programs are affected and no internet traffic occurs. I have sought help from the program forums, and have attempted to make sure all possible settings are right and have tried the nicest possible settings to the network (i.e. small number of connections, small traffic in and out although in the long run that would not really be a good solution). I have used same programs earlier, with the same computer and internet connection but under OS Tiger at much higher speeds for weeks in a row with no problems whatsoever.
When i run network diagnostics, in 9 times out of 10 it claims everything is just fine, sometimes the internet and server light are orange.
Also in about 9 times out of 10 if i just wait for a minute, everything just heals itself and the traffic gets back to normal.
If i disconnect/restart my router/airport express or modem , the network recovers quickly and i get good traffic, for a while.
Just to note, i have tried connecting the modem directly to my computer and the same exact problem exists.
Initially i assumed this would ISPs fault. I have called them twice now, at times when my internet died completely without recovering, and they claimed everything was running just smoothly from their end and according to their information everything up until my modem is just fine; i should be getting nice network traffic.
This leaves the fault to be in my modem or in my settings. I'm going to take the modem to be tested, but of course like to try to adjust my settings seen that lots of people appeared to have problems with leopard network settings.
I made the mistake of trying some quick fixes in these forums without really fully understanding what they do. removing the WPA2 security for a while didn't do anything. typing sudo sysctl -w net.inet.tcp.rfc1323=0 at terminal didn't help either, in contrary now it appears safari and firefox are loading much slower for me. i hope that goes away after a reboot.
In the DNS section of network settings i only see one address, in grey. I asked my ISP to send me their recommended numbers since that was advised in another forums.
the problems are not as apparent when i am not using torrent programs, but then again i am not really monitoring my net traffic as closely at those times. Also i have previously used such programs with no problems, using older OS X versions.

It appears the problem appears only when using torrent software.
There is a lot of discussion on different torrent software forums about this, and directions on how to get around this issue. However with my skills I only managed to get Vuze to work properly while killing the network access from all other application. So i just went back to default settings.
I give up for now, I'll wait until Apple releases OS X update that works together with these programs (like it did in tiger and earlier versions..) or if it's even possible, one of the programs finds a way to get around this issue.

Losing network connection when loading new firmware from iTunes (or syncing

Noticed this when loading 1.1.1 weeks ago and now 1.1.2. Several times during the download/installation process, I lost my network connection. Rebooting the PC restored it, only to have it go down again, requiring another reboot. Required several PC (not iPhone) reboots to be able to complete the process. This happens only during this process -- I otherwise never lose my network connection and always enjoy super speed. Paid it no mind and dismissed as a fluke during 1.1.1 upload, but was surprised to see it again this time. In both cases the final download and install worked perfectly. It's just a time-consuming hassle -- kinda weird -- thx much in advance for any clues about this...

It appears the problem appears only when using torrent software.
There is a lot of discussion on different torrent software forums about this, and directions on how to get around this issue. However with my skills I only managed to get Vuze to work properly while killing the network access from all other application. So i just went back to default settings.
I give up for now, I'll wait until Apple releases OS X update that works together with these programs (like it did in tiger and earlier versions..) or if it's even possible, one of the programs finds a way to get around this issue.

Problem with Virtual PC and Network Connection - VPC gets disconnected

Hi,
I've been having a few problems with a virtual computer and its network connection. I've set up a few computers the same way over the years and they all work fine except this one. We use the Virtual PC and XP mode to access our data from an older
program. The databases are on a server, which are accessed as a mapped drive. Every once in a while (with no particular pattern, sometimes it doesn't happen all day, sometimes it happens every 5 mins), the VPC gets disconnected from the network,
my program returns a file read error and then everything is frozen. When I try to ipconfig/release and renew, it releases correctly then it won't renew. I need to shut down the VPC from the Win7 task manager and even so, it doesn't shut it down,
even when I try to kill the vpc process. The only way it'll come back up is if I restart the computer. The network connection on the Win7 computer doesn't do that.
Is there anything I can do to fix this ?
Thanks,
Melanie

Hi,
Does it become more stable now, actually, I'm afraid that this issue is not related with the drive letter or name. Since you're using bridge mode, the I would suggest you use NAT as a test, it is the default network configuration, which allows the VM
to leverage the external TCP/IP network connected to the host. This is very useful if you regularly move the host computer between different network configurations. NAT is the preferred networking option when there is a shortage of IP addresses, a need to
ensure the VM’s IP address is not targetable from an external network, or a need for connecting using WWAN.
Yolanda Zhu
TechNet Community Support

WTR110 - Connecting from Vista or Windows 7 card kills not only connection but the router!

Hi,
I never had problems with my XP laptop to connect to my wireless network on my WRT110 (using Intel Centrino) but my other laptop, a Vostro 1000 used to work when it had Windows XP, now that I've installed Vista it doesn't work anymore, I always get limmited connectivity, not only that but it also drops the internet connection on the router, all other computers wired or not wired loose internet connection, the router also becomes inacessible by wire. I recently installed Windows 7 on a pc that had XP and a Netgear WG311T and the same problem happens, it not only does not acquire an address but kills the router connection, how is that possible?

Would suggest you to try upgrading the firmware of the router & then reset the router in such a way that power light is blinking on the router. Also, try doing a complete network power cycle ie., unplug the power cable from the modem & from the router. Then, plug the power cable to the modem first once the lights are solid green you could plug the power cable to the router & then your issue will be resolved.

Kernel Panics during system boot, and no kind of network connectivity

I've tried quite a lot of things here, so please read them all before you suggest something - and thanks for taking a look at my question (-:
I recently got my Mac Pro back from the AlaskaMacStore (not an actual apple retail store, and they aren't very good at that), having brought it in for loss of FW800. They sent it to Apple, and I received it back, supposedly with a new motherboard - and my FW800 working. However, it proceeded to kernel panic (complete visual system freeze, not greyscreenofdeath - oddly enough, iTunes would never stop playing during them) at least once a day after that.
Not wanting to deal with them again, I just used it like that and put up with it - but soon enough, I lost any sort of network connectivity as well. With AirPort connected to my Time Capsule's network (which worked fine on my Macbook Air and iPhone and various other devices), I was being told "...Self-Assigned IP address, and thus may not be able to connect to the internet...". Even connected directly via Ethernet to the Time Capsule, or directly via Ethernet to the cable modem, or directly via Ethernet to another Mac, or connected to another Mac's ad-hoc network, I could get absolutely no network communication going on of any sort.
This was too much for me, as all of my work requires frequent and heavy internet access, so I gave in and took it back to the local mac store equivalent - they charged me 100$, and kept it two days, just to tell me they 'couldn't reproduce the problem'. I took the Mac Pro to a friend's house, and went through the same tests - connected to his modem, with his Ethernet cords, and to his wireless and other macs. Same deal, no connection or indication of a networking being connected beyond that blasted 'self-assigned IP' in Network prefs.
Having no desire to be defrauded by the local fools again, I decided I didn't really have anything important on my internal hard drive, and decided to wipe the internals and re-install Leopard. My horrible luck continuing, I found my only Leopard disc to be cracked, prompting me to drive out and purchase a new one. Inserting this into my Mac Pro's drive, I found myself faced with yet another horrible problem.
During the boot to the Leopard DVD, the grey loading screen (with the apple logo and the spinner) simply froze with the spinner pointing left. I left it for a while, expecting this to be part of what I'd previously experienced with the slow boot-from-DVD on a Macintosh... but after 30 minutes of waiting, I got quite worried, and booted back into my normal OS by holding down Option and selecting my RAID.
Now, note this for later - it booted absolutely fine, and though I still had no network connectivity, the system had no problems. I changed the startup-disk to my RAID and then back to the Leopard DVD, naïvely thinking this would solve the problem, and ran into the same problem after restarting and booting to the Leopard DVD again.
Dismissing this as a optical drive problem (haven't had occasion to use optical media in nearly 3 years, don't really trust it in general), I booted the Mac Pro into Firewire Target Disk mode, and connected it to my Macbook Pro, and then booted the Macbook Pro from the installation DVD. Again, note carefully here - there was nothing wrong with the DVD itself, as the Macbook Pro had no trouble booting to the DVD.
I used Disk Utility to preform some planned modifications to the internal drives of my Mac Pro (erasing my previous inefficient RAID setup in favor of a new, faster (but less secure) RAID0 striped setup for my main two 1TB drives), and then proceeded to install a fresh Leopard onto the newly minted RAID. I usually cancel the 'disc checksum' that the Leopard DVD runs on itself, not really worrying about it, but in light of recent possible problems with the DVD, I went ahead and let it run - no problems, it completed and went straight into the normal install.
The install itself completed in a timely manner, and my Macbook Pro re-booted automatically, to the newly Leopard-ed RAIDed internals on the Mac Pro. It booted to the new install without a hitch, played the Leopard intro video, and continued to the setup cube. I opted to shut down (by hitting command-q and selecting the shut down option), so I could set it up on the Mac Pro instead.
Surprised was I, when I experienced the same grey loading screen freeze on the Mac Pro, booting to the newly clean install on the new RAID, that I had seen trying to boot to the Leopard disc. Worrying that my Leopard disc was, infact, corrupted in some way, I tried placing the Macbook Pro into firewire Target Disc Mode, and booting that drive over FW800 on the Mac Pro. Same freezing problem occurred.
Well, now, the only installation that HADN'T kernel panicked on boot was the old install, and that had been erased for the new RAID configuration, so I was left without a way to boot to a working install and test things from the Term. This left me with Single User Mode, which I immediately booted into.
Interestingly enough, there was no problem booting into Single User Mode - so I poked around a bit before mounting, and I had seemingly fine access to the entire filesystem of the new Leopard install, and nothing looked screwed up to my (albiet untrained) eye. After mounting and continuing the boot, it froze - but since this was verbose SUM, and not simple normal boot, I was able to see exactly where it froze: something about 'mDNSResponder starting', and then no input or output was accepted, leaving me assuming it had kernel panicked again.
To test this, I again attempted to boot from the Leopard DVD on the Mac Pro, this time in verbose startup mode, and watched it freeze up at exactly the same point. After a little googling, I found some suggestions to disable the launchd plist for mDNSResponder - I tried SUM again, and did so, then continued with the boot. This time, there was no output relating to mDNSResponder, so the launchd change had worked; however, it still froze - this time, right after three lines, first something along the lines of 'Login Window Application Starting', and then two lines printing Ethernet IDs of some sort. After those Ethernet related lines, it again froze.
What with the DNS and Ethernet bits showing up in the freezing, I was getting worried this was still tied into my NIC in some way, so I unplugged my Ethernet cords and tried the exact same boot again, and again disabled mDNSResponder. This time the only sensible thing before the freeze was the 'Login Window Application Starting' line, which seemed perfectly normal. I doubt there is/was anything wrong with that, so I'm assuming there's still some networking-related process freezing/panicking the computer, and it just doesn't happen to log in a visible way during startup.
Does anybody have any suggestion as to what such a process might be, and how I can at least pause or kill it from SUM, so I can at least finish booting the computer?
If I can't figure out a solution to this, I'll have to buy a new Mac Pro tomorrow morning... I have very, very pressing matters that can't wait for a new Mac Pro to ship, nor can they wait for me to ship this one to Apple and back (I live in Alaska, we have at least a weeks wait if nothing is seriously wrong when sending an Apple product in for repairs on our own), and nor can I wait 2 days for the local Apple store to tell me there's nothing wrong with it and then have to wait another week to, again, send it to Apple myself. I don't want to have to shell out for a new, expensive computer when there's a (most likely) perfectly good one sitting here... so any help would be MUCH appreciated.
If you've read this far, phew, you deserve a cookie. That was one... long... post.
(If you care, this post was cross-posted to my blog, at http://blog.elliottcable.name/posts/macpro_epicfail.xhtml)

Talk about bad luck.
The point at which the system "freezes" with the gray spinner (and just after the login window app starts) is right about the point the accelerated drivers should kick in for the video card.
So a couple things could be going on.
1) bad video card dragging down the bus
2) The system board is fubar - this I think is likely - issues with onboard ethernet, and whats seems to be video card related.
I would hazard to guess that the PCI-express bus has something wrong with it, ethernet and video live on the bus, SATA, and USB live in the southbridge.
So, looks like a trip to a certified apple dealer/repair center is next for your Mac Pro - probably for a new system board, again?
Something tells me that your system really didn't get to Apple for a new board.
You can verify by looking at the serial ID tag on the system board, note the rev and serial # before and after such repairs.

No more network connection

Hello,
recently -- after checking the arch front page for important notes and troubles I might encounter -- I ran a full system upgrade, which I do roughly every two weeks. As usual, I expected a flawless update without problems. First, it seemed to be like that.
However, after rebooting I realized I had no more network connection. I have used a simple, wired network setup.
Now I'm a little embarrassed, because with the help of the wiki I was able to maintain my arch box for years now and also had no problem with the "bigger" changes in the last few years, but now I'm clueless.
I did go through the networking sections in the beginners' guide, but to no avail unfortunately.
What information can I provide here so that anyone could help me?
Something that seems not important to me, but maybe I am wrong about that: I uninstalled the kdeplasma-networkmanager package right after the system upgrade.
For the time being, I do not need wireless connections or something, I only want to establish a wired internet connection.
I can provide logs and everything, but do not know which ones are relevant. Can you please help?
(Other than networking, everything worked fine after the upgrade)

Right after rebooting it shows as follows:
[root@argos ~]# dhcpcd -d
dhcpcd[2955]: sending commands to master dhcpcd process
dhcpcd[2955]: send OK
Then I killed the dhcpcd process, restart it and repeat:
[root@argos ~]# dhcpcd -d
dhcpcd[3089]: version 6.3.2 starting
dhcpcd[3089]: wlan0: up_interface: Operation not possible due to RF-kill
dhcpcd[3089]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
dhcpcd[3089]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
dhcpcd[3089]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
dhcpcd[3120]: wlan0: starting wpa_supplicant
dhcpcd[3123]: wlan0: failed to start wpa_supplicant
dhcpcd[3124]: wlan0: Successfully initialized wpa_supplicant
Line 1062: unknown EAP method 'SIM'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1062: failed to parse eap 'SIM'.
Line 1065: failed to parse network block.
Line 1072: unknown EAP method 'PSK'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1072: failed to parse eap 'PSK'.
Line 1076: failed to parse network block.
Line 1108: unknown EAP method 'IKEV2'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1108: failed to parse eap 'IKEV2'.
Line 1111: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.
dhcpcd[3089]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
dhcpcd[3089]: DUID 00:01:00:01:1a:c3:1b:b4:48:5b:39:9b:25:f5
dhcpcd[3089]: eth0: IAID 39:9b:25:f5
dhcpcd[3089]: eth0: soliciting an IPv6 router
dhcpcd[3089]: eth0: sending Router Solicitation
dhcpcd[3089]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[3089]: eth0: discarding expired lease
dhcpcd[3089]: eth0: soliciting a DHCP lease
dhcpcd[3089]: eth0: sending DISCOVER (xid 0xdb5a0f53), next in 4.1 seconds
dhcpcd[3089]: wlan0: waiting for carrier
dhcpcd[3089]: eth0: Router Advertisement from fe80::2665:11ff:fe00:5316
dhcpcd[3089]: eth0: adding address 2a02:8070:d187:b500:4a5b:39ff:fe9b:25f5/64
dhcpcd[3089]: eth0: vltime 7200 seconds, pltime 3600 seconds
dhcpcd[3089]: eth0: adding route to 2a02:8070:d187:b500::/64
dhcpcd[3089]: eth0: adding default route via fe80::2665:11ff:fe00:5316
dhcpcd[3089]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' ROUTERADVERT
dhcpcd[3089]: forking to background
dhcpcd[3089]: forked to background, child pid 3178

ATV Kills My Network Connection

Similar Messages

Maybe you are looking for