Access Denied Between XP Box

At home, I have 2 XP boxes, PC1 and PC2. Both are on a
domain example.net *local domain*. The DC is running
Windows 2000 Server with SP4 installed. PC1 is able to
see the network shares on the DC but cannot access shares
on PC2. The same goes for PC2, it can access shares on
the DC but not PC1. Whenever clicking on the machines
name in Network Neighborhood, an error message comes up
and says the "Path is not found" and "You may not be able
to access this resource due to permissions. Please
contact administrator...." I have checked permissions for
all user accounts and have found that everyone is allowed
access. I have checked connectivity using ping and made
sure all ICF (firewalls) are disabled. Why is it that the
XP boxes can see the DC but are not allowed to access
each other.

Please help. Thank you in advance.

Thomas

Also, is it possible to remotely manage the Active
Directory from one of the XP machines instead of
configurating the settings physically at the DC? I
installed the Windows 2003 adminpak.msi on XP but it
won't let me now. Keeps saying that I need to upgrade the
DC to SP4 (which I did).

Your XP boxes may not be correctly registered in the example.com domain
Check the W2K server DNS and see if your boxes register and de-register
dynamically. If not, check your DNS installation - a DC DNS should not be
installed as root, that's a common trap.

If everything seems to be ok, I would remove the machines from the domain,
delete the computer accounts on the DC and then rejoin.

Ovidiu Popa
MVP

"Thomas N" <anonymous@discussions.microsoft.com> wrote in message
news:20c7f01c4594c$b3ba8af0$a001280a@phx.gbl...
> At home, I have 2 XP boxes, PC1 and PC2. Both are on a
> domain example.net *local domain*. The DC is running
> Windows 2000 Server with SP4 installed. PC1 is able to
> see the network shares on the DC but cannot access shares
> on PC2. The same goes for PC2, it can access shares on
> the DC but not PC1. Whenever clicking on the machines
> name in Network Neighborhood, an error message comes up
> and says the "Path is not found" and "You may not be able
> to access this resource due to permissions. Please
> contact administrator...." I have checked permissions for
> all user accounts and have found that everyone is allowed
> access. I have checked connectivity using ping and made
> sure all ICF (firewalls) are disabled. Why is it that the
> XP boxes can see the DC but are not allowed to access
> each other.
>
> Please help. Thank you in advance.
>
> Thomas
>
> Also, is it possible to remotely manage the Active
> Directory from one of the XP machines instead of
> configurating the settings physically at the DC? I
> installed the Windows 2003 adminpak.msi on XP but it
> won't let me now. Keeps saying that I need to upgrade the
> DC to SP4 (which I did).

Well...looks like I solved part of the problem but now
new problems have surfaced. I enabled NetBIOS over TCP/IP
on PC1 and now it can access shares from the DC and PC2
but the DC and PC2 cannot access shares from PC1. DC and
PC2 can see each other fine. All machines are able to
ping each other. Whenever trying to access PC1 from the
other two, I get error message "The network path was not
found."

The DC is not on a root dns. It's record is
DC1.domain.home.net. Looks like PC1 isn't getting
registered in the DNS either.

Also, all machines are connected to a Linksys broadband
router. PC1 and PC2 get ip addresses using the router's
DHCP. DC is assigned a static but in the same subnet
192.168.1.x. Whenever I ping any machine from another
machine, all give me responses from 64.49.213.239 (I'm
guessing this is the DSL public IP?).

>-----Original Message-----
>Your XP boxes may not be correctly registered in the
example.com domain
>Check the W2K server DNS and see if your boxes register
and de-register
>dynamically. If not, check your DNS installation - a DC
DNS should not be
>installed as root, that's a common trap.
>
>If everything seems to be ok, I would remove the
machines from the domain,
>delete the computer accounts on the DC and then rejoin.
>
>Ovidiu Popa
>MVP
>
>"Thomas N" <anonymous@discussions.microsoft.com> wrote
in message
>news:20c7f01c4594c$b3ba8af0$a001280a@phx.gbl...
>> At home, I have 2 XP boxes, PC1 and PC2. Both are on a
>> domain example.net *local domain*. The DC is running
>> Windows 2000 Server with SP4 installed. PC1 is able to
>> see the network shares on the DC but cannot access
shares
>> on PC2. The same goes for PC2, it can access shares on
>> the DC but not PC1. Whenever clicking on the machines
>> name in Network Neighborhood, an error message comes up
>> and says the "Path is not found" and "You may not be
able
>> to access this resource due to permissions. Please
>> contact administrator...." I have checked permissions
for
>> all user accounts and have found that everyone is
allowed
>> access. I have checked connectivity using ping and made
>> sure all ICF (firewalls) are disabled. Why is it that
the
>> XP boxes can see the DC but are not allowed to access
>> each other.
>>
>> Please help. Thank you in advance.
>>
>> Thomas
>>
>> Also, is it possible to remotely manage the Active
>> Directory from one of the XP machines instead of
>> configurating the settings physically at the DC? I
>> installed the Windows 2003 adminpak.msi on XP but it
>> won't let me now. Keeps saying that I need to upgrade
the
>> DC to SP4 (which I did).
>
>
>.
>

I just checked the local DNS again and it looks like PC2
doesn't register either, yet it's shares are able to be
viewed. Now I am thoroughly frustrated.

>-----Original Message-----
>Well...looks like I solved part of the problem but now
>new problems have surfaced. I enabled NetBIOS over
TCP/IP
>on PC1 and now it can access shares from the DC and PC2
>but the DC and PC2 cannot access shares from PC1. DC and
>PC2 can see each other fine. All machines are able to
>ping each other. Whenever trying to access PC1 from the
>other two, I get error message "The network path was not
>found."
>
>The DC is not on a root dns. It's record is
>DC1.domain.home.net. Looks like PC1 isn't getting
>registered in the DNS either.
>
>Also, all machines are connected to a Linksys broadband
>router. PC1 and PC2 get ip addresses using the router's
>DHCP. DC is assigned a static but in the same subnet
>192.168.1.x. Whenever I ping any machine from another
>machine, all give me responses from 64.49.213.239 (I'm
>guessing this is the DSL public IP?).
>
>>-----Original Message-----
>>Your XP boxes may not be correctly registered in the
>example.com domain
>>Check the W2K server DNS and see if your boxes register
>and de-register
>>dynamically. If not, check your DNS installation - a DC
>DNS should not be
>>installed as root, that's a common trap.
>>
>>If everything seems to be ok, I would remove the
>machines from the domain,
>>delete the computer accounts on the DC and then rejoin.
>>
>>Ovidiu Popa
>>MVP
>>
>>"Thomas N" <anonymous@discussions.microsoft.com> wrote
>in message
>>news:20c7f01c4594c$b3ba8af0$a001280a@phx.gbl.. .
>>> At home, I have 2 XP boxes, PC1 and PC2. Both are on a
>>> domain example.net *local domain*. The DC is running
>>> Windows 2000 Server with SP4 installed. PC1 is able to
>>> see the network shares on the DC but cannot access
>shares
>>> on PC2. The same goes for PC2, it can access shares on
>>> the DC but not PC1. Whenever clicking on the machines
>>> name in Network Neighborhood, an error message comes
up
>>> and says the "Path is not found" and "You may not be
>able
>>> to access this resource due to permissions. Please
>>> contact administrator...." I have checked permissions
>for
>>> all user accounts and have found that everyone is
>allowed
>>> access. I have checked connectivity using ping and
made
>>> sure all ICF (firewalls) are disabled. Why is it that
>the
>>> XP boxes can see the DC but are not allowed to access
>>> each other.
>>>
>>> Please help. Thank you in advance.
>>>
>>> Thomas
>>>
>>> Also, is it possible to remotely manage the Active
>>> Directory from one of the XP machines instead of
>>> configurating the settings physically at the DC? I
>>> installed the Windows 2003 adminpak.msi on XP but it
>>> won't let me now. Keeps saying that I need to upgrade
>the
>>> DC to SP4 (which I did).
>>
>>
>>.
>>
>.
>