I'm having a strange problem with a fresh install of Vista Ultimate and Parallels v3. All I have installed on the Windows side is Vista Ultimate with all available updates. Parallels is V3.0 build 5160. I am running it on a MacBook 2.16 GHz Intel Core 2 Duo with 2GB RAM. I have tested this problem with 512MB and 1GB allocated to the Vista VM. I have also tried Shared and Bridged networking. The problem is when I connect to an OS X server smb share. Windows Explorer will stop responding when navigating through folders. Sometimes it takes a couple minutes, sometimes a few seconds. Windows Explorer will either not respond or will crash asking me to submit a report to Microsoft. This does not happen when connected to a Windows client or server. Anyone have any ideas? Thanks in advance- Jason
hi, it seems to be well known issue. google gave follow links: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=660925&SiteID=1 http://www.builderau.com.au/blogs/codemonkeybusiness/viewblogpost.htm?p=339270746
I've already tried the quick fixes mentioned in those links. It is not an authentication problem, I can authenticate with the server fine. I can also connect to the same server with a desktop machine running Vista Ultimate and don't get the same problems with Explorer that I get from within Parallels. I've tried two different servers on two different networks and get the same result.
My first question for you is the generic one... What do the logs say? Is it getting hung up on authentication? Is it getting hung on a read? Do the logs tell you the ANSWER? Tell us what the logs say if you want help with networking, the alert box rarely tells you what you need to know to fix a problem.
Eru, What logs do you want me to post? I assume it is a log from Event Viewer? I can copy and paste the error message that I get when Explorer quits also.
Well, I don't do enough with Vista to have them all memorized, so perhaps you can do your homework and figure out the network related ones, I could find it if I needed, but I would just use Google. As to the OS X Server, grab the AppleFileServerAccess.log and AppleFileServerError.log Yes, giving us the error will help.
