Re: Win XP Pro to Win XP Pro network share

Hi,

Thanks, I was able to get this working properly... please see below.

"zuben3@xxxxxxxxx" wrote:

- Make sure they're both part of the same workgroup.

Yes, they were. Forgot to mention this in my last post.

- Permissions set to the root (C:\ in your case) aren't all inherited
by the profiles in Docs&Settings, if that's where your target data
lives (most likely so).

Right. Most of the data was in the old profile, but I wanted to have full
access to the drive, to look around. As you mentioned, this didn't allow
browsing to the old profile (using the temp. transfer profile), so I got
around that by sharing that profile as well. ("Simple File Sharing" was
enabled, and this was the easiest way to handle it, rather than booting into
Safe Mode and changing permissions there)

- You can try creating a profile called "Transfer" or something just
for this temporary task on both computers. Use the same username and
password and make sure it's part of the administrators group and
remove it from the users (limited) group.

This is what resolved the problem. I guess the problem was due to not
verifying that the username / password on both computers was the same --
although the same username was being used, there was a "hidden" password on
the old account (as I had set this up about three years back, and haven't
visited this client since, I forgot about this), so that it could run
scheduled backups using Task Scheduler. I guess this was causing a
credentials problem. I used your method, creating a new Administrator
profile on both computers, and that connected just fine. I didn't bother to
check / remove them from the "Users" group, since (in my understanding) that
would only be restrictive where Administrator priviledges had not been
assigned. The only issue I had with this was getting into the old profile,
which I bypassed by sharing it (as above).

I guess the best solution to this problem would be to ensure the new profile
and old profile username / password match on both computers, which would
allow access to the old profile.

- Don't use the Guest profile--it's limitations are substantial. Kill
it for security reasons even still.

Yes, agreed. I didn't think this through fully, when connecting. By
default, it isn't enabled (so that's fine for the new computer), and as I
mentioned, the old HD was to be wiped anyways, so that wasn't an issue.

- Ensure source machine doesn't have any program or process using the
file(s) you're trying to copy. You can't copy the profile the source
machine is logged on with. The temporary profile you create will get
around this.

This is true only for the "ntuser" (profile) file, but the rest of the data
(i.e. My Documents) would certainly be able to be copied. I prefer starting
fresh in these cases, in case there's corruption in the old profile.

I didn't test this, but if the files are being accessed remotely (i.e. over
the network), would the profile be necessarily logged in on the source
machine? I imagine not, so even this wouldn't be an issue. I'm guessing the
profile on the source machine can be logged off, and the files can still be
accessed.

Best Wishes,
Kurosh
.

Relevant Pages

  • Re: change from domain to workgroup
    ... Since you can log on as the local administrator, ... You should be able to access most everyting in your old profile ... > username and password. ... > i think it expects that i run the programm with my old username. ...
    (microsoft.public.win2000.general)
  • Re: change from domain to workgroup
    ... Since you can log on as the local administrator, ... You should be able to access most everyting in your old profile ... > username and password. ... > i think it expects that i run the programm with my old username. ...
    (microsoft.public.win2000.security)
  • RE: User template question
    ... Account tab). ... A new logon script was also assigned from the Profile tab. ... I'm afraid that your purpose cannot be achieved through User Template. ... Deploys software to user computers. ...
    (microsoft.public.windows.server.sbs)
  • Re: XP SP2 Firewall selects Standard profile when computer is properly
    ... Is this with IBM Thinkpads or other makes and models of computers also? ... >> nearly always) selects the Standard firewall profile. ... >> connected to the network via Ethernet cable. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Assigning user profiles based on OU
    ... the computers via Group Policy. ... > to user student workstations and pull the student profile. ... create OU's for specific client machine sets and apply ... If the policy settings are specific to the ...
    (microsoft.public.win2000.group_policy)