Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade to 2003 - Now Macs can't access drives!

Status
Not open for further replies.

ccaathl

MIS
Mar 7, 2001
35
US
Hello,

I recently upgraded our file store from Windows 2000 Server to Server 2003.

Now none of our Macintosh clients can access their work.

Passwords, usernames, sharing and permissions are all the same as before. I cna even log them onto the old file store with the out of date files and they connect fine.

Hope that someone can help!
Many thanks, T
 
Hello
Sorry about the delay in replying, have had a small holiday. Enough excuses, these suggested solutions unfortunately don't work.
I followed the Microsoft way and installed Mac file support. Then I installed the UAM tool downloaded from MS.
This seemed to install well on the Macs.
They are running OS X.
I created a brand new share on the 2003 server. I set this up to be a Mac based share. Still no one can connect to it.
Anyone have any suggestions?
Thanks, Tom L
 
We had a similar issue put the server address in the host file
 
Hi,
this is what i've been doing. I've tried the netbios name and the IP address - neither work.
I believe it to be a problem with the server rather than the clients - they connected to the Windows 2000 server with no problems at all.
 
Hello

I have finally managed to work out why this was not working.

I added the utility to the Macintosh workstations.
Then I created a share from within Computer Management on the new Windows Server 2003 machine. This share had the same name as the PC share, only it was accessible to Mac users only.

Then, back to the Macs. I chose the server "AFP://192.168.1.1/shared"
Putting AFP was the key part!
(Before, on Windows 2000 Server, you typed the server address and share name "SMB://192.168.1.1/shared" into the Macintosh.)

Now authenticated accessing the files was just as before.

Thanks for all the suggestions, they all helped in getting to the final answer!
Regards, T
 
Hello

I have finally managed to work out why this was not working.

I added the utility to the Macintosh workstations.
Then I created a share from within Computer Management on the new Windows Server 2003 machine. This share had the same name as the PC share, only it was accessible to Mac users only.

Then, back to the Macs. I chose the server "AFP://192.168.1.1/shared"
Putting AFP was the key part!
(Before, on Windows 2000 Server, you typed the server address and share name "SMB://192.168.1.1/shared" into the Macintosh.)

Now authenticated accessing the files was just as before.

Thanks for all the suggestions, they all helped in getting to the final answer!
Regards, T
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top