MENU
During the Port Scan phase what could the Warning level error "No results returned from probe." mean?
Suggested Answer: B
Get Premium CIS-Discovery Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
During the Port Scan phase in ServiceNow Discovery, the warning level error 'No results returned from probe' typically indicates a connectivity issue. This error often arises when a logical or physical firewall is blocking the connectivity between the MID Server and the target device. This prevents the probe from successfully scanning the ports and returning results. The other options, such as incorrect process classifier configuration, wrong credentials, or incorrect datasource precedence, would generally lead to different types of errors or issues in the discovery process. Reference = ServiceNow Discovery documentation, particularly the sections that deal with troubleshooting Port Scan issues and understanding common errors during Discovery phases.
34 comments · newest first
NA
Nan
11 months ago
Nah, I doubt it's the datasource precedence causing this.
CH
Charlette
11 months ago
Surprised that firewall settings can lead to no results!
LI
Lili
11 months ago
Definitely wrong credentials could cause that too.
AS
Ashlee
12 months ago
I think it's more about the process classifier being off.
KA
Karl
12 months ago
Could be a firewall issue blocking the probe.
PO
Portia
1 year ago
I'm torn between A and D; I recall something about datasource precedence affecting results, but I can't remember the specifics.
KA
Katie
1 year ago
I feel like I've seen a question similar to this before, and I think it was about firewall settings too, so B could be the right choice.
KI
King
1 year ago
I think "No results returned from probe" might relate to configuration issues, like option A, but I need to double-check my notes.
MA
Marshall
1 year ago
I remember studying that a firewall could block probes, so option B seems likely, but I'm not entirely sure.
KA
Kattie
1 year ago
This is a tricky one. I'm going to have to draw on my knowledge of port scanning and network troubleshooting to figure this out. I'll carefully consider each option and try to identify the most likely cause of the warning.
GA
Gail
1 year ago
Okay, I've got a strategy here. I'll eliminate the options that don't seem directly related to the port scan warning, like the wrong credentials. Then I'll focus on the more technical possibilities like the firewall or data source precedence.
JE
Jesus
1 year ago
Hmm, I'm not totally sure about this one. The options seem a bit technical, but I'll try to reason through it. Maybe it's a configuration issue or a firewall blocking the connection?
WH
Whitley
1 year ago
This seems like a straightforward question about port scanning. I'll carefully read through the options and think about what could cause a "No results returned from probe" warning.
LO
Louann
2 years ago
I think it might be a combination of both wrong credentials and incorrect Datasource Precedence.
BE
Bettye
2 years ago
I'm just going to close my eyes and point. This whole thing is a mystery to me anyway. Maybe I'll get lucky and hit the right answer.
SA
Salley
2 years ago
I believe it could also be due to incorrect Datasource Precedence.
RO
Rodolfo
2 years ago
I'm feeling pretty confident about C - wrong credentials. I mean, who hasn't forgotten their password at least once, am I right folks?
VA
Val
2 years ago
User 3: Maybe it's a combination of both B and C, firewall issues and wrong credentials could both be causing the error.
AL
Altha
2 years ago
User 2: I agree, it's important to check all possibilities before jumping to a conclusion.
KA
Katina
2 years ago
User 1: I think it could also be B - firewall issues can definitely cause that error.
NA
Nana
2 years ago
D has to be the answer. Incorrect Datasource Precedence is always the culprit, no matter what the problem is. Trust me, I'm an expert (in my own mind).
BR
Brendan
2 years ago
Incorrect Datasource Precedence is a common issue during Port Scan phase.
BE
Beckie
2 years ago
D) Incorrect Datasource Precedence
BE
Bettye
2 years ago
C) Wrong credentials
WE
Weldon
2 years ago
B) Logical or physical firewall preventing connectivity
FR
Freeman
2 years ago
A) Process Classifier incorrectly configured
MA
Marla
2 years ago
I agree with Merilyn, it's likely wrong credentials.
GE
Gerald
2 years ago
I'm going with A - the Process Classifier is probably not configured correctly. Who even sets these things up anyway?
ME
Merilyn
2 years ago
I think it could mean wrong credentials.
RO
Rosio
2 years ago
Hmm, I think it's B - a logical or physical firewall is preventing connectivity. Gotta love those pesky firewalls, am I right?
NA
Nathalie
2 years ago
Definitely, they can cause a lot of issues during scans.
ME
Melodie
2 years ago
Yeah, firewalls can be a pain sometimes.
AM
Ammie
2 years ago
I agree, but I lean towards B) Logical or physical firewall preventing connectivity.
FR
Francine
2 years ago
I think it could be A) Process Classifier incorrectly configured.