Network Connectivity

As you may or may not know I think pinging "something" to determine whether or not to do "something" is fundamentally flawed logic.

An example would be ping a mail server, if the ping is good then send the mail. At best it is naive in it's assumption. If you want to discuss it or have an example of when it is better, I'll be glad to.

So yesterday I was involved in another debate and this morning I got up and put together some code that addresses this issue.

If you want to try the code out it can be found by clicking the Ban Ping-Then-Do link in my signature.

http://www.vbforums.com/picture.php?...8&pictureid=43

I'm a new VB.net "programmer" and am trying to develop a small program to determine if a computer is "up" on my home network before I try to backup files to the other computer. Can you give me a starting point or any hints as to where to look for code, functions or routines that would help do this.

Using VB 2010 (RC). Network has 4 Windows 7 computers.

Thanks.

Dave

Quote:

---

Originally Posted by Dave48

I'm a new VB.net "programmer" and am trying to develop a small program to determine if a computer is "up" on my home network before I try to backup files to the other computer. Can you give me a starting point or any hints as to where to look for code, functions or routines that would help do this.

Using VB 2010 (RC). Network has 4 Windows 7 computers.

Thanks.

Dave

---

Click on the Ban Ping-then-do in my signature. See post #5 there.

Thanks. I just downloaded the code. I'll see if I can figure it out from there.

Dave

I made changes / additions. See the Update at the bottom of the Ping-then-do link, post#1. One of the things I added was a very simple / basic monitor.

Hmm, any clue what this is doing? I'm not sure why I might need it. Pinging is useless because so many routers blackhole pings these days anyway.

I just start a connection attempt and time it out if I have a concern that I won't reach the remote server. A non-blocking connection request is simple enough to do.

Quote:

---

Originally Posted by dilettante

Hmm, any clue what this is doing? I'm not sure why I might need it. Pinging is useless because so many routers blackhole pings these days anyway.

I just start a connection attempt and time it out if I have a concern that I won't reach the remote server. A non-blocking connection request is simple enough to do.

---

The code is for that group of people that believe that they need to ping something to make sure it is alive, before they do what it was they wanted to do.

Your approach is the correct one. Do what ever it is you are doing, and if there is a problem, catch the problem.

The code is also good for simple monitoring of devices on your network.