network tools
My IP, geo, request tools
My IP info, proxy headers
My IP, GEO info, country, city
My request $_SERVER vars
User-Agent tools
My User Agent information
Custom User Agent lookup
Email Address tools
Verify E-MAIL for exist
Trace E-MAIL sender location
Find E-MAIL box location
DNS and WHOIS tools
Find e-mail/domain MX
Domain lookup NS records
Domain A record Lookup
PTR lookup
Domain DNS Lookup
Domain WHOIS info Lookup
Advanced WHOIS Lookup Tool
Custom IP info, reverse lookup
IP info Lookup
Reverse Lookup
IP/Domain/Url Trace-Ping tools
Online Ping
Check/Search Ports tools
Search PORT description

determine mac address from ip,mac address lookup,find ping a remote mac address

Related articles

determine mac address from ip, mac address lookup, ping a mac address, find remote mac address, mac address network search, ping a mac address

Writing this up in the OP may have saved you a lot of grief.
If you can telnet to something on the same subnet, you can

$ arping
Unicast reply from [00:50:AA:10:00:FD] 1.611ms
it if the OS running on the gear supports it. You could also ping it:
$ ping

or try different IP
root@:~# arping
ARPING from eth0
Unicast reply from [00:D0:88:04:9E:72] 9.605ms
from something you do have access to, then run arp to print out the arp cache

$ arp

Address HWtype HWaddress Flags Mask Iface ether 00:2A:A1:94:AD:41 C eth0 ether 00:50:AA:10:00:FD C eth0 ether 00:50:AA:10:00:FE C eth0

See the mac address is how wire level network addressing happens. The IP address is easier and more logical for humans to route, deal with and organize in a much more orderly fashion than could be done with MAC (considering how ethernet works and the intended use of the MAC).
TCP IP was created to allow routing between broadcast domains, as opposed to enlarging them (a la bridging)
Much like a sort of wire level DNS, ARP stores a IP to MAC mapping in the arp cache in the network gear and stations. Any time you connect to a device over the network, within your broadcast domain, (often your subnet) you add that remote device's MAC to your ARP cache (aka table). Once you've communicated you need only to look up the MAC in your local ARP cache to address non routed packets.

Unfortunately ARP is only maintained and available within the broadcast domain. Outside of that it's been routed and this is done with a TCP/IP (and rarely IPX) address encoded in the packet headers. The network gear at the other end sorts out the ARP and routes the packet appropriately once it reaches the destination broadcast domain. The client doesn't need to know or care about the destination MAC unless it's communicating directly with it and there are no routers involved.
This is why you can't get the remote ARP unless you communicate with a program (such as an snmpd) running on the PC(or device) that will give it to you, or with a device on the same subnet where you can get a shell.
An interesting misconception about MACs is that you can use them for security to ID a NIC. Unfortunately a lot of gear can change the MAC on the fly, so that's kind of useless as a security identifier. The fact that it's "hard" set and burned into the NIC is a little misleading.