- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Folks,
Can anyone please help me with this below question:-
If Customer want to discover windows device(wmi) on some other port instead of 135TCP.
For ex: - Customer want to discover on Port 137 then what changes we have to make in IP service table and Port Probe.
Based on my Knowledge, I will follow below approach
Create a new IP service for port 137 and add it to the 'Triggered by services' field in the WMI port probe.
Is this correct approach, can someone guide me.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@SatishChitti Yes, Satish. Your approach is correct. All you need to do is, create a IP Service for port 137 and add it in 'Triggered by Services' filed on the WMI port probe. To make sure this port number is triggered, run a quick discovery against a windows device and check the ECC Queue for the Topic -> Shazzam and Queue -> Output. Open the XML provided there and search for 137 and it should appear as shown below.
After you find out that it was triggered, you can check in Topic-> Shazzam and Queue -> Input, look for XML, to check what exactly is returned (Was 137 successful in responded from the device). Below screen shows, 135 returned correctly but not 137 (your case, 135 might not be there and 137 returns the correct one).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@SatishChitti Yes, Satish. Your approach is correct. All you need to do is, create a IP Service for port 137 and add it in 'Triggered by Services' filed on the WMI port probe. To make sure this port number is triggered, run a quick discovery against a windows device and check the ECC Queue for the Topic -> Shazzam and Queue -> Output. Open the XML provided there and search for 137 and it should appear as shown below.
After you find out that it was triggered, you can check in Topic-> Shazzam and Queue -> Input, look for XML, to check what exactly is returned (Was 137 successful in responded from the device). Below screen shows, 135 returned correctly but not 137 (your case, 135 might not be there and 137 returns the correct one).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago