Release v2.30 makes major changes to the way Ping Sweep operates. It now allows you to specify an IP range or ranges to ping on a per switch basis. This means you can set the range of IPs to match those handled by the switch. You can also now specify the timeout and retries for the ping packets. Responding IPs are queried for their MAC address and the results are placed in our Combined ARP table for use during the mapping process.
There is also a terminology change: previous versions all referred to Switch Configurations which are the combination of a switch and the two optional devices to query for ARP information. Now that term has been changed to Switch Group in order to reduce confusion with Cisco switch configs.
There are several other changes and the SQLite DLL was updated to the latest version 3.8.3.1.
Showing posts with label Ping. Show all posts
Showing posts with label Ping. Show all posts
Tuesday, March 4, 2014
Monday, November 4, 2013
Important NetScanTools Pro v11.53 Release
NetScanTools Pro v11.53 (installed) was released on November 1, 2013. This is a very important release because of the type of fixes that are in it. These fixes affect any of the tools that use WinPcap for capturing or sending packets. The WinPcap fixes are important if you use NetScanTools Pro on a machine where the network interface does not support promiscuous mode (normally WiFi 802.11) or you have more than one network interface on the machine.
If your network interface does not support promiscuous mode, all versions prior to 11.53 will not be able to open the interface resulting in a message similar to this one: "Error: Cannot open interface for packet sending. Please exit and restart NetScanTools Pro".
This means you cannot fully utilize tools that depend on WinPcap - for example the WinPcap ICMP mode of Traceroute will not work. The change in 11.53 allows the interface to be automatically opened in non-promiscuous mode if the open in promiscuous mode fails. If an adapter can be opened in promiscuous mode, all packets passing by it are passed along to the host system, however, if it is opened in 'normal' mode, then only packets intended for the system are passed to the host system. This mostly affects WiFi adapters so now you may find that NetScanTools Pro works much better with your WiFi network interface. Error message reporting has been significantly improved at the same time.
If you have more than one network interface on the system running NetScanTools Pro, all versions prior to 11.53 will only be able to send packets to the local network associated with the secondary interface. In other words if a packet sent out the secondary interface is intended for a destination beyond the default gateway, it will not get there because the default gateway mac address was not being obtained correctly. It now is obtained correctly so packets will go out the secondary interface default gateway as intended.
The WinPcap related changes affected ARP Ping, ARP Scan, Duplicate IP Address Scanner, OS Fingerprinting, Packet Capture Playback, Packet Generator, Ping, Port Scanner, Promiscuous Mode Scanner, Traceroute, Connection Monitor, Packet Capture, Passive Discovery, SNMP Dictionary Attack and SNMP Scanner.
Other changes include:
Version 11.53 is available to all those will active maintenance plans. Click on Help/Check for New Version to obtain it.
If your network interface does not support promiscuous mode, all versions prior to 11.53 will not be able to open the interface resulting in a message similar to this one: "Error: Cannot open interface for packet sending. Please exit and restart NetScanTools Pro".
This means you cannot fully utilize tools that depend on WinPcap - for example the WinPcap ICMP mode of Traceroute will not work. The change in 11.53 allows the interface to be automatically opened in non-promiscuous mode if the open in promiscuous mode fails. If an adapter can be opened in promiscuous mode, all packets passing by it are passed along to the host system, however, if it is opened in 'normal' mode, then only packets intended for the system are passed to the host system. This mostly affects WiFi adapters so now you may find that NetScanTools Pro works much better with your WiFi network interface. Error message reporting has been significantly improved at the same time.
If you have more than one network interface on the system running NetScanTools Pro, all versions prior to 11.53 will only be able to send packets to the local network associated with the secondary interface. In other words if a packet sent out the secondary interface is intended for a destination beyond the default gateway, it will not get there because the default gateway mac address was not being obtained correctly. It now is obtained correctly so packets will go out the secondary interface default gateway as intended.
The WinPcap related changes affected ARP Ping, ARP Scan, Duplicate IP Address Scanner, OS Fingerprinting, Packet Capture Playback, Packet Generator, Ping, Port Scanner, Promiscuous Mode Scanner, Traceroute, Connection Monitor, Packet Capture, Passive Discovery, SNMP Dictionary Attack and SNMP Scanner.
Other changes include:
- The improvement of administrator privileges detection which affects TimeSync - doing a clock synchronization and DNS Tools Core Edit Hosts File. Some portions of Network Connection Endpoints are also affected.
- Addition of a column showing the DHCP Server MAC Address to the DHCP Server Discovery Tool.
- Packet Capture Playback now supports sending .pcap files in addition to .cap files.
- Ping Enhance/TCP Ping now correctly send the number of packets you designate.
- SQLite was updated to 3.8.1 and the database files were updated.
Version 11.53 is available to all those will active maintenance plans. Click on Help/Check for New Version to obtain it.
Wednesday, October 2, 2013
NetScanTools Pro v11.52 Released Sept 24, 2013
NetScanTools Pro 11.52 was released last week and it has several improvements and updates the databases.
Packet Generator will now work better on Windows 8.x in that the operating system will no longer think it is 'not responding' while sending streams of packets. Earlier versions of Windows do not get confused like this, but apparently Windows 8 expects the message queue to be pumped more often. If the message queue is not cleared quickly enough Windows 8 grays out the software and calls it 'non-responding' which clearly was not the case with the Packet Generator.
Several things were done in Ping and Traceroute to give the user better feedback when the Windows Firewall settings are not allowing outgoing packets to be captured by WinPcap. Without knowing when the outgoing packets are sent, it's difficult to establish round-trip-time. A message will now appear explaining the problem and telling you to change the firewall settings or temporarily turn it off. The timing calculation shown in the analysis area below the results grid now shows sub-decimal timing calculations, ie. 123.456 ms instead of just 123 ms.
The Wireless Network Interface tool now has more concise explanations of what was found to better conform to industry standard terminology.
The USB version has a change that only affects the USB version: if the host has WinPcap 4.1.2 or 4.1.3 installed on it, the software uses the host's WinPcap instead of the WinPcap Pro that is on the USB. More about this in another blog post soon.
If you have an active maintenance plan, please start NetScanTools Pro, then click on Help/Check for New Version to access either the new v11.52 full install or USB upgrade patch.
Packet Generator will now work better on Windows 8.x in that the operating system will no longer think it is 'not responding' while sending streams of packets. Earlier versions of Windows do not get confused like this, but apparently Windows 8 expects the message queue to be pumped more often. If the message queue is not cleared quickly enough Windows 8 grays out the software and calls it 'non-responding' which clearly was not the case with the Packet Generator.
Several things were done in Ping and Traceroute to give the user better feedback when the Windows Firewall settings are not allowing outgoing packets to be captured by WinPcap. Without knowing when the outgoing packets are sent, it's difficult to establish round-trip-time. A message will now appear explaining the problem and telling you to change the firewall settings or temporarily turn it off. The timing calculation shown in the analysis area below the results grid now shows sub-decimal timing calculations, ie. 123.456 ms instead of just 123 ms.
The Wireless Network Interface tool now has more concise explanations of what was found to better conform to industry standard terminology.
The USB version has a change that only affects the USB version: if the host has WinPcap 4.1.2 or 4.1.3 installed on it, the software uses the host's WinPcap instead of the WinPcap Pro that is on the USB. More about this in another blog post soon.
If you have an active maintenance plan, please start NetScanTools Pro, then click on Help/Check for New Version to access either the new v11.52 full install or USB upgrade patch.
Friday, September 2, 2011
IPv6 Link Local Addressing
As I've been working to adding IPv6 capabilities to NetScanTools Pro. As I have worked with link local addressing I have learn some interesting things. In the IPv4 world if you want to ping an address or connect to a computer on your local network, the software can easily find out the best interface (if you have more than one) to send packets out of to the other computer - all you had to do was supply the IP address. It does this using routing tables and ARP.
In IPv6, it's not quite so easy. In Windows or any other OS, you will often have two or more interfaces capable of talking IPv6. Since all link local addresses begin with FE80:, there is no method for saying this one address is on this segment and this one is on that segment like there is in IPv4 (by using IP address and subnet mask).
Essentially you have to tell the software you are using which interface to use to get to the link local address. If you have one interface to your switch and all the other devices are on the same VLAN, then it's pretty easy. You do this by appending a %# where # is the IPv6 interface number in Windows - also called the Scope ID. In unix derived operating systems like Ubuntu or OS X Lion, you would use %eth0 for the main interface.
How do you know which interface to use? That's where you have to know your network. In my case, this particular XP machine assigns '6' as the Scope ID - you can see this using ipconfig /all. It could be any number, but it's usually a single digit. So to ping an IPv6 address you would enter smoething lik "ping -6 FE80::3CC0:1%6" on the command line (no quotes). Or if you were using NetScanTools Pro v11 Ping Enhanced you would enter FE80::3CC0:1%6 as the target. If you leave off the %6 or change it to another number the software will not know which interface to send the packets out of. In NetScanTools Pro, you will see an error message. The command line ping will tell you the net is unreachable if you use the wrong Scope ID.
Just a few things I've learned about IPv6 link local addressing.
In IPv6, it's not quite so easy. In Windows or any other OS, you will often have two or more interfaces capable of talking IPv6. Since all link local addresses begin with FE80:, there is no method for saying this one address is on this segment and this one is on that segment like there is in IPv4 (by using IP address and subnet mask).
Essentially you have to tell the software you are using which interface to use to get to the link local address. If you have one interface to your switch and all the other devices are on the same VLAN, then it's pretty easy. You do this by appending a %# where # is the IPv6 interface number in Windows - also called the Scope ID. In unix derived operating systems like Ubuntu or OS X Lion, you would use %eth0 for the main interface.
How do you know which interface to use? That's where you have to know your network. In my case, this particular XP machine assigns '6' as the Scope ID - you can see this using ipconfig /all. It could be any number, but it's usually a single digit. So to ping an IPv6 address you would enter smoething lik "ping -6 FE80::3CC0:1%6" on the command line (no quotes). Or if you were using NetScanTools Pro v11 Ping Enhanced you would enter FE80::3CC0:1%6 as the target. If you leave off the %6 or change it to another number the software will not know which interface to send the packets out of. In NetScanTools Pro, you will see an error message. The command line ping will tell you the net is unreachable if you use the wrong Scope ID.
Just a few things I've learned about IPv6 link local addressing.
Monday, July 11, 2011
NetScanTools (r) Basic Edition 2.1 Released July 8, 2011
On Friday we released NetScanTools Basic 2.1 - our first update to this software since January 2010. This is our freeware version of NetScanTools. It has just a few helpful tools that introduce people to the NetScanTools Product line.
Tools:
DNS Tools - simple query (ipv4 to hostname etc.), Who Am I (shows your IPv4 address, hostname and DNS servers), Test Default DNS (takes IP address or hostname and asks each default DNS server for translation).
Ping - uses standard ICMP ping to contact an IPv4 or hostname.
Graphical Ping - uses standard ICMP ping to contact an IPv4 or hostname and it graphs the response times over time.
Traceroute - uses ICMP packets to show the route between your computer and a target computer.
Ping Scanner - uses ICMP packets to ping every IPv4 address between a start and ending IPv4 address.
Whois - shows basic whois information for around 70 domain extensions and IPv4 addresses.
These tools are simplified in comparison to NetScanTools Pro which means you don't have all the options available and you only get one mode of operation - for example traceroute is ICMP only instead of ICMP, UDP, TCP etc.
Have a look and enjoy!
Kirk
Tools:
DNS Tools - simple query (ipv4 to hostname etc.), Who Am I (shows your IPv4 address, hostname and DNS servers), Test Default DNS (takes IP address or hostname and asks each default DNS server for translation).
Ping - uses standard ICMP ping to contact an IPv4 or hostname.
Graphical Ping - uses standard ICMP ping to contact an IPv4 or hostname and it graphs the response times over time.
Traceroute - uses ICMP packets to show the route between your computer and a target computer.
Ping Scanner - uses ICMP packets to ping every IPv4 address between a start and ending IPv4 address.
Whois - shows basic whois information for around 70 domain extensions and IPv4 addresses.
These tools are simplified in comparison to NetScanTools Pro which means you don't have all the options available and you only get one mode of operation - for example traceroute is ICMP only instead of ICMP, UDP, TCP etc.
Have a look and enjoy!
Kirk
Thursday, February 3, 2011
NetScanTools Pro NetScanner/Ping Sweep Tips
These comments apply to NetScanTools Pro 10.98.1 and earlier. NetScanner/Ping Sweep uses ICMP ping packets to find active computers in the IP range or list of IPs.
1. If you are scanning a range of IPs that include Windows computers with active NetBIOS or SMB Windows computer name access - please - -please - please make sure that the checkbox labeled "Delete NetScanner Temporary Files on Exit" is checked. See NetScanner/Ping Sweep Setup.
2. If you see what you know is the wrong hostname for an IP, first press the Edit Hosts File button and see if the IP is in there. If it is, edit it out and make sure the Add Responding IPs to Hosts File box is unchecked. If the hosts file is not the problem, you need to review DNS. NetScanner uses the builtin resolver in Windows to resolve IPs to hostnames using DNS queries, if those fail a node status request is sent directly to the target to try to get the Windows hostname. Switch to the DNS Tools - Core tool and enter the IP that has the wrong hostname. Then press Test Default DNS. This tool does a direct PTR query to all the DNS's used by your computer. Look for two or more PTR records showing different hostnames. If you see it here, then the problem is in DNS. If the IP does not have PTR records in DNS, then go back to NetScanner and double click on the IP in question to view the NetBIOS/SMB information returned during the scan. You may see the incorrect hostname in the NetBIOS response. If so, then make sure #1 above is implemented - if not, exit the program, restart and rescan.
3. Keep Add responding IPs to hosts file unchecked. It is an artifact of an earlier version of NetScanTools and is no longer relevant in today's systems.
4. If you are looking for MAC addresses, please make sure Retry Send ARP is checked and Get NetBIOS Info is checked. The first one uses ARP to get MAC addresses if you are on the same subnet. The second one queries Windows computers throught the NetBIOS/SMB protocol to obtain MAC addresses. Remember MAC addresses in an IPv4 network are not routed.
5. If you want to ping a set of non-contiguous, random IPs, please create a list of IPv4 address, one per line and save it to a text file. There can be no other information in this file, only the IP addresses. On NetScanner/Ping Sweep, press Load Targets, then Load Text File. Navigate to the IP text file and open it. Now press Start NetScan and answer Yes to the question about scanning the list. You may want to go into Setup and uncheck the box labeled Enable Post-Sweep Delete of Nonresponding IPs - it's up to you.
1. If you are scanning a range of IPs that include Windows computers with active NetBIOS or SMB Windows computer name access - please - -please - please make sure that the checkbox labeled "Delete NetScanner Temporary Files on Exit" is checked. See NetScanner/Ping Sweep Setup.
2. If you see what you know is the wrong hostname for an IP, first press the Edit Hosts File button and see if the IP is in there. If it is, edit it out and make sure the Add Responding IPs to Hosts File box is unchecked. If the hosts file is not the problem, you need to review DNS. NetScanner uses the builtin resolver in Windows to resolve IPs to hostnames using DNS queries, if those fail a node status request is sent directly to the target to try to get the Windows hostname. Switch to the DNS Tools - Core tool and enter the IP that has the wrong hostname. Then press Test Default DNS. This tool does a direct PTR query to all the DNS's used by your computer. Look for two or more PTR records showing different hostnames. If you see it here, then the problem is in DNS. If the IP does not have PTR records in DNS, then go back to NetScanner and double click on the IP in question to view the NetBIOS/SMB information returned during the scan. You may see the incorrect hostname in the NetBIOS response. If so, then make sure #1 above is implemented - if not, exit the program, restart and rescan.
3. Keep Add responding IPs to hosts file unchecked. It is an artifact of an earlier version of NetScanTools and is no longer relevant in today's systems.
4. If you are looking for MAC addresses, please make sure Retry Send ARP is checked and Get NetBIOS Info is checked. The first one uses ARP to get MAC addresses if you are on the same subnet. The second one queries Windows computers throught the NetBIOS/SMB protocol to obtain MAC addresses. Remember MAC addresses in an IPv4 network are not routed.
5. If you want to ping a set of non-contiguous, random IPs, please create a list of IPv4 address, one per line and save it to a text file. There can be no other information in this file, only the IP addresses. On NetScanner/Ping Sweep, press Load Targets, then Load Text File. Navigate to the IP text file and open it. Now press Start NetScan and answer Yes to the question about scanning the list. You may want to go into Setup and uncheck the box labeled Enable Post-Sweep Delete of Nonresponding IPs - it's up to you.
Friday, October 29, 2010
IPv6 Tools in NetScanTools Pro v11
NetScanTools Pro v11 will have the first real IPv6 tools that we have done ever in it. The ability to retrieve DNS AAAA records has always been there, but we've gone beyond that. Here are a sample of the completed tools.
DNS Tools - Basic now includes a Simple Query - IPv6 tool. This tool accepts a hostname like ipv6.google.com or a IPv6 Address like 2001:6b0:1:ea:202:a3ff:fecd:23a7 and attempts to retrieve the IPv6 address or hostname respectively.
DNS Tools - Advanced now includes an IP/Hostname to ASN tool that accepts either a hostname or an IPv4/IPv6 address and returns the ASN.
Ping - Enhanced now includes an ICMPv6 mode.
More IPv6 to come next week. Think about NetScanTools Pro v11 when you need some GUI IPv6 tools. NetScanTools Pro v11 will be released in November. We're getting closer!
DNS Tools - Basic now includes a Simple Query - IPv6 tool. This tool accepts a hostname like ipv6.google.com or a IPv6 Address like 2001:6b0:1:ea:202:a3ff:fecd:23a7 and attempts to retrieve the IPv6 address or hostname respectively.
DNS Tools - Advanced now includes an IP/Hostname to ASN tool that accepts either a hostname or an IPv4/IPv6 address and returns the ASN.
Ping - Enhanced now includes an ICMPv6 mode.
More IPv6 to come next week. Think about NetScanTools Pro v11 when you need some GUI IPv6 tools. NetScanTools Pro v11 will be released in November. We're getting closer!
Wednesday, October 6, 2010
NetScanTools (TM) Pro 10.98 Published
On Monday, October 4, we released NetScanTools Pro 10.98 installed version. The USB version patch was released on Tuesday, October 5.
Here are the changes:
- Ping will now allow up to 8192 consecutive pings to sent. Problems occurred in the previous version if you exceeded 256 pings as defined in Setup.
- Certain DNS functions that use the secondary resolver (ex. Get Basic DNS Records) will now properly handle the truncated flag in the UDP response that indicates the query should be retried using TCP.
- DNS Tools - Core: Fixed problem where if a very large response to a single record query was obtained, all the records would be displayed. Example would be a large PTR record response for a single IP address.
- Updated SQLite to version 3.7.2.
- Updated database files. Removed whois prefix files.
Thursday, May 20, 2010
ipPulse 1.70 released May 20, 2010
I bet you don't know what ipPulse is. So this release announcement may be a shock too. It's the first release in five (5) years and a fairly big one at that.
First of all, what is ipPulse? it is a program designed to cycle through a list of network connected devices and test them one at a time. It can have one or two tests per machine. The first test called the primary test can be either a Ping to see if it responds or a TCP connect to a port of your choice to see if a service is alive on the target. The second optional test can be either a TCP port test (different port) or an SNMP v1/v2c walk of the active interfaces. Failures can be logged and someone can be notified that a failure occurred. Notification can be audible or by email to a computer to a cell phone. That's it. A pretty simple, but effective program. There are programs out there that cost over 10x as much that do pretty much the same thing with more bells and whistles.
So what did we change from the last version of five years ago? For starters it was compiled by the newer Visual Studio 2008 (next time maybe VS2010). Two things were removed: 1. ping using 'raw sockets'. This was redundant because it had another Ping setting. 2. Support for pagers. I haven't seen anyone with a pager in a long time. Cell phones can be emailed from the program (ie. phoneNumber@vtext.com), so unless anyone has a real heart attack over it, pager support is gone. The next thing was Windows 7 (and Vista) support. Previous versions of Windows 'looked the other way' when we wrote our log files and list of targets in the program installation directory. Windows 7 and Vista don't like that at all. So now those writable files go in the user data directory where they belong. The final change was converting from the ancient Wise installer to the latest version of Inno Setup. So now it should run fine on Windows 7, Vista, XP, 2008, 2003 and 2000. Older Windows are not supported - oh well, time to move on.
If you are interested, you can find it at http://www.nwpsw.com/ippulsemain.html
I forgot to mention that it costs $69 for an unlock code. We used to compile a separate CDROM version, but like 45's, CDROMs are vanishing, so now it's just an unlock code. If you have an older version from CDROM and you want to upgrade, contact us for the unlock code. Give us your name, email and CDKEY or invoice number and we'll give you the unlock code for 1.70.
First of all, what is ipPulse? it is a program designed to cycle through a list of network connected devices and test them one at a time. It can have one or two tests per machine. The first test called the primary test can be either a Ping to see if it responds or a TCP connect to a port of your choice to see if a service is alive on the target. The second optional test can be either a TCP port test (different port) or an SNMP v1/v2c walk of the active interfaces. Failures can be logged and someone can be notified that a failure occurred. Notification can be audible or by email to a computer to a cell phone. That's it. A pretty simple, but effective program. There are programs out there that cost over 10x as much that do pretty much the same thing with more bells and whistles.
So what did we change from the last version of five years ago? For starters it was compiled by the newer Visual Studio 2008 (next time maybe VS2010). Two things were removed: 1. ping using 'raw sockets'. This was redundant because it had another Ping setting. 2. Support for pagers. I haven't seen anyone with a pager in a long time. Cell phones can be emailed from the program (ie. phoneNumber@vtext.com), so unless anyone has a real heart attack over it, pager support is gone. The next thing was Windows 7 (and Vista) support. Previous versions of Windows 'looked the other way' when we wrote our log files and list of targets in the program installation directory. Windows 7 and Vista don't like that at all. So now those writable files go in the user data directory where they belong. The final change was converting from the ancient Wise installer to the latest version of Inno Setup. So now it should run fine on Windows 7, Vista, XP, 2008, 2003 and 2000. Older Windows are not supported - oh well, time to move on.
If you are interested, you can find it at http://www.nwpsw.com/ippulsemain.html
I forgot to mention that it costs $69 for an unlock code. We used to compile a separate CDROM version, but like 45's, CDROMs are vanishing, so now it's just an unlock code. If you have an older version from CDROM and you want to upgrade, contact us for the unlock code. Give us your name, email and CDKEY or invoice number and we'll give you the unlock code for 1.70.
Saturday, January 16, 2010
NetScanTools (tm) Basic Edition 2.0 Released Jan 14, 2010
This update to the Freeware Basic Edition changes the layout of the left control panel to make it less confusing. I also added the registered trademark notice for NetScanTools. The SQLite DLL to the latest version as was the whois database it works with. The biggest change was a switch to Inno Setup away from the old Wise installer. This reduced the size of the final installation .exe nearly 1 MB and it gives full compatibility with Windows 7. Speaking of Windows 7, NetScanTools Basic is fully Windows 7 compatible.
You can get NetScanTools Basic 2.0 here.
Monday, June 29, 2009
NetScanTools (TM) Pro 10.92 Published
This release added a powerful new feature to Ping - Enhanced: TCP Ping. TCP Ping uses either a SYN or ACK packet to 'ping' a target and it looks for a response back. If it gets a response, it shows the timing with submillisecond resolution. In this case the timing you are seeing is TCP Latency because you are seeing a TCP response to a TCP packet. Our TCP Ping gives you control over the TCP header. You can set the Distributed Services Code Point bits and the ECN bits to see what effect they have on packet delivery between two points. You can also set the Sequence, Window and Acknowledgement fields in the TCP header to whatever you want. AutoPing was renamed Continuous Ping and we also added Autosave mode so that all the ping results can be saved to a file. This file has tabbed delimited columns so that you can easily import the results into a spreadsheet. This is one of the most complete Ping tools on the market giving you instant access to all three modes of operation: ICMP, UDP and TCP Ping.
Other changes include the addition of the Distributed Services bits to Packet Generator, additional information added to whois IP address queries, improvements to Traceroute and TTCP. Graphical Ping can now send packets as large as 4095 bytes.
10.92 is available now and is ready for download by current registered users. USB version 10.92 will be available in the next day or two.
Other changes include the addition of the Distributed Services bits to Packet Generator, additional information added to whois IP address queries, improvements to Traceroute and TTCP. Graphical Ping can now send packets as large as 4095 bytes.
10.92 is available now and is ready for download by current registered users. USB version 10.92 will be available in the next day or two.
Friday, May 15, 2009
NetScanTools (tm) Basic Edition Released May 14, 2009
What? another NetScanTools?
Yes. When we stopped producing NetScanTools Standard 5.1 in August 2004, we left a whole lot of registered users without any alternative. Business users who wanted to move up opted for NetScanTools Pro, but many, many home and small business users could not justify or afford the upgrade, so they either kept using on NetScanTools Standard (yes, we still hear from people who have used it for years) or they found something else.
Two weeks ago we decided to make a new program using the latest Visual C++ 2008 compiler along with an updated interface -- that's right two (2) weeks ago. Now there is a new program created from almost scratch and it is completely finished! And it works fine on Windows 7, Vista 32/64, 2008, 2003, XP and even Windows 2000.
This new tool has simplified versions of six tools: Ping, Traceroute, Ping Scan, Graphical Ping, DNS Tools and Whois. They are very usable versions of more advanced tools found in NetScanTools Pro. There are embedded web pages comparing the NetScanTools Basic versions of the tools with the NetScanTools Pro versions. Plus we show you what other tools are available in NetScanTools Pro -- just in case you are interested.
It is now our entry level program.
And it's freeware. Try it. Enjoy it. And don't forget to give us feedback on the About NetScanTools Basic page.
You can find it here:
http://www.netscantools.com/nstbasicmain.html
Yes. When we stopped producing NetScanTools Standard 5.1 in August 2004, we left a whole lot of registered users without any alternative. Business users who wanted to move up opted for NetScanTools Pro, but many, many home and small business users could not justify or afford the upgrade, so they either kept using on NetScanTools Standard (yes, we still hear from people who have used it for years) or they found something else.
Two weeks ago we decided to make a new program using the latest Visual C++ 2008 compiler along with an updated interface -- that's right two (2) weeks ago. Now there is a new program created from almost scratch and it is completely finished! And it works fine on Windows 7, Vista 32/64, 2008, 2003, XP and even Windows 2000.
This new tool has simplified versions of six tools: Ping, Traceroute, Ping Scan, Graphical Ping, DNS Tools and Whois. They are very usable versions of more advanced tools found in NetScanTools Pro. There are embedded web pages comparing the NetScanTools Basic versions of the tools with the NetScanTools Pro versions. Plus we show you what other tools are available in NetScanTools Pro -- just in case you are interested.
It is now our entry level program.
And it's freeware. Try it. Enjoy it. And don't forget to give us feedback on the About NetScanTools Basic page.
You can find it here:
http://www.netscantools.com/nstbasicmain.html
Subscribe to:
Posts (Atom)