Re: Win XP Pro to Win XP Pro network share

On Sep 16, 5:54 am, Kurosh <Kur...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,

I was setting up a new computer for a client yesterday (going back today to
finish a few things), and normally I would just take the HD out and put it in
the new computer, to transfer the data. In this case, he has IDE drives in
the old computer, and only S-ATA connections in the new. I opted to copy the
data via Ethernet (cross-over cable) instead, but ran into a connection
problem that I haven't seen before: "The requested resource is in use." I
did a Google search on this, and noted a lot of "ASP" solutions, but this is
a simple network connection (two Win XP Pro machines), not involving a web
server.

Here's what I tried:

1. On the old computer, shared the root of the drive (C:) with network
users, and allowed them to make changes. Also, unchecked "Make this folder
private" for My Documents.

2. Set the IP address of the old computer to 192.168.1.2

3. Set the IP address of the new computer to 192.168.1.1

4. Enabled the Guest account on the old computer (via the "User Accounts"
control panel applet)

5. Both computers run NIS (the old one running 2006, the new running 2008),
so I tried disabling both, then I tried enbling both and allowing the IPs to
be "trusted", then I tried uninstalling NIS 2006 and Windows Defender on the
old computer (the HD is going to be wiped anyways after the data transfer).

I can ping the old computer (no problems) by IP address from the new
computer. I get the above error message when going to Run > \\192.168.1.2
from the new computer. I also tried going to Run > \\192.168.1.2\c$, and I
get the logon box, trying to connect to <computername>\Guest.

Any suggestions? I'm going to verify that the old computer has all the
latest patches (the new one does), and put it into a "clean boot" (to try to
rule out background processes interfering). If I can't resolve this fairly
quickly this morning (I'll be there in about 3 hours from now), we'll just
get an external HD and copy the data over (which my client was thinking to
get anyways, to facilitate backups).

Thanks,
Kurosh

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

- 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).

- 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.

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

- If that doesn't work, try setting specific shares and add Transfer
(or whatever profile you're using) to the ACL with Full Control.

- Check ownership of the problem directory on source computer.

- Make sure files/dirs aren't locked or set to private.

- Reboot both machines for good measure.

- 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.

- Do both computers show up on both network browsers? Do all their
shares?

- Can you type in a UNC like \\SourceComp\C$ instead of the IP? How
about after setting the specific share with proper permissions? Like: \
\SourceComp\SomeDirectory\SomeChildDir\TargetShare You shouldn't need
to if they're both XP Pro since the network browser will reveal all
the shares for that computer you setup. Then it's just a matter of
access permissions.

Good luck!

.

Relevant Pages

  • Re: AD with WINXP
    ... > Email client: Outlook ... Clients machines that are ... > keep the user profile for the client machine? ...
    (microsoft.public.windowsxp.setup_deployment)
  • AD with WINXP
    ... Email client: Outlook ... Clients machines that are ... keep the user profile for the client machine? ...
    (microsoft.public.windowsxp.setup_deployment)
  • AD issue with NEW domain
    ... Email client: Outlook ... Clients machines that are ... keep the user profile for the client machine? ...
    (microsoft.public.windowsxp.general)
  • Re: Script help
    ... > configure the machines to auto-logon to that account. ... > need the script, just log on the account and add the printer, followed by ... This would not only prevent profile buildup, ...
    (microsoft.public.windows.server.scripting)
Loading