My Network Service Finder is sooooo sloooww
-
I created a client-server application where I installed the client on 10 computers in a network (LAN)... now since the IP address of each computer are dynamic.. I created my server in such a way that I will scan the network from something like 192.168.1.1 to 192.168.1.255 just to find those 10 computers. It works, it was able to detect the 10 computers which is running the specific service.. My problem is that the detection is too slow.. starts from 192.168.1.1 (30 seconds) then 192.168.1.2 (another 30 seconds) so like an average of 30 seconds for each IP... is there a way to fasten this up?
-
I created a client-server application where I installed the client on 10 computers in a network (LAN)... now since the IP address of each computer are dynamic.. I created my server in such a way that I will scan the network from something like 192.168.1.1 to 192.168.1.255 just to find those 10 computers. It works, it was able to detect the 10 computers which is running the specific service.. My problem is that the detection is too slow.. starts from 192.168.1.1 (30 seconds) then 192.168.1.2 (another 30 seconds) so like an average of 30 seconds for each IP... is there a way to fasten this up?
I'm not sure if there's a 'proper' way. Have you tried pinging the addresses first to see if they exist? I would be testing several at once using threading too.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
I'm not sure if there's a 'proper' way. Have you tried pinging the addresses first to see if they exist? I would be testing several at once using threading too.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
I created a client-server application where I installed the client on 10 computers in a network (LAN)... now since the IP address of each computer are dynamic.. I created my server in such a way that I will scan the network from something like 192.168.1.1 to 192.168.1.255 just to find those 10 computers. It works, it was able to detect the 10 computers which is running the specific service.. My problem is that the detection is too slow.. starts from 192.168.1.1 (30 seconds) then 192.168.1.2 (another 30 seconds) so like an average of 30 seconds for each IP... is there a way to fasten this up?
In the System.Net.NetworkInformation namespace, there is a Ping object, that can ping either an IP address, or a host-name (the name of the computer). Use the Ping.Send( string ) or Ping.Send( IPAddress ) methods and get a PingReply object with details about the host or address pinged. See
-
I created a client-server application where I installed the client on 10 computers in a network (LAN)... now since the IP address of each computer are dynamic.. I created my server in such a way that I will scan the network from something like 192.168.1.1 to 192.168.1.255 just to find those 10 computers. It works, it was able to detect the 10 computers which is running the specific service.. My problem is that the detection is too slow.. starts from 192.168.1.1 (30 seconds) then 192.168.1.2 (another 30 seconds) so like an average of 30 seconds for each IP... is there a way to fasten this up?
In the System.Net.NetworkInformation namespace, there is a Ping object, that can ping either an IP address, or a host-name (the name of the computer). Use the Ping.Send( string ) or Ping.Send( IPAddress ) methods and get a PingReply object with details about the host or address pinged. See How to ping a hostname/ip using ASP.NET 2.0 and C# .NET[^] for an example of using the Ping and PingReply objects.