This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Community FAQ
Register | Log In
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- Archive
- Cannot connect to DCOM port 135 error
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Register to ask a question, start a topic or share an idea
Join the Community
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-22-2010 03:13 PM
Resolved. It was actually firewall issue. Our network guy had to open the port on the router.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2010 05:15 PM
Actaully, I didn't modify the GPO since it would impact hundreds PCs. I do have remote admin enabled on the problem machines. Actually, I manually enabled it by using the script you recommended in the post. http://www.lansweeper.com/forum/yaf_postst2967_Scan-over-VPN.aspx.
But most of our PCs have remote admin disabled and the active scan is working fine with them.
But most of our PCs have remote admin disabled and the active scan is working fine with them.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2010 04:10 PM
Enabled Remote admin mode but got the same error. I checked other PCs with success in active scan and they actually have the Remote Admin mode disabled. So, "Cannot connect to DCOM port 135 : Firewalled" might be caused by something else ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2010 10:10 PM
kungfupanda wrote:
Enabled Remote admin mode but got the same error. I checked other PCs with success in active scan and they actually have the Remote Admin mode disabled. So, "Cannot connect to DCOM port 135 : Firewalled" might be caused by something else ?
It might take some time for the GPO to be active.
Do you have remote admin enabled on the problem machines?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2010 09:38 AM
The remote admin mode in the netsh firewall show state should be enabled.
Firewall status:
-------------------------------------------------------------------
Profile = Standard
Operational mode = Enable
Exception mode = Enable
Multicast/broadcast response mode = Enable
Notification mode = Enable
Group policy version = Windows Firewall
Remote admin mode = Enable
Ports currently open on all network interfaces:
Port Protocol Version Program
-------------------------------------------------------------------
82 UDP Any (null)
82 TCP Any (null)
81 UDP Any (null)
81 TCP Any (null)
9524 UDP Any (null)
9524 TCP Any (null)
135 TCP Any (null)
5910 TCP Any (null)
Firewall status:
-------------------------------------------------------------------
Profile = Standard
Operational mode = Enable
Exception mode = Enable
Multicast/broadcast response mode = Enable
Notification mode = Enable
Group policy version = Windows Firewall
Remote admin mode = Enable
Ports currently open on all network interfaces:
Port Protocol Version Program
-------------------------------------------------------------------
82 UDP Any (null)
82 TCP Any (null)
81 UDP Any (null)
81 TCP Any (null)
9524 UDP Any (null)
9524 TCP Any (null)
135 TCP Any (null)
5910 TCP Any (null)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 10:15 PM
screen shot has been attached to my previous post
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 09:32 PM
Click on "attach" on the right side of your post.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 09:31 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 08:52 PM
Could you post the output of "netsh firewall show state" and a list of installed software please.
Archive
This board contains archived posts from the retired Lansweeper Forum and Insiders Community.
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now
Related Content
- Error Lansweeper in Deployment Packages
- Failed sync between Lansweeper on-premise installation and Network Discovery Hub in Product Discussions
- Intune Scanning - No V2 in List & Issues in General Discussions
- Can Lansweeper scan Dell Docking station's serial number which connect to laptop? in Open Office Hours Q&A
- Switch network interfaces not updating connected asset in General Discussions
