Access issues to Admin$ on XP SP2 machines

[SBS 2003 User]

OK I'm sure this is a simple solution but for the life of me I just cannot
figure it out. I'm sure some of my professional colleagues out here in the
NG's will be able to provide some helpful insight as always.
I am in a SBS 2003 Server SP 1 and fully patched domain. I use SAV Corporate
Edition v10.1.4 which is the latest that I am upgrading to. I've loaded the
Symantec System Center onto my XP SP2 desktop so that I may control SAV from
my workstation. I've always done it this way and have never had any issues.
Now I'm trying to push out the updated clients and definitions to the
workstations. The parent server for SAV is a Windows 2003 Server SP1. I am
able to push it out to some clients and not others. Appears ths issue is a
share access problem. Meaning that from the Symantec System Center Console I
should be able to ping the workstations and be able to access them via
\\computername\Admin$. Well of course the ones I can access I have no
probelms but it appears the ones I cannot push out the updates to I cannot
acces the admin share nor ping the IP or FQDN.
All workstations are on the same network and all are obtaing IP's from the
same DHCP server. I've checked a few workstations to verify that Admin$ does
exist and it does. I've checked DNS and all are registered in both forward
and reverse lookups scopes. So my $60,000 question is what is preventing me
from pinging and access the Admin share on these machines.

 

[Gray]

So is the firewall running on the XP machines?

 

[SBS 2003 User]

Yes it is and it doesn't make a difference if I turn it off or on. I even
added and Exceptin TCP port that Symantec uses.

 

[Anthony]

"but it appears the ones I cannot push out the updates to I cannot acces
This can happen if DNS registrations are not up to date, so when you contact
PC1 it resolves to the wrong address. You either get no answer, because that
IP is not in use, or you get access denied, because that IP is actually a
different machine.
Check whether the machine you are failing to connect to has the correct
address registered in DNS,
Anthony

 

[SBS 2003 User]

Hey Anthony,
Thanks for the input. That was the first place I went to checkout was DNS
seeing how I couldn't resolved the FQDN or even ping the IP. I doubled
checked my DHCP settings on the client also to make sure the option to
register with DNS was checked. Also verified both forward and reverse
lookups in DNS.