Welcome to the MacNN Forums.

amagab · May 21, 2009, 02:48 PM

This is a really odd situation. For some reason I can't access our Xserve share from Windows. Here's a list of points:

+ xserve can be pinged from any client
+ xserve web server can be accessed through browser from any client
+ xserve share can be accessed from Mac clients
- xserve share CAN'T be accessed from Windows clients

Some please help.

Thanks!

besson3c · May 21, 2009, 08:10 PM

XServe is hardware, not software. I think you mean "OS X Server share". However, OS X supports Samba (Windows) and AFP (Apple) file sharing natively. You can share files with SSHfs and NFS. First, you'll need to establish what service is running to share files with. If it is AFP, you'll need to enable Samba, which is probably labeled as "Windows file sharing".

amagab · May 21, 2009, 08:34 PM

Thanks, I know the difference. Didn't think I needed to spell it out here.

The share is setup using AFP and Samba is enabled.

Thanks for your response and I appreciate any help I can get.

Any suggestions?

Cold Warrior · May 21, 2009, 08:36 PM

Can a domain admin account access the shares? Testing this would help confirm/deny any permissions problems.

amagab · May 21, 2009, 08:39 PM

Originally Posted by Cold Warrior

Can a domain admin account access the shares? Testing this would help confirm/deny any permissions problems.

I've tried connecting/mapping under several different accounts including an admin account but no difference. I don't think it's a permission issue because it won't even connect. When I try to connect to the share it just ends up timing out and saying it can't find or connect (sorry, I should have taken down the exact error message). I'll do that tomorrow.

Cold Warrior · May 21, 2009, 08:44 PM

Is guest access on or off? This thread mentioned guest access on/off with SMB affecting shares and mapping to them.

amagab · May 21, 2009, 11:16 PM

Originally Posted by Cold Warrior

Is guest access on or off? This thread mentioned guest access on/off with SMB affecting shares and mapping to them.

Thanks for the link. Guest account was off so I set it to on. I don't have access to a windows machine until tomorrow though so I can't test it yet.

I did find some error messages in the Windows File Service Log.....a bunch of them but here are some to show what they look like:

[2009/05/21 15:41:17, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:send_smb(656)
Error writing 4 bytes to client. -1. (Broken pipe)
[2009/05/21 15:42:18, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:get_peer_addr(1009)
getpeername failed. Error was Socket is not connected
[2009/05/21 15:42:18, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:get_peer_addr(1009)
getpeername failed. Error was Socket is not connected
[2009/05/21 15:42:18, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:write_socket_data(446)
write_socket_data: write failure. Error = Broken pipe
[2009/05/21 15:42:18, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:write_socket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2009/05/21 15:42:18, 0] /SourceCache/samba/samba-100.12/samba/source/lib/util_sock.c:send_smb(656)

Anyone know what that means?

Thanks!

amagab · May 23, 2009, 04:38 PM

I enabled Guest but it is still not working. Any other suggestions? Thanks!

amagab · May 26, 2009, 08:53 PM

I connected using VNC fine but still can't access the share through Windows Explorer. I've tried 3 different Windows machines in different locations. Someone please help! Thanks!

Cold Warrior · May 26, 2009, 09:06 PM

A few other ideas:
- try connecting using the server/share IP instead of domain name.
- try connecting while logged into the windows machine as a local user, not a domain user

- write a script to automatically map the shares at login. While researching your problem, I remember that this worked for someone else. Any kind of subtle differences though in your problem versus theirs could mean this may not work for you.

amagab · May 26, 2009, 09:11 PM

I appreciate your response. However, all our computers are local accounts. We don't have a domain. I've also tried connecting with both the IP address and the server name.....no difference.

I'll see if I can try writing some mapping script.

I forgot to mention one thing. At the time that this started happening I had changed the servers admin password. Would that cause this? I can't see why it would affect Windows users and not Mac users.

Thanks!

amagab · May 26, 2009, 09:12 PM

One more thing, our Windows users can see the Xserve in the "My Network Places" but still can't connect to it.

Cold Warrior · May 26, 2009, 09:31 PM

This article describes more about how Windows 2000 and XP connect to shares, specifically how they use credentials.

To test this, create a Windows user with the exact same name and password as your server admin account. If it will connect, then it could be an issue with how the credentials are being passed.

amagab · May 27, 2009, 06:55 PM

Originally Posted by Cold Warrior

This article describes more about how Windows 2000 and XP connect to shares, specifically how they use credentials.

To test this, create a Windows user with the exact same name and password as your server admin account. If it will connect, then it could be an issue with how the credentials are being passed.

Good suggestion! I tried creating two new profiles with the same credentials as on the Xserve but it didn't work.

swap_1712 · Aug 17, 2009, 07:43 PM

Windows users require Open directory password authentication type. Change "shadow password" from workgroup manager to "open directory" password and you should be fine.
If you are using windows vista to log in, by default vista tries to use current user account on windows to login. In this case, you will have to specify that the user which is trying to login is not present on windows but on the server itself. You can do this by entering username in the format "<server ip address>/shortname on xserve" and you should be able to get in.

Zorflieg · Aug 17, 2009, 07:57 PM

You have to allow the user SACL (Service Access Control List) access in server admin.

The problem is they might have all the access in the world everywhere else but unless they are allowed access to the AFP share service specifically it wont let you in.

Open server admin on the xserve.

Click on the name/IP of the server on the left.

Click on the settings button across the top of the control panel.

Click on the access tab.

Click services button.

Highlight AFP in the list on the left.

Drag the users you want to have access to the afp shares into the list to grant them access.

Undo all the mucking about you've been doing for the last half hour go back in the folder permissions and make sure they are right.

Viola.

Personally i think the control panel to do this is hidden in a granted logical but retardedly un user friendly place for an OS that is so user friendly in other ways. But hell what do i know...