Detecting an active/inactive IP address

[William Fletcher]

Can anyone suggest a *quick* way to detect an active/inactive IP address from within a PBDLL pgm without shelling to "ping" (etc) ?

I'm actually seeking a way to efficiently detect an inactive Novell server (which has IP) and if anyone has further suggestions / approaches I would greatly appreciate them too!

Many TIA

William Fletcher

[Semen Matusovski]

William -- http://www.mvps.org/vbnet/
How to Ping an IP Address By Host Name

I tested (in VB). Works.
I tried to convert general line to PB code. (see Source code's forum)


[This message has been edited by Semen Matusovski (edited April 05, 2000).]

[William Fletcher]

Bless you Semen! A great tip plus you saved me lots of 'conversion' time!

William Fletcher

------------------

[William Fletcher]

One catch - I'm using this under a Login Script which runs *before* the user is logged into NT and the PingTime routine is coming back with "Problems". Run from the desktop after login it runs fine.

Any idea(s)?

------------------

[Semen Matusovski]

William --
I am very doubt that you can do something until network becomes reachable.

But Echo.Status returns different error codes (see vbnet).
So (I don't know your task) you can repeat attempts until networks becomes available.
If it will be necessary, you can do "Log Off" by program way
(like I remember, there is very simple MSDN sample).



------------------

[Scott Turchin]

If the network is available, I posted some ICMP code in the source code forum, that version is still sorta rough, but works fine, in fact the app I wrote sat and timed out every five minutes it would send a ping and WAIT for a PC to come on the network and then send a message when it arrived (Anti-hacker measures and it DID catch them )


Anyway, if the network is there, icmp echo may be your easiest way..

Scott

------------------
Scott
mailto:[email protected][email protected]</A>

[William Fletcher]

Thanks Scott - I'll be looking into it.

I looked into the error codes, Semen, and I'm timing out on my pings *before* login is complete (inside the Login Script). The same routine runs fine *after* login is complete (the pings return OK).

------------------


[This message has been edited by William Fletcher (edited April 06, 2000).]

[Scott Turchin]

Let me toss a suggestion in, depending on the NIC and the stack itself, under Windows, or W2k or Windows NT a lot of customers (at my job) place startup scripts to start host sessions, either via IPX or TCP/IP or even DLC and we used to get a lot of calls because they failed to connect...

Just because you have windows up, doesn't necessarily mean it's done loading...it "Looks" like it loads faster..

So my suggestion would be put an app in the registry under:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

Give it a name ie:

Winlog
and a commandline

c:\winlog\winlog.exe


That usually loads a few seconds after login etc is complete, I've had VERY good success with that..


Scott

------------------
Scott
mailto:[email protected][email protected]</A>