I just installed a win7 client to a sbs2002r2 server, All went well till I tried to push install Symantec from the server to the client.Which would fail every time. So I transfered the install package to the client over the network and did finall install the antivirus that way.
In tryinng to find out why the connection failed I did the following.:
Ping the server by name and by IP works from client to the server, and server is fully accessable in that direction from the client.
Ping the client from the server at 'IP 192.168.1.35' (The IP assigned to the client in DHCP and listed in DNS HostA as athe client by name and IP works
Ping the client from the server at 'client name' only shows the ping directed to IP '192.168.1.15' Which is the wrong IP address.
That address was assigned to another client in the system therefor the failure I guess.
I ran DNS server and found many duplicate records So I cleaned up the records by using aging/scavaging settings ,waited for a time and all the DNS records are now listed ok without duplicates. All clients except "35" are working properly. The client for IP '35' did not have a record in reverse lookup so I added it. I also note that the client'35' has a red x on the tool bar network connection icon, but this client '35' is working fine and has full access to the server and internet without problems.
I still can not ping the client from the server by name as it continues to resolve to the "15" IP address even though I deleted that record from DNS and DHCP and all clients are listed properly on the server. When I try to connect using SBS2003r2 server management console with connect to computer 'by name" using terminal services it fails with the error "The client could not connect to the remote computer.Remote connection may not be enabled or computer too busy try again." All other client will connect with this method.
When I try to connect to the client using the servers RDP connection ,by client "name" it fails with the same message unless I use only the proper IP 192.168.1.35 assigned to the client then it connects and I can control the client remotely. The staff using the system need to be able to use RWW on this server to remote into the clients and this will not work on this client only, all the rest do.
I think I already ran ipconfig flush/renew but do I need to do it again since I did the repairs on the DNS duplicates?
I suspected maybe a blockage by the windows firewall on the client but that is controlled by Symantec SBS endpoint protection .
I did make exceptions in the windows firewall for port 4125 but that did not help.
I am not sure what to try next??
I appreciate any help you can give.
