- This topic has 11 replies, 3 voices, and was last updated 3 years, 9 months ago by .
-
Posts
-
I have one computer that I can ping from a command prompt and receive a reply, but in BatchPatch the ping reply “timedout”. What am I overlooking?
When BatchPatch does a ping it really is the same kind of ping that gets sent at the cmd prompt. Assuming that you are saying that you can launch the cmd prompt on the same computer that is running BatchPatch to ping the target but in BatchPatch the same target being pinged is timing out there aren’t too many things that could cause that. The only things I can think of are some kind of typo or weird formatting issue when you added the target computer to BP, or maybe a weird DNS caching issue or DNS suffix issue. I would suggest trying the following things in no particular order:
reboot the BP computer
re-add the target computer to BP from scratch
add the target computer by IP instead of name
add the target computer by FQDN instead of short nameSee if any of those gets you anywhere
I am getting the same thing. I am using IP address only to eliminate a DNS issue. I can ping the IP from command prompt and powershell but not from BatchPatch. I can RDP to the destination, check for updates, check for logins, but not pings. The destination computer even has its firewall turned off: Private and Public profiles. It just stays red and says TimedOut.
BatchPatch version 2021.1.29.12.48
It’s really unclear to me how or why this could happen. I can only make the same suggestions that I made above… (you didn’t mention if you tried any/all of them) … with one addition:
*reboot the BP computer
*re-add the target computer to BP from scratch in a new row
*add the target computer by IP instead of name
*add the target computer by FQDN instead of short name or IP
*check to see how many network adapters are on the computer. if there are multiple adapters, disable any adapters that are not currently in usePlease report back and let me know if any of these does the trick. While I don’t have any other suggestions to make at the moment, it will be helpful for us to know if any of these things works.
Also… see what happens if you toggle the setting ‘Tools > Settings > General > Force pinger to always use only IPv4’
The last suggestion worked. I unchecked “Force ping to always use only IPv4 and it started pinging and the alert turned green. Then I went back to settings and checked it. TimedOut again.
When you unchecked it… did it ping the IPv6 address or still IPv4 address?
I have IPv6 disabled on the target PC. We only use IPv4 in our environment. But to answer your above question, no, it does not ping the IPv6 address when I uncheck it.
I figured out what was causing it. The server that have BatchPatch installed had an old DNS entry in its cache. I went to the DNS server and removed the old machine name’s A and PTR records. Then I went back to the server that has BatchPatch running and did an IPCONFIG /FLUSHDNS. As soon as I did that it started pinging correctly. Even with the default check mark of “Force pinger to always use only IPv4 addresses (no IPv6 addresses). Thank you for replying and apologies for the false alarm.
Oh, and it now also pings successfully by both its IP address and NetBIOS name.
Excellent. Glad you got it worked out. Thanks for explaining what the issue was. This is helpful. Essentially the issue is that when “force IPv4” is enabled BP has to do an explicit DNS lookup, otherwise it can end up pinging the IPv6 address (if IPv6 is enabled). However, when entering an IP address directly into BP as a hostname, obviously that should always be able to work regardless of the “force IPv4” setting, and a DNS lookup should not be required, so I think we can make an adjustment to the code that will take care of that. Presumably the problem in your case was specifically tied to the stale PTR record. My guess is that *just* having the stale A record wouldn’t have caused the issue. Regardless, I think we can make an adjustment to the code to at least ensure that an IP that is input directly into BP will never do the lookup.
- You must be logged in to reply to this topic.