10.4.8 Killed my network stuff'ns

I can get online on our network, but i cannot ssh terminal server into my linux server, i cannot get software updates from the apple (get the -1001 error), and certain other applications cannot update any longer.
I cannot also not SFTP into my linux server.
all tend to be timeout errors. didnt happen till 10.4.8

Ron, is this on a work / organisation network or a home one? If work related, have a word with IT and see if they have switched off firewall access to ports 133 - 135. Apple SU uses these ports.
best wishes
Andrew Platt

Similar Messages

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

How can I transfer my iTunes library from my laptop to an external drive connected to my time capsule? I want to be able to access the music from several devices by wifi and am a newbie to network stuff.

I have a 1TB Time capsule, I would like to attach a USB drive to the Time Capsule and transfer my iTunes Library to it so I can run itunes from wifi. I am new to network stuff. My current iTunes library is on a USB drive velcro'd to the back of my Macbook - rather inconvenient, the USB port is loose. The music files are external but the library files with ratings/play counts are in the iTunes folder. Advice please? Be gentle and assume I know nothing please!
Thanks
scott

Setting it up the way you have with the library on the internal and just the media on the external makes it a lot more tricky to move things around. If it was all on the external you could do in the time it takes to copy the files plus about 20 seconds.
You can use the same library file, except in that file are references pointing to the media files on the USB drive. Are you planning on doing this with the same USB drive that you are using right now>? It is possible it may work. If the configuration is that you have SongA on USB drive Fred, as long as the drive remains named Fred then you should be able to move it to a different point of attachment. If you are planning on using a different USb drive you can try renaming the new USB drive to the exact same name as the existing one and maybe trick iTunes into not noticing the difference.
This is where having as much detail as possible when posting an issue is helpful so we don't have to consider every possible configuration.

ITunes kills my network

Hi, I've seen a number of threads in the past about iTunes killing the network. I'm trying to download the latest firmware for my iPad (4.3.2) but I am unable to do so as my network dies. It only happens when I use iTunes. I am on an ADSL Router, and it seems that it kills my connection between my PC (10.1.1.3) and my router/gateway (10.1.1.1) As I type, my PC has been happily pinging the default gateway for 30 minutes now, but as soon as I try to download apps or the firmware, anytime between immediately and 60 seconds, it starts displaying "General Failure" and "Request timed out" randomly until it dies. I then get random replies of "Reply from 10.1.1.3: Destination host unreachable." The firmware won't allow me to resume the download after it dies, which make it that much more difficult.

I have also tried updating from version 7 to 8 Itunes. This did not fix the issue.

Is Killer Network actually Killing My Network?

Hello All,
I have been running into issues this past week after a recent computer build. One of my computers either is having Video Card Issues, or Network Issues.
I have a "Lan Center" that I have built over the years in my basement. Ever since the early Beta Counterstrike days I have always ran more than 1 computer in my household. Most of my friends are broke hippies, but I work in IT and enjoy playing once in a while.
The Game : GTA V for PC
The Problem : When going high speeds in vehicles, or when in big online lobby's. The framerate either drops (I don't know how to monitor FPS on this game as of yet) or my network is dying. On the other two PC's when in a private lobby, I can watch this PC lag in game. It will start off fine, but jump in a Bugatti, and it all goes to hell.
The Hardware :
Computer 1 -
CPU -i7-5820K (No OC)
Video - EVGA GTX 970 (No OC)
Mobo - ASRock X99X
HDD - Samsung 850 Pro 512gb
Ram - Crucial 16GB DDR4
PSU - Corsair AX760
CPU Cooler - Corsair H75
Sound - Creative SB ZxR
Case - NZXT H440
OS - Win 7 64bit Pro
Computer 2 -
MSI GT60 20D-026US Laptop
CPU - i7 4700MQ (No OC)
Video - GTX 780m (No OC)
HDD - Samsung 840 EVO 500gb
Ram - 16GB DDR3
OS - Win 8.1 64bit
Computer 3 -
CPU - i7-4790K (No OC)
Video - Radeon HD7870 (No OC)
Mobo - MSI Z97-GD65
HDD - WD Black 1TB
Ram - Kingston 8GB DDR3
PSU - EVGA 750G2
CPU Cooler - Stock
Case - NZXT H440
OS - Win 7 64bit Pro
Network Equipment -
Connection - Comcast 50/10
Modem - Motorola SB6121
Router - Netgear N750
Troubleshooting : I have already updated all of the drivers for the current hardware. I have already ran ALL windows updates. I have already ran Speccy on the culprit pc (Computer 3). All idle temps are fine, I left it running while running the game and all temps appear to be fine then as well. What I don't understand is the network graph, while in game it shows HUGE spikes and inconsistency. Thinking it could be a network cable, I replaced it with a new one. I just don't understand why this computer would spike and the other two don't. Another possibility is, when building this computer, it was basically a swap from my main computer. I never uninstalled the drivers for my GTX 970, so I guess there is a possibility that that is causing the video issue. All have Killer NIC cards. So stands my question. Is Killer Network, killing my network? Any help would be greatly appreciated. Also, any tips on buffing up my network would be great as well. Thanks in advance!

I am with JLio01 on this. Try the Killer Network driver without the application and see if that fixes the issue.
There is not really any reason that it should lag like that.

Hyper V file transfer kills the network

Dear All,
We have 4 Hyper V VM installations on 2 HP DL 380 G8 servers and have they are connected to HP NSA 2040 SAN Storage through 6 Gbps Fibre channel. The physical machines are clustered.
Out of the 4, 2 are Clustered Hyper V's running Microsoft Dynamics AX 2012 R3 and we have 2 Clustered Hyper V for Database server running MS SQL 2012 R2.
The issue here is that the APP servers are slow in communicating with the DB server. The Hyper V's have a dedicated 4 * 1Gbps interface cards teamed and the packets are getting timed out. But from any other machine in the subnet the communications are proper.
When ever i try to copy a file from the DB server to the APP server using SMB share it kills my network, the copy will happen but after the copy is completed the network comes backup.
Its strange scenario. APP server 2 APP server smb copy is fine, and from DB to DB smb copy is fine but cannot copy between them.
Can anyone please help?
Thanks,
Sriram A Das

Hello,
This forum is for discussions and questions regarding profiles and Microsoft's recognition system on the MSDN and TechNet sites. It is not for products/technologies.
As it's off-topic here, I am moving the question to the
Hyper-V forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Chat SSDP Discovery flooding network killing all networking

I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

IChat SSDP Discovery flooding network killing all networking.

I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
This has only just started in the last week.

Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

Mavericks: Killer of Networked Printing

I'm a veteran user of PC/Windows after 2y owning a MBP I'm still amazed at how much stuff just is bizarre in the OSX world that worked flawlessly in the Windows world, at least since Win 7 especially. Very difficult to do the most common tasks used all of the time for me as a somewhat power Windows user, in the OSX world. For example: no way to role back a driver installation or application if it turns out not to be a good thing without an entire blithering Time Machine restore. That, is just too lame! Next comes the very commonly used column header sort feature in Windows Explorer. Just doesn't work nearly as well in OSX world. When I updated to Mavericks, I discovered the very lovely kind of horizontal hourglass display of Safari Top Sites was removed in the latest version, and there is no way to revert back to the prior version. As well, one could swipe thru history pages in the prior version (at least the one assoc w/ Lion) has now been removed and we have an ugly list now and no way to view these pages unless I missed something. Next comes the very very frequently use Screen Print, Home & End buttons in the default Windows keyboard. These features are used very frequently, and yet they don't exist in OSX, at least on my smaller MBP keyboard. Instead, it's a key combination I have a hard time remembering, and it just doens't work quickly and intutively as it does in Win world. These are real productivity features.
Now comes my HP Photosmart D5400 connected to my MSHome network: worked fine prior to Mavericks, now, despite the fact Software Update installed the alledgedly updated driver for X, not happening, for me and what sounds like everything else.
OSX is not the best productivity OS unless you're really an advanced user it would appear. I really do like many features of this MBP, but so many areas are just plain odd in this day an age in terms of practicality and productivity. And a huge one is: no built-in way to role back to prior states w/o restoring from a former image.
I'm hoping if I post here when the soln to network printing (not some blithering work around!) is posted hopefully I can print wirelessly once again. The problem is posted all over the web so I won't go into detail, and don't want to bother w/ other ways of making the broken thing work as a work around. I tried a few of those last evening, killing a good hour+ to no avail. May end up going back to Lion if I can figure out how to restore just the OSX partition from an external TM back up I did early on, taking care to save all my data prior to that. I do like a feature or two in X, but they're not really all that useful in the end.

This pretty much sums it up:
Reverting a system backwards from Mavericks is no picnic
Summary: After installing OS X Mavericks to their systems, some users want to go back to whatever system version they had before, usually Mountain Lion or Lion. However, a retrograde is not an easy process.
By David Morgenstern for The Apple Core | November 1, 2013 -- 05:42 GMT (22:42 PDT)
Following an installation of OS X Mavericks to their system, a number of readers have contacted me about retrograding, returning to an older version of the OS. They seem to believe that this is a process similar to the upgrade: simply clicking a few buttons in Time Machine and it will be done. Nothing can be further from the truth.
Man oh man, that is so blithering lame--for 2013!

Time machine kills Wifi network!!

I had recently posted a thread on TC forum "Weird shut down of TC" that my TC just shuts down routinely.
I have a 1TB TC that has been working very well. I bought the new unibody MBP and the Time machine has been backing up quite nicely for past one month.
I now have a problem that the TM aborts with a message the the drive could not be accessed due to network problems.
My Wifi would be down, status light amber, after a while the status light would go off completely but the disk in TC would be spinning as can feel the spin vibrations. This would happen about every 45 minutes and only way to go back up was to unplug and plug.
I now find that the culprit is time machine. This is what I tried sequentially:
A. Rolled back to 7.3.1 firmware. Same problem.
B. Switched off the TM from prefrences. It worked well for a day.
C. Switched on the TM. As soon as TM backup started, I had the TC wifi freeze.
D. updated to firmware 7.3.2 with TM turned on. Same problem
E. Turned off the airport card, plugged in ethernet cable so now was not using the wifi but wired connection to the TC. Started the TM and again. SAME PROBLEM.
F. Turned off TM, all was well for the entire day.
G. Turned it back on and on the first back up attempt, the WiFi was killed again.
I think now the problem may be with the size of the back up that TM is attempting. It does the 'prepare for back up' pretty quickly but once the back up starts, it kills the WiFi and aborts with a message that there is no network.
Anyone have any idea if I should troubleshoot differently or diagnose this differently?
Has anyone had a problem with TM with large back ups?

Hi Alexandre,
Thanks for the input. Sorry my profile was not updated. I am using MBPro 10.5.5.
Here is the output from console which I think is the portion till the network went down. Could not find a way to attach the file.
Thanks for any help you can give:
Dec 7 08:50:36 Mehers-MB-Pro-2 kernel[0]: AFPSleepWakeHandler: waking up
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: Computer did wake up from sleep. Reschedule our timers!
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:40 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:26:38 Mehers-MB-Pro-2 ntpd[27]: time reset -0.527369 s
Dec 7 09:34:27 Mehers-MB-Pro-2 SyncServer[3340]: SyncServer: Truth vacuumed. Next vacuum date 2008-12-21 09:34:24 +0500
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup requested by user
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Starting standard backup
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network mountpoint /Volumes/Data-1 not owned by backupd... remounting
Dec 7 09:51:34 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3360
Dec 7 09:51:34 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network volume mounted at: /Volumes/Data
Dec 7 09:51:36 Mehers-MB-Pro-2 hdiejectd[3374]: running
Dec 7 09:51:37 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75690496 to: 75768832 (joffset 0x1d0f000)
Dec 7 09:51:38 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: event logs in /Volumes/Backup of Meher’s MB Pro/.fseventsd out of sync with volume. destroying old logs. (524 2 54320)
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: log dir: /Volumes/Backup of Meher’s MB Pro/.fseventsd getting new uuid: 2EF5457F-ED49-4E27-A818-A80F61BCCB86
Dec 7 09:51:47 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (906 > 0)
Dec 7 09:51:52: --- last message repeated 1 time ---
Dec 7 09:52:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:17: --- last message repeated 1 time ---
Dec 7 09:52:37 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: No beacon for too long time
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:52:51: --- last message repeated 1 time ---
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:2a:6e
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 09:53:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 09:53:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: No Ack
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:17 Mehers-MB-Pro-2 configd[14]: AppleTalk startup
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: MAC AUTH succeeded
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Up on en1
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x7c92a00
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:74:89
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: got dev 0x4dd6604
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: wireless interface detected.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: up
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: attached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is coming UP
Dec 7 09:53:23 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 diskimages-helper[3365]: terminating disk1 - image is no longer available
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: rder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: ] [IOType Read] [PBlkNum 722696] [LBlkNum 29801] [FSLogMsgID 1403590549] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write error (6)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: HFS resolvelink: can't find iNode463676
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write failed - expected:12017024, actual: 1048576
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: 741] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in recoverIndex:recover canceled (live.0.)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexCI in ContentIndexUpdateContent:Caught mach exception. Fun Fun Fun.
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in bool siwriteBackAndIndex(_SI*, __ContentIndex*, const __CFDictionary*, const __CFDictionary*, db_obj**, const __CFString*, int, bool, bool, bool, __SIUserCtx*, const __CFString*, int32_t, bool):ContentIndexUpdateContent failed
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in void setAttributes(siset_attrctx*, Boolean, long unsigned int):Couldn't update index.
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:29: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup failed with error: 26
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: close: journal 0x4e8ae08, is invalid. aborting outstanding transactions
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:34 Mehers-MB-Pro-2 com.apple.launchd[1] (com.apple.netauth.sysagent[3360]): Stray process with PGID equal to this dead job: PID 3363 PPID 1 check_afp
Dec 7 09:53:40 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 3414
Dec 7 09:54:36 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:54:55: --- last message repeated 7 times ---
Dec 7 09:55:08: --- last message repeated 8 times ---
Dec 7 09:55:12 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:55:17: --- last message repeated 7 times ---
Dec 7 09:59:07 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2c00 Autoneg capable 1
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x4fd2300.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e1:0f:ab
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x4fd2300.
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backup requested by user
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Starting standard backup
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 10:01:00 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: posting to KEA EINPROGRESS for /Volumes/Data-1
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 found 1 filesystem(s) with problem(s)
Dec 7 10:01:00 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 10:01:05 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3441
Dec 7 10:01:05 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:05 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:05 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Network volume mounted at: /Volumes/Data
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:20 Mehers-MB-Pro-2 hdiejectd[3459]: running
Dec 7 10:01:21 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75768832 to: 76011520 (joffset 0x1d0f000)
Dec 7 10:01:22 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 10:01:22 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:22 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (906 > 0)
Dec 7 10:01:35: --- last message repeated 1 time ---
Dec 7 10:01:38 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 unmounting 1 filesystems
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data-1, flags 524288, pid 40
Dec 7 10:01:39 Mehers-MB-Pro-2 loginwindow[39]: No servers unresponsive
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:00: --- last message repeated 1 time ---
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: Link Down
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: interface en is going DOWN
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: filter detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: down
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f4:e9:4f
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:02:20 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2cff Autoneg capable 1
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x62aeb00.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f5:10:a0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x62aeb00.
Dec 7 10:02:48 Mehers-MB-Pro-2 mDNSResponder[16]: Note: Frequent transitions for interface en0 (192.168.1.130); network traffic reduction measures in effect
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <1d89> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <token> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).

Killer Network Manager literally 'killing' my network

I've recently bought the Z97M Gaming motherboard and installed the network driver that came with it.
Unfortunately the Killer Network Manager's "Bandwidth Control" setting seems to 'kill' my whole network. With that feature enabled you are unable to access the internet via ethernet or wireless regardless of device. It seemingly also stops access to the router via the default gateway IP however I haven't tried that from a device that isn't this computer. The only way to regain access is to reboot the router.
After spending several hours trying to diagnose the issue I finally discovered that it was the "Bandwidth Control" setting that I mentioned above so I naturally just disabled that. Unfortunately I've now found out that, despite the fact I've applied the changes with the "Bandwidth Control" setting turned off, it seems to re-enable itself when I put my computer to sleep and then power it up again.
I can't really go forward with continually rebooting the router in order to resolve the issue, I need a fix that I can perform locally. Ideally I'd like to be able to just install the network driver without installing the Killer Network Manager but it doesn't seem like MSI offer that option. The only other option that I can think of is to change something on my computer or on the router. The router is the Super Hub 2 / 2ac from Virgin Media.
Thanks in advance and please let me know if you require any further information.

Quote from: Svet on 14-January-15, 11:59:51
do you use latest killer suite drivers 1.1.49.1068 ?
Sorry probably should've included that in my original post.
Yes I'm on 1.1.49.1068 on Windows 7 64bit.
Quote from: TZBC on 14-January-15, 13:19:38
MSI website provide the Killer Network Driver without KNM
check this out
removed because I can't post links...
I did look on MSI's site and, for some reason, that driver isn't listed on the UK site (can't post links but just append uk. before msi.com).
I assume there's not going to be any locality issues with installing that driver and it's just an oversight that it isn't on the UK site?

MacBook killing wireless network

I have the MacBook 1.1 . Router is Linksys WRT54G. Up until approximately 2 weeks ago the network has worked without issue. For some reason the MacBook is killing the wireless network. I thought it was my ISP at first but then narrowed it down to the issue only happening when the MacBook is on the wireless network and then in the past couple of days noticed the network gets killed as soon as the Macbook connects. Im not referring to the just the MacBook loosing connection.... the entire wireless goes down and no wireless devices have access. It eventually comes back up but as long as the MacBook remains in the wireless network it will go back down again.
Snow Leopard... Latest driver... latest firmware. It seems that this started right after a recent update downloaded on the MacBook but I cannot recall what was updated. I need this fixed since my Macbook is my main computer. The others are for family members and Im forced to stay off so they dont get booted.

I have a similar problem with the Linksys WRT54G2 router. The problem seems to come and go but like you rz22g the only time the network is affected is when my MacBook is connected. All other devices on my network work fine PS3, MacMini etc.
Just a speculation but the frequency of this problem started when I upgraded the firmware of the router. I don't know why this would have such a negative reaction. I have also checked that all the router settings are identical to the way they were before the router firmware update.
Oddly enough while I type this my network has been the most stable I've seen it in a while.

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.

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

Killer's network drivers only [without software suite]

>>Killer_E220x_Wireless-N_INF_Win7_Win8_Win8.1.zip<<

Okay. I see the confusion. He is using the drivers that Svet recommended. Which are slightly newer than your own, but are also without the Killer Network Manager and must be installed manually. (10.0.1.263 for the Wireless and 8.0.2.42 for the e2200)
My issues with the wireless seemed to go away with Svet's drivers - which was essentially a newer download pinned to the forums of what Warner gave to you. He could give Warner's a try but they basically are the same. I assumed my issue didn't go away as I was having another BSOD issue that didn't exactly specify which device was causing the BSOD.
As for my issue - I have uninstalled the Logitech software and haven't had a crash within the past day and a half. I noticed the longer I have the laptop on, the more likely the BSOD. So, I am leaving it on all day playing games off and on.
I did notice that SetPoint does install software that is meant for keyboards. Simply because Logitech has a unified driver suite between their mice and keyboards able to use a single wireless dongle, eliminating the need to use one for each device. This could, in theory, be causing an issue with the MSI SCM. Most people think of the SCM as a control app, but it also installs a service (called Micro Star SCM) which handles event communication between several different driver packages/software. This is why when the SCM is uninstalled, the keyboard light manager fails to start up as well as Hybrid Power and a few other MSI apps. If uninstalling the Logitech software does work, then it could be that the keyboard manager in SetPoint is intercepting events that should be going to the SCM service.
If it crashes again, I will swap out the mouse itself. I'll update my thread on this issue on the next crash or in a few days if I have no further issues. I'm crossing my fingers and thanks for the tips.

10.4.8 Killed my network stuff'ns

Similar Messages

Maybe you are looking for