Cant manage/connect local XPPRO SP2 clients from AD in Win2k3 STD

Very strange problem here...

Brand new w2k3 std server with latest updates installed with about 10
clients, AD, DNS, WINS, getting DHCP from Bellsouth router. Joined ws's to
domain, can login and get resources from network; server shared printers,
shared files. Can manage local groups from AD in Computers tab for about 1/2
of local machines for local admin desktop access, but cannot connect to other
machines period when double clicking on station name. Can ping IP and
Netbios station name and they both resolve to correct IP and name, &
vice/versa.

Tried taking off of domain from ws client, WinXP Pro, SP2 latest updates,
rebooting client, deleting station name in computers in AD, rejoining
sucessfully to domain using administrator credentials; same problem.

Other info: I initially setup this server at home on my network. When I got
to the site where I was installing it at, had to change internal NIC TCPIP
properties for gateway & DNS from 192.168.1.1 to 192.168.1.254 to match local
network. Rebooted server and no entried in Event Viewer saying there were
problems related to those changes.

Then, that is causing me other problems with pushing AV clients down. Any
suggestions? Your help would be MOST appreciated.

Other questions: for testing purposes, how do I 'flush' out WINS cache?
More importantly, how do I manually 'force' AD to make any changes I've made
to happen right then instead of waiting a period of time for AD changes to
take effect?

Thank you ahead for your time - Billy

cannot connect to other machines period when double clicking on station
name: what's the error message? It could be the permission issue.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"justfishing" <(E-Mail Removed)> wrote in message
news:FC1EDFE4-CAF0-44EE-95CC-(E-Mail Removed)...
> Very strange problem here...
>
> Brand new w2k3 std server with latest updates installed with about 10
> clients, AD, DNS, WINS, getting DHCP from Bellsouth router. Joined ws's
> to
> domain, can login and get resources from network; server shared printers,
> shared files. Can manage local groups from AD in Computers tab for about
> 1/2
> of local machines for local admin desktop access, but cannot connect to
> other
> machines period when double clicking on station name. Can ping IP and
> Netbios station name and they both resolve to correct IP and name, &
> vice/versa.
>
> Tried taking off of domain from ws client, WinXP Pro, SP2 latest updates,
> rebooting client, deleting station name in computers in AD, rejoining
> sucessfully to domain using administrator credentials; same problem.
>
> Other info: I initially setup this server at home on my network. When I
> got
> to the site where I was installing it at, had to change internal NIC TCPIP
> properties for gateway & DNS from 192.168.1.1 to 192.168.1.254 to match
> local
> network. Rebooted server and no entried in Event Viewer saying there were
> problems related to those changes.
>
> Then, that is causing me other problems with pushing AV clients down. Any
> suggestions? Your help would be MOST appreciated.
>
> Other questions: for testing purposes, how do I 'flush' out WINS cache?
> More importantly, how do I manually 'force' AD to make any changes I've
> made
> to happen right then instead of waiting a period of time for AD changes to
> take effect?
>
> Thank you ahead for your time - Billy

Computer Management ! error: "Computer 'blah blah blah' cannot be managed.
The network path was not found."

To make a long story short, I had forgotten I had just uninstall Mcafee's
security suite and it inadvertently turned back on the firewall. Its these
small humbling experiences in life that keep us going isn't it?

Thank you very much for your response and offer for help. I hope this helps
others. Have a great day!

"Robert L. (MS-MVP)" wrote:

> cannot connect to other machines period when double clicking on station
> name: what's the error message? It could be the permission issue.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "justfishing" <(E-Mail Removed)> wrote in message
> news:FC1EDFE4-CAF0-44EE-95CC-(E-Mail Removed)...
> > Very strange problem here...
> >
> > Brand new w2k3 std server with latest updates installed with about 10
> > clients, AD, DNS, WINS, getting DHCP from Bellsouth router. Joined ws's
> > to
> > domain, can login and get resources from network; server shared printers,
> > shared files. Can manage local groups from AD in Computers tab for about
> > 1/2
> > of local machines for local admin desktop access, but cannot connect to
> > other
> > machines period when double clicking on station name. Can ping IP and
> > Netbios station name and they both resolve to correct IP and name, &
> > vice/versa.
> >
> > Tried taking off of domain from ws client, WinXP Pro, SP2 latest updates,
> > rebooting client, deleting station name in computers in AD, rejoining
> > sucessfully to domain using administrator credentials; same problem.
> >
> > Other info: I initially setup this server at home on my network. When I
> > got
> > to the site where I was installing it at, had to change internal NIC TCPIP
> > properties for gateway & DNS from 192.168.1.1 to 192.168.1.254 to match
> > local
> > network. Rebooted server and no entried in Event Viewer saying there were
> > problems related to those changes.
> >
> > Then, that is causing me other problems with pushing AV clients down. Any
> > suggestions? Your help would be MOST appreciated.
> >
> > Other questions: for testing purposes, how do I 'flush' out WINS cache?
> > More importantly, how do I manually 'force' AD to make any changes I've
> > made
> > to happen right then instead of waiting a period of time for AD changes to
> > take effect?
> >
> > Thank you ahead for your time - Billy
>
>

Thank you for the update.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"justfishing" <(E-Mail Removed)> wrote in message
news:F75C9634-4B30-4F14-B78D-(E-Mail Removed)...
> Computer Management ! error: "Computer 'blah blah blah' cannot be managed.
> The network path was not found."
>
> To make a long story short, I had forgotten I had just uninstall Mcafee's
> security suite and it inadvertently turned back on the firewall. Its
> these
> small humbling experiences in life that keep us going isn't it?
>
> Thank you very much for your response and offer for help. I hope this
> helps
> others. Have a great day!
>
> "Robert L. (MS-MVP)" wrote:
>
>> cannot connect to other machines period when double clicking on station
>> name: what's the error message? It could be the permission issue.
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "justfishing" <(E-Mail Removed)> wrote in message
>> news:FC1EDFE4-CAF0-44EE-95CC-(E-Mail Removed)...
>> > Very strange problem here...
>> >
>> > Brand new w2k3 std server with latest updates installed with about 10
>> > clients, AD, DNS, WINS, getting DHCP from Bellsouth router. Joined
>> > ws's
>> > to
>> > domain, can login and get resources from network; server shared
>> > printers,
>> > shared files. Can manage local groups from AD in Computers tab for
>> > about
>> > 1/2
>> > of local machines for local admin desktop access, but cannot connect to
>> > other
>> > machines period when double clicking on station name. Can ping IP and
>> > Netbios station name and they both resolve to correct IP and name, &
>> > vice/versa.
>> >
>> > Tried taking off of domain from ws client, WinXP Pro, SP2 latest
>> > updates,
>> > rebooting client, deleting station name in computers in AD, rejoining
>> > sucessfully to domain using administrator credentials; same problem.
>> >
>> > Other info: I initially setup this server at home on my network. When
>> > I
>> > got
>> > to the site where I was installing it at, had to change internal NIC
>> > TCPIP
>> > properties for gateway & DNS from 192.168.1.1 to 192.168.1.254 to match
>> > local
>> > network. Rebooted server and no entried in Event Viewer saying there
>> > were
>> > problems related to those changes.
>> >
>> > Then, that is causing me other problems with pushing AV clients down.
>> > Any
>> > suggestions? Your help would be MOST appreciated.
>> >
>> > Other questions: for testing purposes, how do I 'flush' out WINS cache?
>> > More importantly, how do I manually 'force' AD to make any changes I've
>> > made
>> > to happen right then instead of waiting a period of time for AD changes
>> > to
>> > take effect?
>> >
>> > Thank you ahead for your time - Billy
>>
>>