-
All replies
-
Helpful answers
-
Jul 21, 2014 6:09 PM in response to raconteur10by Carolyn Samit,Might be Finder preferences are corrupted ...
Open the Finder. From the Finder menu bar click Go > Go to Folder
Type or copy paste the following:
~/Library/Preferences/com.apple.finder.plist
Click Go then move the com.apple.finder.plist file to the Trash.
Restart your Mac.
If that didn't help, apps such as CCleaner do far more harm to your Mac than good. Your Mac runs maintenance in the background for you Mac OS X: About background maintenance tasks
Check for CCleaner uninstall instructions here > https://www.piriform.com/mac/ccleaner
After you uninstall CCleaner, try connecting to the server.
-
-
Jul 21, 2014 6:41 PM in response to Carolyn Samitby raconteur10,Thanks for the response Carolyn but unfortunately it didn't fix the problem. I have also removed CCleaner.
-
Jul 21, 2014 6:41 PM in response to Linc Davisby raconteur10,The server is another Mac Mini. We have another six or so Macs connected to the server. Some running Mavericks.
-
Jul 21, 2014 6:48 PM in response to raconteur10by Linc Davis,Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES â–¹ All Messages
from the log list on the left. If you don't see that list, select
View â–¹ Show Log List
from the menu bar at the top of the screen.Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.
-
Jul 21, 2014 8:20 PM in response to Linc Davisby raconteur10,22/07/2014 1:13:46.270 pm mds[39]: (Error) Server: Failed to register path "/Volumes/HD 2" to store <MDSStoreToken: 0x7fbae348fbe0>{storeID:0x6b000040 registered:YES private:NO age:28.414s uuid:1913115F-22F8-4A63-A6EE-37321A4643E5}
22/07/2014 1:15:42.062 pm sharingd[193]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7f913b513de0 FFFFFFFF DDDDDDDD
22/07/2014 1:17:24.769 pm com.apple.IconServicesAgent[227]: main Failed to composit image for binding VariantBinding [0x4e3] flags: 0x8 binding: FileInfoBinding [0x371] - extension: ai, UTI: com.adobe.illustrator.ai-image, fileType: PDF .
22/07/2014 1:18:06.000 pm kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xffffff801a5bc8e8
22/07/2014 1:18:06.000 pm kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/HD 2
22/07/2014 1:18:06.000 pm kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/HD 2
22/07/2014 1:18:06.000 pm kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/HD 2
Just took out a couple of random parts. Let me know if you need more. Thanks
-
Jul 21, 2014 8:36 PM in response to raconteur10by Linc Davis,Launch the Network Utility application. Select the Netstat tab and then the button marked
Display comprehensive network statistics for each protocol
Click the Netstat button, or press the return key. Text will appear in the window. Copy it into a reply to this message. Please post the text, not a screenshot.
-
-
Jul 21, 2014 8:55 PM in response to raconteur10by Linc Davis,That's the routing table. Please review the instructions and try again.
-
Jul 21, 2014 9:01 PM in response to Linc Davisby raconteur10,Sorry...
tcp:
61269 packets sent
14501 data packets (5423429 bytes)
457 data packets (298568 bytes) retransmitted
0 resends initiated by MTU discovery
34229 ack-only packets (284 delayed)
0 URG only packets
0 window probe packets
8915 window update packets
3181 control packets
0 data packets sent after flow control
0 checksummed in software
0 segments (0 bytes) over IPv4
0 segments (0 bytes) over IPv6
66665 packets received
15538 acks (for 5408457 bytes)
1286 duplicate acks
0 acks for unsent data
46049 packets (49418889 bytes) received in-sequence
233 completely duplicate packets (175429 bytes)
0 old duplicate packets
1 packet with some dup. data (996 bytes duped)
6329 out-of-order packets (8815198 bytes)
0 packets (0 bytes) of data after window
0 window probes
70 window update packets
166 packets received after close
0 bad resets
0 discarded for bad checksums
0 checksummed in software
0 segments (0 bytes) over IPv4
0 segments (0 bytes) over IPv6
0 discarded for bad header offset fields
0 discarded because packet too short
1604 connection requests
50 connection accepts
0 bad connection attempts
0 listen queue overflows
1622 connections established (including accepts)
1613 connections closed (including 48 drops)
37 connections updated cached RTT on close
37 connections updated cached RTT variance on close
15 connections updated cached ssthresh on close
0 embryonic connections dropped
15554 segments updated rtt (of 13699 attempts)
544 retransmit timeouts
20 connections dropped by rexmit timeout
0 connections dropped after retransmitting FIN
2 persist timeouts
0 connections dropped by persist timeout
0 keepalive timeouts
0 keepalive probes sent
0 connections dropped by keepalive
2887 correct ACK header predictions
40214 correct data packet header predictions
79 SACK recovery episodes
43 segment rexmits in SACK recovery episodes
39243 byte rexmits in SACK recovery episodes
256 SACK options (SACK blocks) received
6226 SACK options (SACK blocks) sent
0 SACK scoreboard overflow
0 LRO coalesced packets
0 times LRO flow table was full
0 collisions in LRO flow table
0 times LRO coalesced 2 packets
0 times LRO coalesced 3 or 4 packets
0 times LRO coalesced 5 or more packets
3 limited transmits done
106 early retransmits done
20 times cumulative ack advanced along with SACK
udp:
6116 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
0 with no checksum
0 checksummed in software
0 datagrams (0 bytes) over IPv4
0 datagrams (0 bytes) over IPv6
41 dropped due to no socket
2230 broadcast/multicast datagrams undelivered
0 times multicast source filter matched
0 dropped due to full socket buffers
0 not for hashed pcb
3845 delivered
994 datagrams output
69 checksummed in software
0 datagrams (0 bytes) over IPv4
69 datagrams (11318 bytes) over IPv6
ip:
72011 total packets received
0 bad header checksums
0 headers (0 bytes) checksummed in software
0 with size smaller than minimum
0 with data size < data length
3522 with data size > data length
0 packets forced to software checksum
0 with ip length > max ip packet size
0 with header length < data size
0 with data length < header length
0 with bad options
0 with incorrect version number
0 fragments received
0 dropped (dup or out of space)
0 dropped after timeout
0 reassembled ok
71997 packets for this host
14 packets for unknown/unsupported protocol
0 packets forwarded (0 packets fast forwarded)
0 packets not forwardable
0 packets received for unknown multicast group
0 redirects sent
62678 packets sent from this host
0 packets sent with fabricated ip header
0 output packets dropped due to no bufs, etc.
0 output packets discarded due to no route
0 output datagrams fragmented
0 fragments created
0 datagrams that can't be fragmented
0 tunneling packets that can't find gif
0 datagrams with bad address in header
0 packets dropped due to no bufs for control data
71 headers (1428 bytes) checksummed in software
icmp:
41 calls to icmp_error
0 errors not generated 'cuz old message was icmp
Output histogram:
destination unreachable: 41
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
0 multicast echo requests ignored
0 multicast timestamp requests ignored
Input histogram:
destination unreachable: 14
0 message responses generated
ICMP address mask responses are disabled
igmp:
0 messages received
0 messages received with too few bytes
0 messages received with wrong TTL
0 messages received with bad checksum
0 V1/V2 membership queries received
0 V3 membership queries received
0 membership queries received with invalid field(s)
0 general queries received
0 group queries received
0 group-source queries received
0 group-source queries dropped
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 V3 reports received without Router Alert
2 membership reports sent
ipsec:
0 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound packets considered authentic
0 inbound packets failed on authentication
0 outbound packets processed successfully
0 outbound packets violated process security policy
0 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
arp:
5 ARP requests sent
9 ARP replies sent
0 ARP announcements sent
98 ARP requests received
6 ARP replies received
104 total ARP packets received
0 ARP conflict probes sent
0 invalid ARP resolve requests
0 total packets dropped due to lack of memory
3 total packets dropped due to no ARP entry
0 total packets dropped during ARP entry removal
12 ARP entries timed out
0 Duplicate IPs seen
ip6:
793 total packets received
0 with size smaller than minimum
0 with data size < data length
0 with data size > data length
0 packets forced to software checksum
0 with bad options
0 with incorrect version number
0 fragments received
0 dropped (dup or out of space)
0 dropped after timeout
0 exceeded limit
0 reassembled ok
784 packets for this host
0 packets forwarded
0 packets not forwardable
0 redirects sent
0 multicast packets which we don't join
0 packets whose headers are not continuous
0 tunneling packets that can't find gif
0 packets discarded due to too may headers
0 forward cache hit
0 forward cache miss
0 packets dropped due to no bufs for control data
126 packets sent from this host
0 packets sent with fabricated ip header
0 output packets dropped due to no bufs, etc.
4145 output packets discarded due to no route
0 output datagrams fragmented
0 fragments created
0 datagrams that can't be fragmented
0 packets that violated scope rules
Input histogram:
TCP: 22
UDP: 762
ICMP6: 9
Mbuf statistics:
507 one mbuf
two or more mbuf:
lo0= 69
217 one ext mbuf
0 two or more ext mbuf
0 failures of source address selection
icmp6:
0 calls to icmp_error
0 errors not generated because old message was icmp error or so
0 errors not generated because rate limitation
Output histogram:
router solicitation: 4
neighbor solicitation: 4
neighbor advertisement: 4
MLDv2 listener report: 7
0 messages with bad code fields
0 messages < minimum length
0 bad checksums
0 messages with bad length
Input histogram:
neighbor solicitation: 3
neighbor advertisement: 6
Histogram of error messages to be generated:
0 no route
0 administratively prohibited
0 beyond scope
0 address unreachable
0 port unreachable
0 packet too big
0 time exceed transit
0 time exceed reassembly
0 erroneous header field
0 unrecognized next header
0 unrecognized option
0 redirect
0 unknown
0 message responses generated
0 messages with too many ND options
0 messages with bad ND options
0 bad neighbor solicitation messages
3 bad neighbor advertisement messages
0 bad router solicitation messages
0 bad router advertisement messages
0 bad redirect messages
0 path MTU changes
ipsec6:
0 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound packets considered authentic
0 inbound packets failed on authentication
0 outbound packets processed successfully
0 outbound packets violated process security policy
0 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
rip6:
0 messages received
0 checksum calcurations on inbound
0 messages with bad checksum
0 messages dropped due to no socket
0 multicast messages dropped due to no socket
0 messages dropped due to full socket buffers
0 delivered
0 datagrams output
pfkey:
0 requests sent to userland
0 bytes sent to userland
0 messages with invalid length field
0 messages with invalid version field
0 messages with invalid message type field
0 messages too short
0 messages with memory allocation failure
0 messages with duplicate extension
0 messages with invalid extension type
0 messages with invalid sa type
0 messages with invalid address extension
0 requests sent from userland
0 bytes sent from userland
0 messages toward single socket
0 messages toward all sockets
0 messages toward registered sockets
0 messages with memory allocation failure
-
Jul 21, 2014 10:10 PM in response to raconteur10by Linc Davis,A lot of packets are being lost. If the client connects to the network via Ethernet, try a different cable, different switch port, etc.
-
Jul 22, 2014 12:43 AM in response to Linc Davisby raconteur10,Thanks for the reply but I tried another port in the office and I'm still getting the same error...
-
Jul 22, 2014 7:02 AM in response to raconteur10by Linc Davis,And another cable? Is this the only client with the problem?
-
Jul 22, 2014 5:25 PM in response to Linc Davisby raconteur10,Yes same issue with another cable.
I was the only user experiencing this issue but another user's computer has begun to show similar symptoms. Her finder is freezing when she tries to access the server.