![]() Why, at first impression did Windows 7 mapping to Mavericks shared drive and the network seem to function via SMB and work fine only to fail after a few days? I think the failure began when I made an attempt to copy a backup drive of about 70 gig including a large image file to the Pegasus on the Mac Mini which then set off a chain of slowness events that became worse over time and finally got so bad as to be intolerable. What is causing the network slowdown? I miss 10.6.8 which was heaven compared to this debacle. ![]() I am testing the CIFS fix this weekend to see if my network functions as intended after mapping from Window 7 machine to Mini's Pegasus. Today, I could not even upload a small PDF to google. After a time I cannot make use of Logmein as it became impossible and also Citrix failed. Network slows down making it unusable after the workstation mapping begins to fail. Why does mapping on network v mapping to host differ? Worse, I've had added network problems not mentioned here killing further testing whenever I map to Pegasus from a Windows 7 Machine or map to Pegasus from XP machine after a time, maybe 4- 5 days. How is this possible? This is Windows to Mavericks and no SMB issue. I have Windows 2008 Server VM using Fusion working well that will map to host Mini shared drive and also map to the Mini's Pegasus with no issue. I have newer Mac Mini, 16 Ram, SSDs, with 10.9.4.
0 Comments
Leave a Reply. |