I have an SMB NAS drive that connected fine in 10.4. However, with 10.5, on my MacBook Pro I can connect to it and can see the 2 volumes on it but can't do anything with them, and can't disconnect from it once connected. On an iMac G5 also upgraded to 10.5, it starts to connect and then locks up. I can connect to the NAS with FTP with no problem but not through sharing.
I bought a Freecom Network drive a few weeks ago and whilst I can (eventually) see the drive and its contents on my mac I can't write reliably to the drive. Normally i get error -1407 or various permissions messages popping up.
I contacted Freecom who sent me a driver for the 500Gb drive and this made it better, but still i can't use the drive reliably. It looks nice and that's about it!
Has anybody found a way to get the 500Gb Freecom drive working with a MAC (I tried connecting it to AEBS and a wired router and found the same thing!)
I have the Freecom 500GB NAS drive connected to my Linksys WRT54GS wireless router. Using the method described earlier in the thread, I can connect to the drive via SMB, and read/ write files without a problem. The only issue I haves using Time Machine, my wireless network is too slow for the amount of data being copied, so Time Machine times out with a failure.
It´s weird. Thinking about downgrading to Tiger. Reminds me to the Apple commercial. Do you remember? Windows users downgrading to XP? Never heard of that. But i do have lots of comments of user downgrading to Tiger. So, how about the commercial? Sorry to say that - Windows Vista seems to be far ahead in comparision to Leopard...
Hi, we have the same problem with Samba. We have 4 Mac Minis and 2 Macbook Pros running 10.5.1, as well as 4 Mac Minis running 10. 4.x and one Vista PC. They are connected to our central file Server, a Windows 2003 Standard edition. On the Macs we upgraded to 10.5 we see the following problems connecting with Samba:
- connection with the shares works
- authentification works
- copying files in each direction generates error messages that indicate permission problems. However the shares on the server are shared to "everyone" with "full access".
- copying files randomly from the Mac to the server randomly shows them in the target folder, but within seconds they disappear again
- same thing happens when files on the server are opened in an application and then saved again. They disappear and are completely lost - can only be restored from tape backup.
- copying folders containing files and folders is not reliable. Some files are copied, others get lost on their way to the server.
However all Macs running 10.4 don't have that problem. -it definitely seems to be a serious bug in 10.5 (data loss!!!)
In Apple's support forums I found nothing about that problem. Does anyone know a fix?
I have had this problem with 2 of the 3 Macs I am working with...2 have Leopard and one has Tiger. The Tiger Mac can see everything with no problems. The Leopard Macs seem to have trouble connecting only to certain drives. We called a mac tech and no luck. Finally, I was online and downloaded an smb client called smbMount and I can connect to the smb drives now using Firefox instead of the Go To Server through the finder. When you download the app, open the text file and read the instructions, there are a few configurations that need to be made in Firefox in order to make it accept the smb:// address. This worked immediately. The smbMount is available at
http://www.macupdate.com/info.php/id/25262/smbmount
Not mine -- I still get permissions errors trying to write to SMB NTFS shares with 10.5.2. Also WHY can OS X not write to directly connected NTFS disks? I believe there are third-party solutions to this, so why are we still waitiing?
I'm having the same problems too. I have 3 macs running 10.5.2 (the rest are running 10.4.11) and all of them are exhibiting this same problem. They can connect to the server (Windows Server 2003) using smb, but some of the folders appear empty. Sometimes the folders in question change to document icons but when you click on the icon the file disappears. Plus the connection to the network shares intermittently drops.
These are new macbooks that came with 10.5 so I can't downgrade them to 10.4
I just gotta say brilliant, Apple! You give us a translucent menu and reflective dock, but completely hose the ability to connect to Windows servers. Just
what smb problems did you fix in the updates, because it hasn't made a darned difference.
Unfortunately, the work-arounds posted here are not acceptable due to "end user issues."
I need a real fix. Otherwise, these macbooks are basically useless.
I have an update on the "empty" folders on the Windows 2003 server. It turns out there was a space at the end of the folder name. I was poking around the network share in Terminal and noticed that it listed the problematic folders as
"foldername\ /" (without the quotation marks)
I was unable to rename the folders in XP Pro, Windows 2003 server [both gave errors that it couldn't find the source disk or file to rename] or Mac OS 10.5 [The operation could not be completed. An unexpected error occurred (error code -43)]. The only way I was able to rename the folders was by using a Mac that was running 10.4 After deleting the space at the end of the folder name the 10.5 Macs could access the contents of the folders.
This still doesn't explain the network share spontaneously disconnecting.
