Friday, November 14, 2008

Pokemon Goldene Edition Rom Deutsch

length: 10.5 Leopard, but ...

Just before preparing for the next version of Mac OS Leopard seen the light of the world I have my MacBook Pro finally lifted from 10.4 to 10.5.

But what a shock: "Connect to Server ..." is an error -6602 and sometimes comes a kernel panic !

Apparently Leopard no longer connects properly with the Windws servers, here is the statement from Microsoft:
Cause: Windows Server 2008 implements FileShare scoping. In previous versions, if you browsed a Virtual Cluster Network name or the node name, you were presented with all the file shares being hosted on the node (local and clustered). Scoping uses the network name to identify if the browse request if for a cluster file share or local. If it's a cluster network name, it only returns the file shares in the group that is associated with the network name. If it's the local name, it only returns the local shares. The same is true when connecting to a file share, the correct network name must be used. When connecting or browsing with an IP address, it will only access to the nodes local non-clustered shares.
- Leopard 10.4 works, because we can see in the network traces that it provides the network name.
- Leopard 10.5 does not provide the network name, only connects via IP address, Which causes this issue.
Well, what can you do? User Windows Admin who set up a special access to the Shares (Merci!), so you can connect again.

I also have reported the problem via the Apple feedback page . The issue is certainly known, but "constant dripping wears away the stone" ...

As for the kernel panics: they are gone. Maybe the Re-Install VMware has solved the problem.

0 comments:

Post a Comment