I'm well-versed with 2K but am an absolute newbie with XP. Our company recently (today) has migrated all of our desktop systems to XP/ActiveDirectory.

I use my personal notebook alongside my work PC, since my corporate issue one just doesn't cut it for what I want. My notebook is 2K, previously my desktop was 2K.

I created a share for the My Documents directory on my desktop PC, and mapped it to my notebook and then made it available offline. Net result was I could synch my work files before I left the office, and work on them at home without having to connect via our VPN, and any changes would be re-synched the next morning. Worked great.

Now, with XP, I've created a new map for the My Documents directory, and I have been able to map it from my notebook with no issues. I can access any files there, but the problem is that I can't write any files from my notebook to the share. Every time I do I get an error message claiming access denied, the source file may be in use (which isn't the case). Since the problem happened with every file I tried to write to the mapped drive, I'm attributing the issue to permissions on the share (ie. read-only).

I've checked the permissions on the share, I went from allowing only my account access to allowing Everyone total control, and still no dice. Tried creating new shares on different folders and the same result. I'm at a bit of a loss...

With our setup, my desktop is part of a domain but my notebook is standalone, and not connected to the domain. I'm able to establish the map by using my domain credentials (domain\username) so I don't think that's the issue. Our SE that came to our office for the migration is at a loss for why I can't do it. I also have local admin privileges on my desktop if that makes a difference (although I'm not a domain admin).

Since I'm new to XP, I'm wondering if I'm overlooking something obvious. Also, is it possible that something in our Group Policy is preventing me from creating a share that allows anything more than read-only access? The other thing I've noticed that is peculiar (to me) is the fact that whenever I check the properties for a folder (locally, not applied to the share), it is flagged as read-only. I can disable that, and it migrates the changes to all files and sub-folders, but once I apply and then check again, it's back to read-only. I haven't seen this on Win2K, could this be the problem? I have no issues writing to the folders locally.

Anyways, sorry for the long-winded post, just wanted to be as specific as possible.

Any help or input would be greatly appreciated...!

Cheers,
KV