Hi, I don't know if you ever got this resolved. I didn't see anything on the list though. So, here's my take on it... Comments inline. > -----Original Message----- > > Hi. > I got a strange problem. > About a year ago I set up a windows 2000 server to act as a > file server for some old, old macintosh. There where no problem. > Today when I do the same I got some strange problem. First I > made AD that also shared files. The old macintosh computer could read from > the share, but not write. Apple shares are "read-only" by default for some strange reason. Check the share properties of the Macintosh share in question and uncheck the option "This volume is read-only". > I worked a lot with users and rights to this > share. So I reinstalled and set it up as a singel server with file > sharing, and now they can't even connect to the share or see it. When trying > to connect directly to the ip address, it complaining about the protocol > or something like that. > I also tryed from a new macintosh, with the same result. What did you reinstall? The server OS? If so, did you also install "filesharing for Macintosh"? /Dan Manell ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=147 ********************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm