NASLite Network Attached Storage

Hi,

I have been happily using Apple 10.3.8-9 and an old PII box running NASlite-SMB for many months without a problem. I just updated to Tiger (10.4) I am getting a host of connection problems. (I am posting at Apple to but I wonder if someone might have a a suggestion)
I am getting the following messages after using trying to connect and submitting the Workgroup, Name and a (blank) password.
"The finder cannot complete the operation because some data in "smb://10.0.1.100/" could not read or written. (Error code -36)."

Error code -36 is a I/O error.

in my logs I'm getting these messages:
mount_smbfs: session setup phase failed: syserr = Socket is not connected
mount_smbfs: could not login to server SERVER: syserr = Socket is not connected

If there is a way I can correct this it would be great. I understand I just may have to wait for Apple to fix whatever the problem is but I hope not!

Any suggestions would be great - thanks for taking the time to read this!

matt

Since it's not officially available until this evening at 6pm I can't comment.

My copy of Tiger 10.4 will arrive this afternoon and I will check for compatibility.

Hi, I'm having similar problems.

I'm relatively new to the Mac OS (my mini is my first) but I had my NAS server working in perfect harmony with my 10.3 installation until I upgraded to Tiger.

Over the course of trying to rectify this I have had an assortment of errors including "name or password is not correct", -36 and "the original item could not be found".

I can, however, connect and log in to the server using the terminal window and telnet.

Please help my Mac and Nas box get along again.

PS Can I ask where you posted your error to Apple support? Is it a discussion others can view?

Found mgantner's Apple Support submission

http://discussions.info.apple.com/webx? ... @.68ad8218

FYI update:

I've installed Tiger 10.4 and am having the same issue, SMB and NFS will not mount, ftp will however.

I'll investigate this and post/fix when I resolve this.

just as an update to Ralph and others: I have been doing some reading and discovered that networking in Jaguar did not like dashes in the shared volume name. Of course that was jaguar - but Apple may have changed thier smb protocol in a way that has a similar problem now. all the shares names from NASlite SMB have dashes in them: DISK-1, DISK-2, etc.

I tried to escape the dash with a '\' backslash and a '/' forward slash but it didn't change anything.

Might be something - might be nothing but I thought I would throw that out there.

matt

The folllowing thread is a discussion on Apple concerning connecting to SMB shares on a variety of linux platforms.

http://discussions.info.apple.com/webx? ... @.68adbf17

At the very bottom of the thread (last post) there is a workaround for this problem but I think it requires root access to the Samba server which of course NASlite does not provide...though I may be wrong.

Temporary solution from Apple Discussions



I'm now connecting to my NASLite box no probs

Hi
Please note Apple has an article concerning this issue. Read it under http://docs.info.apple.com/article.html?artnum=301580 - it's slightly modifying badbugs instructions, using pico and adapting permissions:

HTH
stoe

I have the Mac 10.4.4 problem - cannot mount the NASLite Server. Digging into the Mac documentation says "one cannot connect to a share with a name that contains a hyphen. Resolve the issue by giving the share a name that does not contain a hyphen."

NASLite-SMB Server documentation says "...will name all configured fixed disk drives available on the server computer as Disk-1 through Disk-4 respectively. These names are fixed and cannot be changed"

I am not sure this hyphen information is solved with the work around published by Apple. Is it related or is this a different problem?

I've never had a problem mounting any of my naslite boxes under OSX until 10.3, then the [default] minauth=none fix, solved that.

OSX doesn't have any issues with hyphen'd volume names, this is the first I've heard of it.

The minauth=none fix works just fine. How do I mount them automatically at boot, for all users, as Windows does? I am somewhat familiar with **nx, so a pointer to the right commands would be helpful.

Thanks