RPC erros

[itadmin2]

I have still an issue with a couple of desktops not been scanned due to RPC errors (The RPC server is unavailable 0x800706BA). I have installed SP3 on both of them but still the problem will not go away.

all clients get serviced by a DHCP server with the lease period of three (3) days.

a) from the computer which has the issue, I can ping the following
loopback card and it respons
the computer by name
the computer by ip
the gateway
a internet name server e.g. ns.sun.com and all works fine.

from the Domain controller,
running arp -a show the computer mac address but pinging to the computer either with a name or ip address does not respond.

The firewall on the computer (does allow file and printing as well as DCOM on TCP port 135).

[itadmin2]

thanks for your assistance, it looks like i have to scratch install these workstations.

[Hemoco]

I'm sorry, there isn't much more I can do to help, this is clearly a local computer problem.

[itadmin2]

thru the connection tester the outcome is still as follows:
Remote WMI test
-----------------------------------------------
\root\cimv2 Remote WMI access test FAILED
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Remote Registry test using WMI
-----------------------------------------------
\root\default Remote WMI access test FAILED
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

i have removed and joined the computer to the domain, C$ admin share is visible from the computer but not visible from remote locations.

[itadmin2]

i have stopped the firewall service, but stills the problem exists.

[Hemoco]

Could you try shutting the firewall service down just to be sure.

[itadmin2]

telnet to 127.0.0.1 135 works from the client.
so does trying to ping to all server within LAN and internet.
it seems to be a problem with other computers communicating to these clients from within the LAN.

[Hemoco]

If you can't telnet to the port, it's firewalled or there is no service running.

Could you try the telnet on the host itself? (telnet 127.0.0.1 135)

This might be the cause of your problem:

A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

[itadmin2]

i have tried this from the machine which has the lansweeper service installed both by name and ip address and neither is successful.
The results are as follows:

C:\>telnet pce0057 135
Connecting To pce0057...Could not open connection to the host, on port 135: Connect failed

C:\>telnet 192.168.1.51 135
Connecting To 192.168.1.51...Could not open connection to the host, on port 135: Connect failed

In the server's eventvwr the following are visible....
DCOM was unable to communicate with the computer 192.168.1.51 using any of the configured protocols and
DCOM was unable to communicate with the computer PCE0057 using any of the configured protocols.
....
DCOM was unable to communicate with the computer PCE0057.domainname.local using any of the configured protocols.

A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

[Hemoco]

Could you try "telnet computername 135" to the client.
This should check if something is blocking the dcom port.

If it works you should get a blank command screen.