Network Tools

[Solaris17]

For 192.168 (which is the smallest of the local networks), it would have to scan 65,536 IP addresses which is a lot. Moreover, if there is a firewall on that computer, you are likely to get no response at all from it.

couldent you ping localhost get that systems ip then scan the range :xxxx ?

 

[FordGT90Concept]

I can get the IP addresses of the running machine easily, but not the IPs of other machines without being told what they are.

I know routers send a "Hello?" message to all connected machines in order to build a database of connections but I doubt individual computers have access to that information.

What I can do is list all active connections. I see my server on that list but I don't see my other desktop.

 

[Solaris17]

hmmm osrry man i guess well need to wait for kreij this is beyond my skill

 

[FordGT90Concept]

"net view" shows all the machine names (Windows only) but I can't find any way to turn those names into IPs.

 

[Kreij]

No, actually you wouldn't need to do it that way. Grab the IP of the requesting machine, strip off the last number (say 10.1.1.x) and then scan from 10.1.1.1 to 10.1.1.254

I occansionally use a little freeware utility called "dnswalker", but it's dirt slow and only does that (unlike yours which has more functionality).

 

[Kreij]

@FordGT

You should not have to use unmanaged code for network stuff.
Try this ...

string _HostName = System.Net.Dns.GetHostEntry(xxx.xxx.xxx.xxx).HostName;

I don't really care if the machine does not return a hostname (you can always just substitute "unknown" for the name), as long as it detects its presence on the network at a particular IP address.

 

[FordGT90Concept]

No, actually you wouldn't need to do it that way. Grab the IP of the requesting machine, strip off the last number (say 10.1.1.x) and then scan from 10.1.1.1 to 10.1.1.254

I occansionally use a little freeware utility called "dnswalker", but it's dirt slow and only does that (unlike yours which has more functionality).

So just ping those 256 addresses and display those that respond?

@FordGT

You should not have to use unmanaged code for network stuff.
Try this ...

string _HostName = System.Net.Dns.GetHostEntry(xxx.xxx.xxx.xxx).HostName;

I don't really care if the machine does not return a hostname (you can always just substitute "unknown" for the name), as long as it detects its presence on the network at a particular IP address .

That's what DNS Resolve does if you give it an IP address. It returns something like...

##-##-##-##.dr01.lmrs.ia.frontiernet.net

... on intrernet or the IP address entered.

 

[Kreij]

Yes, start a loop for the local class C IP addresses in the domain (or just on the local LAN) and if one responds to the ping try to get the hostname.

 

[FordGT90Concept]

None will return a hostname (just loopback the IP address). Not to mention, GetHostByEntry on an IP address if it doesn't have a hostname takes like 5-10 seconds. The timeout they have set in there is way too long.


Having some 258 threads running at once is a lot but it would be the absolute fastest way to get the results. I'll have to decide if I will break it up or limit how many are running at once.

 

[lemonadesoda]

1./Port scanner isnt working fully yet. Where to enter the port data?

2./The console keeps "homing" rather than staying at the bottom of the output script

 

[FordGT90Concept]

1. In the input text box. Separate multiple port numbers by commas. See the picture in the first post for an example. It assumes all ports use the "localhost" IP. Basically, it creates a TCP Listener on all the ports you specify. Once the Listener is good, it stops it and reports back. Theoretically, if the port is blocked, it should throw an exception when attempting to start the listener which is caught and handled.

By the way, the Port Scan is multithreaded so if you put in 80,8080,5050, it may or may not show the results in that order. It displays them in the order it completes them.


2. That's a short fall of the .NET framework. Everytime the app finishes writing data, I force it to scroll to the bottom through a user32.dll call and then focus the cursor back in the input text box. I don't know of a way to do it any better than that, unfortunately, without either changing the GUI completely or making the app an entirely console application which means no stopping a task mid-stream and text-based menus.



Edit:

No, actually you wouldn't need to do it that way. Grab the IP of the requesting machine, strip off the last number (say 10.1.1.x) and then scan from 10.1.1.1 to 10.1.1.254

I occansionally use a little freeware utility called "dnswalker", but it's dirt slow and only does that (unlike yours which has more functionality).

This worked. On my network, it does 192.168.0.1-192.168.0.255 in approximately 30 seconds. Is that faster than dnswalker? It gets the hostname too (which surprised me) for all except my the router. It detected all running devices (router, my computer, my server, laser printer, and inkjet printer).


Edit 2: I think I won't release 1.4 until I know for sure Port Scan works. Also, if there's any other changes I should make in this release, let me hear 'em. At this rate, I'm going to run out of version numbers.


Edit 3: Solaris' comment about "ranges" inspired me to add port ranges to the port scan. For example, in 1.4, the following will work:
80,90,100-110,99-95,70

It produces:

Started the port scan...
  100  Good
   90  Good
  101  Good
   80  Good
  102  Good
  103  Good
  104  Good
  105  Good
  106  Good
  107  Good
  108  Good
  109  Good
  110  Good
   95  Good
   96  Good
   97  Good
   98  Good
   99  Good
   70  Good
Scan Complete (500 milliseconds)

 

[oily_17]

I downloaded your app to try out, as it seems like a very handy tool....but got a small bug

Just tried the Ping -

Can ping router 192.168.1.1, but trying to ping any other machine and I get the windows pop up "Network Tools has stopped working..." and the app closes.
It seems to start, gives "Pinging [machine name][IPv6 address] with 32 bytes" but then crashes..

Some info -
Running on Vista SP2 x32 (PC5)
No difference running as Admin (right click)
I can ping these machines using the command prompt.

Network is set up as follows-

Router>>PC2 & Switch1>>PC1,3,4 & Switch2>>PC5 & Print Server


Any idea's , as this does seem to be a useful tool to have.

 

[[I.R.A]_FBi]

i network tool

 

[FordGT90Concept]

...

Any idea's , as this does seem to be a useful tool to have.

The Ping code might not be IPv6 compatible. Can you give me the detailed message of the exception? Most of the code there is mine so if I know what exactly isn't IPv6 capable, I should be able to fix it.

 

[oily_17]

Give me a sec

EDIT: This is the window that pops up -

And info from it-

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: nettool.exe
Problem Signature 02: 1.3.0.0
Problem Signature 03: 4ac7430d
Problem Signature 04: System
Problem Signature 05: 2.0.0.0
Problem Signature 06: 49cc5ec9
Problem Signature 07: 2c1e
Problem Signature 08: 127
Problem Signature 09: System.Net.Sockets.Socket
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 2057

 

[FordGT90Concept]

When it shows the IPv6, does it have a port number on it? Also, is the IPv4 address appended to the end of it? I suspect the bug has something to do with a TrimPort function which could mistake a IPv6 colon for a IPv4 colon.


I PM'd you a debugging version by the way.

 

[oily_17]

Got your PM.

The IPv6 shows[fe80: :......: 15de%9] no port number or IPv4 address

Will run the debugging version now.

EDIT: OK same window, with same error

EDIT2:Just disabled IPv6 and now I get "Timed Out" but at least it does not crash..maybe need a reboot.

 

[FordGT90Concept]

Well, I fixed a potential bug but I'm not sure it is the bug.

A shame it doesn't give you the detailed description. That makes it much harder to troubleshoot.


Download it again at the same URL. Hopefully it will be fixed.

 

[oily_17]

Ok, I just rebooted (slow old work horse)

Will give it a try now.

EDIT: With IPv6 disabled I get the timed out result both with your app and through the command prompt ping

Will try again with IPv6 enabled to see if it crashes.

EDIT2: As soon as I enable IPv6 the app crashes when attempting to ping another machine

 

[FordGT90Concept]

I'm trying to figure out how to enable IPv6 on my network but I think my DGL-4500 doesn't support it. I don't see anything else that stands out as causing problems with IPv6 just by examining the code.


Edit: If both apps time out, that most likely means either the target is unreachable or the target is not responding to pings.

 

[oily_17]

I just disabled it through the Network Connections >>Properties>>IPv6 (unchecked box)

EDIT:Yea , I think I didn't give them enough time after the reboot before trying them out

 

[FordGT90Concept]

I enabled IPv6 on Windows XP via cmd: netsh interface ipv6 install

Pinging google.com still returned IPv4. Is there a certain host that is IPv6 to make it return IPv6?


Edit: Ha, "localhost" worked. I got the exception now so I should be able to fix it.

 

[oily_17]

Maybe I am looking at this wrong in ipconfig /all I get "Link-local IPv6 address...XXXX::XXXX::"

EDIT: Ahh I see you got it to work/not work..I thought it was just me there

 

[FordGT90Concept]

I'm getting somewhere with it. Instead of crashing, it now times out. I have a theory as to why that is happening so it shouldn't be long before it is fixed, at least in the pinger.

 

[oily_17]

Yeah I get the same result
IPv6 = crash
no IPv6 = time out

EDIT: I may be off to bed soon, if not I will try out anything if you want.

No hurry on this....I probably just give you more headaches...