Have I mentioned how much I don’t like working with Macs?
I have some friends who like them, so I won’t go as far as some Mac fanboys to claim that Macs suck and everyone is better off with an XP computer (but that is pretty much how I feel).
I bought a Mac for my wife a year ago, because at school there are still people emailing around clarisworks files, and from time to time we want to do something that would require accessing a shared folder on the network.
Problem is: it never works.
“The alias ServerName could not be opened because the original item cannot be found”
Searching google turned up 101 different ways to connect to a network share, and they all failed in different ways.
Last nigiht I found myself trying to get it to work once again, but this time I happened across a solution.
After hours of wasting my time, I finally found the solution here.
Windows 2003 Servers encrypt their communications, Macs can’t deal with this. Problem solved.
Chris May 
I hate to be a downer, but I recently made the switch from a badass gaming computer running XP/Ubuntu in a dual boot environment, to a MacBook. I must say that, yes, the issue with the cut/paste operation is a pain in the ass, though it can however, be overcome by opening a new window with the destination folder and simply dragging it over, no not the best solution, as that would be for Apple to simply add the cut/paste operation, but it does prove useful.
With regards to this post, I must say, that issues with Mac OS and Windows interoperability is generally the fault of Microsoft, when you consider that since the inception of IE, it has not been a web standards compliant browser until IE8, which still has a compatibility mode. For example, if you take and put any Linux based operating systems, OS X, and Windows in a network, guess which OS is going to have the most problems with networking, not to mention the lockdown of the NTFS file system, and how everything Microsoft has to be proprietary, whereas I can take the hard disk out of a Linux based machine, throw it in an OS X based machine, and it works, and vice versa, try that with windows…
All things aside, I think your site here is very well written and with good reading content… Thanks!
~Jacob
Jacob,
I know what you are getting at. With OSX, Macs are running on a *nix OS, so I’d expect them to work better with other *nixs. But in my world, at home, at my clients, in the office, at friends, at family members etc. 99% of the computers are windows. I can understand if MS doesn’t build in compatability for a MS machine to work well with Macs or linux, until recently there were almost none of them around, and even now PCs are probably 10 to 1 over Macs and Linux (maybe just 5 to 1 I’m just pulling numbers out of thin air). On the other hand, I think the onus is on Apple to make their stuff work with Windows machines where possible becuase chances are a lot of macs are going to run in a (majority) windows network.
This post really wasn’t me blaming Apple, it’s more to do with W2k3 locking things down and making the user explicitly open them up, but the fact that it was this hard to do something this simple is horrible.
I love my iphone though 🙂
Thanks for the comments. Chris.