Mapping network drive from W2K to XPpro

[Guest]

I ran into a problem that drives me nuts:

A small Windows 2000 workgroup, everything's working just fine. Now I
ve added one WinXP-SP2 machine, clean install (no upgrade). All static IPs
in the 10.0.0.xxx space, netmask 255.255.255.0.

While the Win2000 machines can map each other's drives just fine, the XP
machine can map drives on the Win2000 machines but the Win2000 machines can
NOT map drives on the XP machine.

And that's my problem.

When I try to map an XP drive from a Win2000 machine, a dialog comes up
asking for username/password. This already should not happen because both
machines are logged into with the same user/pw already. When I type the
username/pw into the dialog, it comes back that "either the user does not
exist or the password is incorrect".

Same thing happens when I just open "network neighborhood" on any of the
Windows 2000 machines - I can see the XP machine, but when I click on it I
get the same username/pw dialog box, rejecting the valid user/pw.

It DOES, however, work the other way around: The XP machine can open any of
the Win 2000 computers, or map their drives.

From the command prompt, I CAN ping the XP machine just fine from any of the
Win2000 machines on the network (and vice versa), so it does not seem to be
an IP problem.

I am good at Win2000 but new at XP. The XP machine is a clean install,
everything at defaults, just the firewall is turned off to get it out of the
way. It looks to me like the problem must be SOME setting on the XP machine,
either in the network setup or in some policy, or some authentication
requirement, that prevents me from connecting to the XP machine from the Win
2000 machines. And it must be some default setting, because except for
turning off the firewall I haven't changed anything yet.

PLEASE pretty please, anyone has any ideas?

 

[Chuck]

I ran into a problem that drives me nuts:

A small Windows 2000 workgroup, everything's working just fine. Now I
ve added one WinXP-SP2 machine, clean install (no upgrade). All static IPs
in the 10.0.0.xxx space, netmask 255.255.255.0.

While the Win2000 machines can map each other's drives just fine, the XP
machine can map drives on the Win2000 machines but the Win2000 machines can
NOT map drives on the XP machine.

And that's my problem.

When I try to map an XP drive from a Win2000 machine, a dialog comes up
asking for username/password. This already should not happen because both
machines are logged into with the same user/pw already. When I type the
username/pw into the dialog, it comes back that "either the user does not
exist or the password is incorrect".

Same thing happens when I just open "network neighborhood" on any of the
Windows 2000 machines - I can see the XP machine, but when I click on it I
get the same username/pw dialog box, rejecting the valid user/pw.

It DOES, however, work the other way around: The XP machine can open any of
the Win 2000 computers, or map their drives.

From the command prompt, I CAN ping the XP machine just fine from any of the
Win2000 machines on the network (and vice versa), so it does not seem to be
an IP problem.

I am good at Win2000 but new at XP. The XP machine is a clean install,
everything at defaults, just the firewall is turned off to get it out of the
way. It looks to me like the problem must be SOME setting on the XP machine,
either in the network setup or in some policy, or some authentication
requirement, that prevents me from connecting to the XP machine from the Win
2000 machines. And it must be some default setting, because except for
turning off the firewall I haven't changed anything yet.

PLEASE pretty please, anyone has any ideas?

Is the account in question properly activated for network access on both
computers?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>

Check for misconfigured / overlooked firewalls, and for registry setting
restrictanonymous, on both computers, too.
Misconfigured / overlooked firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

 

[Guest]

Hi Chuck:

Gosh, that was fast !! Not only that, it also solved my problem.

Firewall wasn't it; this is a fully self-contained subnet with no outside
access so there are no firewalls needed (the XP box has it also disabled).

It was, though, the "network access" setting on the XP box. In Win2000,
there's no such thing needed. You install the OS and you're done; you can map
to the box from anywhere, to any drive, as long as you have the proper
username/pw credentials.

Seems like not so on the XP box. I went through the Network Setup wizard,
and that made the box accessible from the Win2000 machines via Network
Neigborhood. But still no drive mapping possible.

That was finally solved by setting the entire drive as "shared". Again,
nothing like that was required on the Win2000 boxes; I can map to them simply
by using the default shares (\\machinename\c$, etc.)

So thanks again for pointing me the right direction, Chuck. Could you please
just briefly confirm if I have it right:

On an XP machine, first I must run the Network wizard to make it accessible
by other boxes on the network, and secondly I must set all drives I want to
map to as "shared". Correct?

Thank you.

 

[Chuck]

Hi Chuck:

Gosh, that was fast !! Not only that, it also solved my problem.

Firewall wasn't it; this is a fully self-contained subnet with no outside
access so there are no firewalls needed (the XP box has it also disabled).

It was, though, the "network access" setting on the XP box. In Win2000,
there's no such thing needed. You install the OS and you're done; you can map
to the box from anywhere, to any drive, as long as you have the proper
username/pw credentials.

Seems like not so on the XP box. I went through the Network Setup wizard,
and that made the box accessible from the Win2000 machines via Network
Neigborhood. But still no drive mapping possible.

That was finally solved by setting the entire drive as "shared". Again,
nothing like that was required on the Win2000 boxes; I can map to them simply
by using the default shares (\\machinename\c$, etc.)

So thanks again for pointing me the right direction, Chuck. Could you please
just briefly confirm if I have it right:

On an XP machine, first I must run the Network wizard to make it accessible
by other boxes on the network, and secondly I must set all drives I want to
map to as "shared". Correct?

Thank you.

I'm glad that this worked for you, but it should not be necessary this way.
Windows XP Pro systems will act just like Windows 2000 systems. If you disable
Simple File Sharing, and enable an administrative account properly.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>

And if the system was already setup, there should have been no need to run the
Network Setup Wizard again. The C$ share already exists - you just need
administrative access to it from the Windows 2000 system. This simply requires
a properly activated, non-Guest account, under Classic File Sharing. So check
your file sharing setup again.