Mac OS 10.4 (Tiger)/Linux compatibiltiy
 

I have several drives mapped in my Apple machines to various servers. After upgrading to tiger, I can no longer hit my linux server. I have 800 GB of storage for my Mac users, who can no longer hit this server. I was using smb://10.2.0.16/macfiles. Now when I do, it tells me that the server doesn't exist. I can ping it, traceroute to it, view open ports, but cannot map to it. Any ideas. I called Apple support and they didn't know what to do. I need to upgrage 30 macs, but cannot if they cannot see the fileserver.
I have posted on several mac forums sites to no avail and even called Apple support. They told me it was my linux box, even though 300 PCs and all of the other macs can hit it. the only one that cannot is the new 10.4 (tiger). Is there an update that I need to do?

Have you tried using smbclient on the command line to connect to it to see if any specific error messages come up? Are there any messages in the samba logs on the linux machine? I just tried on my home network and my Powerbook with Tiger has no trouble connecting to my Gentoo or Slackware boxes over samba.

Another suggestion.... if you can't get samba to work from the Apple do you run NFS on your Linux server? NFS is probably a better method of connecting to your file server anyway.

I am new to both mac and linux. I am a windows guy, but have been thrust into this as everybody else either quit or got fired who knew about this. Oh, by the way, we lost the AS/400 guy too. (I wonder if that should tell me something). Anyway, I am not sure how to use the smbclient from command line. I did try setting up nfs, but when i try to hit it from the mac, I get "Could not connect to the server because the name or password is not correct". It didn't ask for any authentication like the smb did. One very important thing I probably should have mentioned is that this is a cluster environment. The 10.2.0.16 is a virtual IP. As I stated before, we haven't had any problems at all (except OS 9, which couldn't hit the cluster). Thanks for the help

Well, from a console you can do "smbclient -U <username> \\server\share" to connect to a share....

As far as the clustering goes, that is an area I know little about so hopefully one of our more enterprise networking types can offer some suggestion if that could be where the issue lies.

If smb does not work, you can access your linux box very efficiently via NFS.

The only problem is that by default Linux considers insicure ports if above 1024.
That's the case of Mac OS X when making NFS connections.

You simply have to put the insicure flag in the /etc/exports file on your Linux server. See man pages for exports.

For example:
/pub (ro,insecure,all_squash)

I tried on my system and it works. Great!