windows / samba issue? | ||||||
| posted by Greg Whynott on Dec. 5, 2013, 5:40 p.m. (6 days ago) | ||||||
| ||||||
| Thread Tags: discuss-at-studiosysadmins | ||||||
| ||||||
ran into a situation which i'm trying to wrap my head around. hopefully someone has seen this before. our file servers have areas exported via CIFS and NFS from both Blue Arc's and Nexenta's.share1 has the a few directories in it, and sub dirs. so: share1/folder1/subfolder1 all is good. now lets jump onto a windows machine and navigate to the Q: network drive (no dfs). we are now at Q: dir folder1 foobar 'dir folder1' returns expected results, as does 'dir foobar' 'cd folder1' and 'cd foobar' work as expected. ok all is good up to this point. now if we create a sym link beyond the 'folder1' level, we run into issues: back on unix at the base level we type: ln -s folder1/subfoler1 barfoo test it from unix, works as expected for both ls and cd. back on windows at the base of Q:: dir folder1 foobar barfoo ls barfoo we see subfolder1 get listed, as expected. cd barfoo returns an error: The system cannot find the path specified. all the folders and sub folders are on the same file system, no dfs or submounts. It can list the contents of the directory but can not cd into it.... This works on Blue Arc but it fails as described above on any shares on the Nexenta system. Any clues to offer? have packet traces should you care to see. -g |