Leopard Upgrade and Loss of File Transfer to Windows PC
Loss of File Transfer to Windows PC - I successfully upgraded my MacBook to Leopard with the following exception where I was previously able to transfer files to a Windows PC. I can still connect to the PC but unable to see the folders in "finder" or move files over to it. I can still do this however from my other Mac (iMac) which is still on Tiger. What would the upgrade have done to prevent file transfer being done?
Thanks Neil
iMAC,
Mac OS X (10.4.9),
Loss of file transfer to Windows
Please - when you get the answer to this let me know - I have exactly the wsame situation. My iMac is on Tiger and sees Vista and XP PC's fine. This MacBook Pro sees the iMac and that it is after installing Leopard. Ugh
I had similar problems with browsing Windows shares... Initially I performed an Upgrade installation of Leopard. A temporary work-around was to use the IP address of the Windows computer.
For example (in the Connect To Server dialog) use:
smb://<IP address>/sharename
Obviously, you'll have to determine the local network IP for your Windows computer and know the name of the share. You can do this by opening up a CMD window and issuing the following command at the prompt:
ipconfig/all
Hope that wasn't too "technical".
Note: What fixed the whole problem for me was to perform a clean installation of Leopard... Now all the Windows computers on the network appear under Shared in the Finder sidebar.
Thanks for the input, though I can see the PC in my shared finder window, but unable to transfer files onto the PC, whereas I was able to do so under Tiger - any further thoughts on this?
If you can read but not write to the drive, then it would point to a permissions issue.
What account are you logging into Windows under? The first time you connected, you should have been prompted to authenticate. At that time, you would have had to enter an account with Full Access under Windows...
Have you applied the Keychain update? I had problems immediately after an Upgrade installation with logging on using previously saved authentications...