XP W2K networking problem

[Casian Moscovici]

Hi everyone

I recently added a new XP Professional PC to an existing home network
consisting of two XP machines and one W2K. The three older computers all
see each other and share folders. The new computer can access the two XP
machines (and vice versa) but not the W2K machine, although it does see
the computer name. Equally, the W2K computer can't access files or
folders on the new XP computer although it does see it.

I've checked and rechecked the users, shares and security settings and
all appear to be fine. If they weren't, the older machines wouldn't be
able to share resources, nor would all three XP machines including the
new one. The only problem is between the new XP and the W2K.

I'm stumped and exasperated and would appreciate some fresh ideas. What
am I missing here?

Thanks for your help.

 

[Pegasus \(MVP\)]

Hi everyone

I recently added a new XP Professional PC to an existing home network
consisting of two XP machines and one W2K. The three older computers all
see each other and share folders. The new computer can access the two XP
machines (and vice versa) but not the W2K machine, although it does see
the computer name. Equally, the W2K computer can't access files or folders
on the new XP computer although it does see it.

I've checked and rechecked the users, shares and security settings and all
appear to be fine. If they weren't, the older machines wouldn't be able to
share resources, nor would all three XP machines including the new one.
The only problem is between the new XP and the W2K.

I'm stumped and exasperated and would appreciate some fresh ideas. What am
I missing here?

Thanks for your help.

Start by going through the basic steps:
- Turn off the WinXP firewall.
- Ping the WinXP PC from the Win2000 PC.
- Map a shared drive on the Win2000 PC by running this command:
net use Q: \\WinXP-PC\SomeShareName
It is essential that you run these commands from the Command Prompt.

 

[Steve Winograd]

Hi everyone

I recently added a new XP Professional PC to an existing home network
consisting of two XP machines and one W2K. The three older computers all
see each other and share folders. The new computer can access the two XP
machines (and vice versa) but not the W2K machine, although it does see
the computer name. Equally, the W2K computer can't access files or
folders on the new XP computer although it does see it.

I've checked and rechecked the users, shares and security settings and
all appear to be fine. If they weren't, the older machines wouldn't be
able to share resources, nor would all three XP machines including the
new one. The only problem is between the new XP and the W2K.

I'm stumped and exasperated and would appreciate some fresh ideas. What
am I missing here?

Thanks for your help.

How are you trying to access the W2K machine from the new computer?
What exactly happens when you do it? If there's an error message,
what does it say?

How are you trying to access the new XP computer from the W2K
computer? What exactly happens when you do it? If there's an error
message, what does it say?

Have you set up matching user accounts (same name and password) on all
computers?
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Desktop Experience)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Casian]

Start by going through the basic steps:
- Turn off the WinXP firewall.
- Ping the WinXP PC from the Win2000 PC.
- Map a shared drive on the Win2000 PC by running this command:
  net use Q: \\WinXP-PC\SomeShareName
It is essential that you run these commands from the Command Prompt.

Hi, I'm replying from a different account. The ping worked but net use
just generated error 67 - network name could not be found. I didn't
make the linkn before, but I'm thinking that the fact the two PCs are
networked wirelessly may be an issue. The older XP PCs and the W2K PC
are all physically wired to a router. The new XP is connecting through
a wireless bridge to the router, though this doesn't seem to bother
the other XP PCs. The wireless network name is not the same as the
workgroup name. Could this be the problem?

Casian

 

[Pegasus \(MVP\)]

Start by going through the basic steps:
- Turn off the WinXP firewall.
- Ping the WinXP PC from the Win2000 PC.
- Map a shared drive on the Win2000 PC by running this command:
net use Q: \\WinXP-PC\SomeShareName
It is essential that you run these commands from the Command Prompt.

Hi, I'm replying from a different account. The ping worked but net use
just generated error 67 - network name could not be found. I didn't
make the linkn before, but I'm thinking that the fact the two PCs are
networked wirelessly may be an issue. The older XP PCs and the W2K PC
are all physically wired to a router. The new XP is connecting through
a wireless bridge to the router, though this doesn't seem to bother
the other XP PCs. The wireless network name is not the same as the
workgroup name. Could this be the problem?

Casian

===============

The network name matters when discovering machines automatically but it is
irrelevant for the "net use" command. I would now do this:
- Map a share by IP address:
net use Q: \\aaa.bbb.ccc.ddd\SomeShareName
- Connect the machines with a wired link.

 

[Casian Moscovici]

Hi, I'm replying from a different account. The ping worked but net use
just generated error 67 - network name could not be found. I didn't
make the linkn before, but I'm thinking that the fact the two PCs are
networked wirelessly may be an issue. The older XP PCs and the W2K PC
are all physically wired to a router. The new XP is connecting through
a wireless bridge to the router, though this doesn't seem to bother
the other XP PCs. The wireless network name is not the same as the
workgroup name. Could this be the problem?

Casian

===============

The network name matters when discovering machines automatically but it is
irrelevant for the "net use" command. I would now do this:
- Map a share by IP address:
net use Q: \\aaa.bbb.ccc.ddd\SomeShareName
- Connect the machines with a wired link.

Thanks for your help. It turned out to be an issue with the Comodo
firewall. I still don't understand why and how Comodo only blocked
communication between these two particular PCs, but once I tweaked some
obscure firewall settings on both PCs the problem resolved.

Casian

 

[Pegasus \(MVP\)]

Thanks for your help. It turned out to be an issue with the Comodo
firewall. I still don't understand why and how Comodo only blocked
communication between these two particular PCs, but once I tweaked some
obscure firewall settings on both PCs the problem resolved.

Casian

Thanks for the feedback. Firewalls are a common cause in such cases, which
is why I recommended that you should turn it off for your tests.