Solved

how to ping a computer using Powershell

Posted on 2012-03-19
16
985 Views
Last Modified: 2012-03-27
I need to ping a computer using Powershell to determine whether a computer exists with a particular computer name.

I tried:

 $ping = new-object system.net.networkinformation.ping
  $ret=$ping.send($entry)

Open in new window


but it gives me an error:
Exception calling "Send" with "1" argument(s): "Value cannot be null.
Parameter name: address"
0
Comment
Question by:YZlat
  • 5
  • 3
  • 3
  • +4
16 Comments
 
LVL 16

Expert Comment

by:Dale Harris
ID: 37739270
Where are you declaring $entry?
0
 
LVL 2

Expert Comment

by:ven16
ID: 37739272
why don't you try straight 'ping'  command with computer name.

ping <computer name>
0
 
LVL 7

Expert Comment

by:abdulalikhan
ID: 37739292
If you are using PowerShell 2.0 you should use Test-Connection instead of System.Net.NetworkInformation.Ping

Follow this link.

http://www.ilovepowershell.com/powershell-how-to-ping-computers/
0
 
LVL 2

Expert Comment

by:ven16
ID: 37739298
$ping = new-object system.net.networkinformation.ping
  $ret=$ping.send("<computername or ip address>")

may be it will help you
http://www.ilovepowershell.com/powershell-how-to-ping-computers/
0
 
LVL 35

Author Comment

by:YZlat
ID: 37739405
ven16, if I use ping command, how do I retrieve the results?
0
 
LVL 35

Author Comment

by:YZlat
ID: 37739409
ven16, do you realize that your last comment is identical to the code I posted?
0
 
LVL 2

Expert Comment

by:ven16
ID: 37739482
yes,i do just put the computername in brackets, i just add the computer name to your code.
sorry it was again wrong code ....
0
 
LVL 35

Author Comment

by:YZlat
ID: 37739551
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.
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 
LVL 4

Expert Comment

by:R3C0N
ID: 37739871
PING-EE-WORKS.Export.txt

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.

-R3c0n
0
 
LVL 4

Expert Comment

by:R3C0N
ID: 37739878
Yea forgot to tell you to open it with powershell or rename it with a .ps1 extension using quotes      "MyPingScriptForm.ps1"
0
 
LVL 11

Expert Comment

by:X_layer
ID: 37739886
Try this:
Test-Connection -ComputerName ComputerNameYouWantToPing -Quiet -Count 1

Open in new window

You'll get true or false response.
0
 
LVL 4

Expert Comment

by:R3C0N
ID: 37739935
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.

-R3c0n
0
 
LVL 35

Author Comment

by:YZlat
ID: 37742416
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?
0
 
LVL 5

Expert Comment

by:kollenh
ID: 37743429
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.  :)
0
 
LVL 35

Author Comment

by:YZlat
ID: 37758582
But that does not tell me whether the machine exists
0
 
LVL 5

Accepted Solution

by:
kollenh earned 250 total points
ID: 37766703
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 = $_.name
    	$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.
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

Suggested Solutions

Hi all.   The other day I had to change the passwords for a bunch of users on the fly. Because they were so many, I decided to do it in an automated way and I would like to share it with you all.   If you are not doing it directly in a Domain Co…
Create and license users in Office 365 in bulk based on a CSV file. A step-by-step guide with PowerShell script examples.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video explains how to create simple products associated to Magento configurable product and offers fast way of their generation with Store Manager for Magento tool.

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now