A word of warning... I've tried to use MC to sync to a "generic handheld" that was a UNC path to a windows share on my LAPTOP via 802.11n, and eventually had to abandon it because I had nothing but problems. The sync would work some days without issue (except for being quite slow), but then other days would completely fail, requiring a restart of BOTH the laptop and the machine doing the syncing in order to get Windows Explorer to respond again.
I suspect that this unreliability is why no major handset manufacturer has officially supported full WiFi sync so far. I think the problem really has nothing to do with MC per-say, and has much more to do with the Windows network file copy behavior being flaky and unreliable (particularly in Vista and Windows 7). It doesn't handle minor transmission errors well, and just assumes that network storage will perform just like local storage only slower.
What I've taken to doing now is to sync MC to a folder on my local drive, and then I use SyncBack SE on my laptop to sync this folder to my laptop. This process is dramatically faster (despite being a two-step process) and is much more reliable, because SyncBack is designed to handle network paths much better than the built-in Windows file copy processes.