Redirecting/Inserting a new IP into Casper Remote

[msample]

Has anyone run across an issue with a computer that has been enrolled on one particular IP that gets logged into the JSS, but after the computer has picked up a different dynamic IP from a different location on the same subnet -you can't push packages out to that computer through Casper Remote?
The JSS has lost contact with the computer in question because of it's new dynamic IP allocation.

I've pinged the IP of the computer we're trying to push a package to...scanned the network via Casper Recon to verify the correct IP of the machine we're reaching out to, but Casper Remote only displays the last IP that the system was enrolled under.

After a Recon scan to the machine we're trying to reach, is there a way to enter in the new IP we found into Casper Remote to re-direct our package push to?

When engaging "run" in Casper Remote, the activity status shows ...opening ssh connection to xxx.xx.xxx.xxx"... but fails.

[Simmo]

Nope, Casper Remote works off of information in the JSS
Technically I am sure you could change the information at the database level, but that would not be advised.

Just have the machine in question run a recon, IP address updates on every check-in.
I may suggest having a policy in Self Service for users to run a recon so you can just direct them there and have the IP update if it has not already.

[mdonovan]

This probably isn't helpful but there is the 'Refresh Data' button in the window toolbar in Casper Remote - ensure you click this before scoping any tasks.

[bentoms]

Second what @mdonovan advises.