
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 04:19 PM
We get "Cannot connect to DCOM port 135 : Firewalled?" errorfrom multiple machines. We checked that the firewall were turned off.
Labels:
- Labels:
-
Archive
11 REPLIES 11

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 06:50 PM
Checked there're no third party firewall installed and the DNS record are correct. Able to PING those machines from Lansweeper server.
Run connection test and got the resulst like below
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)
Run connection test and got the resulst like below
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)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 04:44 PM
The problem could be
1) Windows firewall not turned off (check with "netsh firewall show state")
2) a Third party firewall
3) dns problem, check if the ip address shown in the error is the correct IP.
1) Windows firewall not turned off (check with "netsh firewall show state")
2) a Third party firewall
3) dns problem, check if the ip address shown in the error is the correct IP.
