how to ping a computer using Powershell

I need to ping a computer using Powershell to determine whether a computer exists with a particular computer name.

I tried:

 $ping = new-object

Open in new window

but it gives me an error:
Exception calling "Send" with "1" argument(s): "Value cannot be null.
Parameter name: address"
LVL 35
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dale HarrisProfessional Services EngineerCommented:
Where are you declaring $entry?
why don't you try straight 'ping'  command with computer name.

ping <computer name>
If you are using PowerShell 2.0 you should use Test-Connection instead of System.Net.NetworkInformation.Ping

Follow this link.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

$ping = new-object
  $ret=$ping.send("<computername or ip address>")

may be it will help you
YZlatAuthor Commented:
ven16, if I use ping command, how do I retrieve the results?
YZlatAuthor Commented:
ven16, do you realize that your last comment is identical to the code I posted?
yes,i do just put the computername in brackets, i just add the computer name to your code.
sorry it was again wrong code ....
YZlatAuthor Commented:
I tried Test-Connection and it seems to work, but what I really need is to return an error if the computer name cannot be found.

This is a form based on a list of computers stored in the default path in the textbox. "C:\computers.txt" Or just create a text file on the C:\ drive named computers.txt from active directory. the results will be in green for computers connected and in red for those disconnected.

Yea forgot to tell you to open it with powershell or rename it with a .ps1 extension using quotes      "MyPingScriptForm.ps1"
Try this:
Test-Connection -ComputerName ComputerNameYouWantToPing -Quiet -Count 1

Open in new window

You'll get true or false response.
Just a quick update or step by step if your new to forms and powershell.

1.) If you exported your computers from active directory and saved only the computernames in a text file. You would then click the UPDATE button,

2.) Then highlight one of the computernames in the listbox. Click the GET INFO button and in the background test connection will run on the machine highlighted returning the results in the rich text box.

3.) You can save the results or look in the script I think I hard coded the results to a servers.rtf file on the C:\ drive. But it returns green for good and red for bad in the RTF box. I've been wanting to get this out for people to work with. Let me know how it works for everyone. Just trying to give back to the community.

YZlatAuthor Commented:
That's not really what I need. I am already getting true or false response whether the computer is online. I want to get more detailed response as to why computer is unavailable. What I need is to find out which ones are ghost computers that do not exist. The name might be in AD but the machine does not exist. That's what I am looking for. Can anyone help?
Off the top of my head, sounds like you want to query AD for some properties of the object.  If you have the Quest Active Directory tools installed, use:
get-qadcomputer {name} | Select whenChanged

Open in new window

 That will (essentially) tell you the last time to computer talked with AD.

If you don't have the QAD tools, I suggest you go download them.  :)
YZlatAuthor Commented:
But that does not tell me whether the machine exists
You won't be able to make a single check that a machine "exists" - that information just isn't able to be stored anywhere.  The best that is available to you is checking some attributes and making your own determination.

Since there is a domain policy specifying how often computers must change their password, use that as a basis for a 'maximum number of days since last communication'.  Many people use 90 days as their "stale" value; if it's been longer than 90 days since a computer updated/talked with AD then it is considered a stale object and is either deleted outright or disabled, depending on their internal policies.

You can easily use Powershell + Quest (QAD) tools to automate such a process or just build a report.  This will show you a list of computers that last changed their password more than 90 days ago, along with the exact date of the last password change and when they were joined to AD:
 get-qadcomputer | ? {$_.whenchanged -lt ((get-date).addDays(-90))} | sort whenChanged | select Name,whenChanged,whenCreated

Open in new window

Assuming you're running Powershell 2.0 (if not, why? go get it), you could include your ping test as a layer of validation, although it will drastically slow down the script:
get-qadcomputer | `
  Where-Object {$_.whenChanged -lt ((Get-Date).AddDays(-90))} | `
    ForEach-Object {
    	$computername = $
    	$changed = $_.whenchanged
    	$created = $_.whenCreated
    	if (Test-Connection $computername -Count 2 -ErrorAction SilentlyContinue) {
    		$cs = gwmi Win32_OperatingSystem -computername $computername
    		if ($cs.csname -eq $computername) {
    		  Write-Host $computername "last updated > 90 days but is pingable"
    		} else {
    		  Write-Host $computername "is pingable but actual computername is" $($cs.csname)
    	} else {
    		Write-Host $computername "is a stale object"

Open in new window

If you have a number of computers that do not directly connect to your network - such as remote/VPN users - then you may have trouble weeding through which systems are truly gone and those that are just not connected.

I hope this helps you out.  Let us know if you need/want more information.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.