Hi Jen:
OK, it's the "Microsoft Exchange Server" that's confusing me. I *think*
your Admin has set it up so that your "File Server" is on the same computer
as the "Exchange Server".
There's no reason he wouldn't do that, and that will work just fine. It
confused me with the reference to "Exchange server" because "Exchange" is an
email server that has Public Folders whose behaviour is quite different.
You, I think, are talking about "File folders" on the "File Server".
In which case, the issue almost certainly IS the "UID" issue, and it's not
something you should have to fix for yourself. That's what your System
Administrator is paid all those bucks to worry about.
In the article I sent you, there are links to two Apple articles that
describe how to correct the issue. The articles are specifically written to
be understood my trained network engineers, because if you go fiddling
around with this stuff when you are not a trained network engineer, you can
knock your computer off the network and be unable to get it to reconnect
However, the basis is that when Unix starts up, it assigns a User ID of
"501" to the local user. It then expects the network login to correct this
by supplying a new UID that is unique on the network.
Your System Administrator is responsible for ensuring that this will happen,
and the Apple article gives procedures for doing this.
In a small company, there is nothing to prevent him from visiting each Mac
and manually entering the user IDs. In fact, he can talk you through this
over the phone so you could do it yourself.
However, the key is that to be able to make this change, you must have
"root" authentication on the local machine, and you must already know the ID
you are going to assign.
Your Sys Admin has to supply both those pieces of information
Cheers
Hi John,
Thank you for your response. Our server is on a microsoft exchange
server (2003 I believe and all up to date w/upgrades) and we were able
to create files and move documents onto the server in the various
folders but now can only open and view, cannot make changes and
'resave' documents to the server. If we open the doc from the server,
make changes, save to our local hard drive then drag and drop back
into the server folder, then it works, but for some reason the ideal
scenario of opening a doc, updating, then simply clicking 'save' is
not working. We receive the following message:
The disk is full. Free some space on this drive, or save the document
on another disk. Try one or more of the following:
*Close any unneeded documents, programs and windows.
*Save the document on another disk.
Our network admin said we have 98% free space on the server and he
also checked the server settings to make sure that we all have read/
write capabilities and full permissions, and we do, so I'm just not
sure why this is happening.
We've tried all the workarounds/possible solutions except for the "
change your UID" recommendation from the mvp site as I have never
worked with UID's before and not sure I fully understand. Any
insight? Any other recommendations on websites/groups to check?
Again, thank you John! ~Jen
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <
[email protected]>
Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant
Technical Writer.
Sydney, Australia +61 (0) 4 1209 1410
