Inability for Mac OS X 10.4 and 10.5 to view shares when connecting via SMB to 2008 R2 Cluster running File Services

inability mac os x 10.4 , 10.5 view shares when connecting via smb 2008 r2 cluster running file services

 

 

environment defined following:

 

servers:

 

file server cluster "filecluster"

two 2008 r2 enterprise servers hosting failover cluster providing file services (smb only) - fresh installation , put production.  located in "server" subnet.  running on hp bl460cg6 , connected 3par inserve t800 via qlogic fc mezzanine adapters -> brocade 8gb fc c7000 chassis switches -> inserv fc adapters.

 

file server standalone "sparky"

1 2008 r2 standard being used workstation - in-place upgraded 2008 sp1 sp2 r2 (over several months).  located in "user" subnet.  local sata storage used testing.

 

workstations:

 

1 mac running os x 10.6.2

1 mac running os x 10.5.8

1 mac running os x 10.4.11

 

above workstations in "user" subnet.

 

users:

 

all users domain users appropriate rights shares, , ntfs level permissions confirmed correct.  access windows machine provides desired results.

 

 

issue synopsis

 

access windows device on smb either directly file share on "filecluster" client access point or via dfs works fine.  access "sparky" hosted shares work.

 

access mac device running 10.5.8 or 10.4.11 on smb "filecluter" client access point fails via connection string of "smb://<fqdn>/".  the share enumeration screen appears, no shares listed.

 

access mac device running 10.5.8 on smb “filecluster” client access point fails via connection string of “smb://<fqdn>:139/”.  the share enumeration screen appears, no shares listed.

 

access mac device running 10.5.8 on smb “filecluster” client access point succeeds via connection string of “smb://<fqdn>:139/<share name>”.  share connected successfully.

 

access mac device running 10.4.11 on smb “filecluster” client access point succeeds via connection string of “smb://<fqdn>/<share name>”.  share connected successfully.

 

access mac device running 10.6.2 on smb “filecluster” client access point succeeds via connection string of “smb://<fqdn>/”.  shares enumerated correctly.

 

access mac device running 10.6.2 on smb “filecluster” client access point succeeds via connection string of “smb://<fqdn>/<share name>”.  share connected successfully.

 

access mac device (any version) on smb “sparky” server succeeds via connection string of “smb://<fqdn>/” share enumeration.

 

access mac device (any version) on smb “sparky” server succeeds via connection string of “smb://<fqdn>/<share name>”.  share connected successfully.

 

 

essentially, goal mac users able enumerate shares.

 

i’ve started building test cluster utilizing similar hardware, storage, , os configurations – meaning hp bl460 blades, 3par inserve storage, , 2008 r2.  the goal of test determine whether or not client access point can service share enumeration requests 10.4 , 10.5 clients.  i’ve tested out pre-cluster (still building 2^nd node) , far works fine 10.4 , 10.5 mac clients connect via “smb://<fqdn>/” , enumerate shares.

 

if has run before, great hear how fixed – if can – or more details others plan on utilizing pss once have findings validated via test cluster.

i believe has been fixed in snow leopard, contact apple confirmation / more information.

as workaround, can configure use port 139 and connect using the netbios name in url doing following in nsmb.conf:

example:
echo "[default]" >  ~/library/preferences/nsmb.conf
echo "port445=netbios_only" >> ~/library/preferences/nsmb.conf

then thconnect url has netbios name in it, example smb://<netbiosname>:139/<share>

there following requirements cluster nodes:

• netbios must enabled on cluster nodes
• ntlmv2 response should changed lm , ntlm, ntlmv2 if negotiated

thanks!
elden

Windows Server  >  High Availability (Clustering)