![]() |
Ping Wizard |
![]() |
There are two solutions:
1. First Solution
To workaround this problem in Windows NT 4.0, you can disable the security check on RAW sockets by creating
the following registry variable and setting its value to DWORD 1:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Afd\Parameters\DisableRawSecurity
After you change the registry, you need to restart your computer.
NOTE: BE VERY CAREFUL WHEN MAKING ANY CHANGES TO THE REGISTRY. BACKUP YOUR REGISTRY BEFORE MAKING ANY CHANGES.
Use the PingWithoutRaw method call. This function uses the icmp.dll to accomplish the Ping.
A lot of times you really don't need to resolve the IP's to Hostnames. So it is most often that you will keep
this property set to false.
The reason for the length of time is due to a DNS lookup for the IP address in question. This lookup checks your
LMHOST File, then your DNS server for the name resolution information to see if it can find its registered name.
To speed it up on your end, if you are so inclined , is to implement the following choices:
1) Turn off the option, especially if you don't use it for any practical purpose. This is the most likely choice,
especially if your app is unmanned or your hardware devices are setup for it.
2) You can map your IPs in your LMHOST file. This takes mapping each IP and giving it a name. Can be done, but
impractical.
3) Add the entries into your DNS server. Also impractical but possible.
Our recommendation to all customers is to leave the setting off unless you have a good reason to use it. If you
have a good reason to use it, then you must deal with the wait.
A lot of hardware devices on a local network wont have a name anyway. A lot of times you already have a friendly
name if they are on the LAN, and you can do your own correlating.
i.e. UnlockPingWizard("MYSERIALNUMBER")