NetScanTools Pro 11.84 Released Jan 25, 2018

The big news about release 11.84 is SMB Scanning. Back in May 2017 during Wannacry we had several people check out the Network Shares - SMB tool and ask if it scanned specific devices by IP address. It does not really do that since it uses only NetBIOS, so I set about to make a tool that does these things:

1. connect to NetBIOS Name Service and grab the 'Windows computer name' and MAC address.
2. connect to SMB port and test the SMB service for supported versions. Every supported version is shown.
3. show latency.
4. do this for a list of IPv4 addresses or hostnames. IPv6 will be added in a later version.

Here is an animated GIF showing the new SMB Scanner in action:

You can use the SMB Scanner Tool to see supported SMB versions and check for vulnerabilities based on those supported versions. It identifies SMB 1.0 support in red because we already know it is compromised. More about the SMB Scanner.

IPv6 improvements

Another important addition is the new multicast Ping button that helps you discover IPv6 neighbors in the Network Neighbors tool. What this button does is ping the link local multicast address and this forces neighbor discovery to happen. The results are then updated after 10 seconds showing all responding link local IPv6 neighbors.

How to get NetScanTools Pro 11.84

If you already have an active maintenance plan for NetScanTools Pro, click on Help/Check for New Version to login and download the full installer.

NetScanTools Pro v11.80 released Aug 4, 2016

NetScanTools Pro 11.80 was released on Aug 4, 2016. This version was completely compiled on Windows 10 and is dual code-signed with both SHA256 and SHA1.

We added a new IPv6 Route Tool that displays the routes and many other properties.

There are many changes and the most obvious change is in the way WinPcap compatible interfaces are shown and selected. Tools that use WinPcap now have a much more verbose description of the interface, not just the IPv4 address shown before. Previously, users would occasionally run into problems where the IPv4 address shown in the dropdown list was not able to be opened even though WinPcap says it was compatible with it. The way the interfaces are opened based on the selection was significantly changed internally so there should be less chance of problems.

The Real Time Blacklist Check tool was changed from a text based single threaded (one after the other) output to a grid based output with multithreading. In other words, in v11.80 many RBL servers are queried simultaneously for the presence of the mail server IPv4 address in their databases.

SNMP tools now support SNMPv3 without the enduser having to go obtain libeay32.dll. We have an Encryption Registration Number and the software is ECCN 5D992.c.

The SNMP Scanner and SNMP Dictionary Attack Tools were worked on extensively to fix problems that happened if you sorted a column with scanning (no longer allowed) and also problems with the XML Excel Schema. Side note - if you are using Excel, don't 'import' the XML file, simply 'open' it just like any other Excel file.

Here are the specific changes:
-Compiled on Windows 10.
-New Tool: IPv6 Routing Table.
-Significant change to the way WinPcap compatible interfaces are listed and chosen. Layout of some tools had to change to support longer selection box.Opening and using a WinPcap network interface no longer depends on matching the IPv4 address.
-We now test to verify that the official WinPcap service or the alternative npcap or Win10Pcap services are running.
-Realtime Black List Check tool completely rewritten with new user interface and it is now multithreaded for increased speed.
-SNMP Core and Advanced tools now have simplified SNMPv3 options. SNMP DLL now has libeay32.dll added and SNMP Library Manager was removed. ECCN 5D992.c
-SNMP Scanner, SNMP Dictionary Attack and Protected Storage Viewer have updated grid controls and are now prevented from sorting by clicking on the column header while the tool is working. Exporting with Microsoft Excel schema has been updated - simply 'open' the XML file from Excel (do not import it). SNMP v1+v2c setting is now properly saved.
-ARP based tools now confirm that the target IPv4 addresses are within the same subnet as the chosen WinPcap interface.
-ARP Scan now automatically sorts by the IP address column when complete.
-Whois changed so that if whois server does not respond, it times out and automatically stops.
-Assigned IPv6 Teredo server is shown in IPv6 Compatible Interfaces.
-Corrected privilege problems with writing to certain parts of the registry during registration process.
-Updated SQLite to version 3.13.0
-Updated MAC address/Manufacturer database.
-Updated IP to Country database.
-Code signing now uses both SHA256 and SHA1 for maximum operating system portability.

NetScanTools Pro v11.62 Released August 15, 2014

This release added the new IPv6 Syntax Validation tool (thanks go to Jeff Carrell for all his help!), consolidated the currently IPv6 capable tools into one menu bar link and addressed the way the top and left panel menus look on High-DPI displays (3200x1800).

It also added the ability to properly send packets to IPv4 multicast addresses when WinPcap is used to send the packets. Prior software versions did not use the correct destination mac address. And now you can also use new scripting commands to specify the source and destination mac addresses in Packet Generator.

One important fix was a change to the way responding ARP packets are processed in the ARP Scanner and Duplicate IP Scanner tools: it now only processes packets with IP addresses corresponding to the allowed range that you specified. Prior versions would show IPv4 addresses outside the range giving uncertain or hard to interpret results.

If you have an active maintenance plan, please click on Help/Check for New Version to download the full install or USB upgrade patch.

We at NetScanTools support World IPv6 Launch Day and we would like to tell you that we are incrementally adding IPv6 support to our software. NetScanTools Pro 11 currently has a number of tools supporting IPv6. NetScanTools LE will be doing whois lookups of IPv6 in the next release. Here are the IPv6 enabled tools in NetScanTools Pro 11.30:

• Ping (11.0+) and Traceroute (11.3+ only) both support IPv6 address targets both direct and through tunnels.
• DNS Tools accepts IPv6 input for Simple Query, NSLOOKUP, DiG, Get Basic DNS Records and IP to ASN.
• Network Neighbors (11.3+ only) shows the IPv6 equivalent of the ARP table.
• Packet Flooder can target IPv6 addresses with UDP packets.
• Packet Capture can capture IPv6 network traffic.
• Country to IP or ASN shows IPv6 allocations by country.
• Network Interfaces shows the IPv6 link local and global addresses assigned to each interface.
• Whois accepts IPv6 global address input to find the ownership or assignment of those addresses. (11.3+ works best)

If you have NetScanTools Pro 11.30 and an IPv6 capable OS like Windows 7, please try these tools. You can even use ::1 as input - that's the same as 127.0.0.1 or localhost in IPv4. Try a ping or traceroute to ipv6.google.com or a whois of 2620:0:1cfe:face:b00c::3. Be careful with Packet Flooder - use it with a link local address (starts with fe80:) of a nearby computer - don't forget the %scopeID number for link local addresses - see the IPv6 menu item to get the Scope ID.

Let us know if you like this hints and tips post.

Worked on NetScanTools Pro Tech Details page this weekend

Completely reorganized and reformatted the NetScanTools Pro Technical Details page. This page directs you to the individual tool descriptions. Have a look:

http://www.netscantools.com/nstprodetails.html

Don't forget to check out the IPv6 tab on the far right. It shows a list of network tools that can talk or do things with IPv6 addresses. IPv6 is coming, so don't get left behind.

IPv6 Network Neighbors in NetScanTools Pro 11.30

We introduced a new tool for IPv6 called Network Neighbors. This tool provides information similar to what the ARP Cache tool does for IPv4: a mapping of IPv6 addresses to physical addresses. Unlike the ARP Cache tool a physical address can be not only a MAC address, but it can also be an IPv4 address associated with a tunneling interface. You can see that in the image below.

Interesting things in this image are the global IPs that start with 2001: - one on those is the local address and the others are target addresses. Note also the large number of permanent multicast entries starting at the top with the ff02::c SSDP, ff02::16 All MLDv2-capable routers, ff02::1:2 All-dhcp-agents and finally the ff02::1:ffxx:xxxx solicited node address (RFC 4291).

You can see the lone fe80:: link local address attached to the only real physical network interface (NIC) in the computer. And you can even see the VMware player interfaces.

What you cannot see in the image is the interface alias, type and ifIndex (Scope ID).

This is new in NetScanTools Pro v11.30.

IPv6 Traceroute in NetScanTools Pro 11.30

NetScanTools Pro Traceroute can now do IPv6 traces. It can do native IPv6 (direct IPv6 connection) and tunneling traces such as through Teredo or 6to4. When you do a native IPv6 traceroute, you will potentially see every hop between you and the target. But with tunneling, it's different: you will see the tunneling server as the first hop even though it may be quite a few hops away. This is shown in the traceroute through a Teredo tunnel to ipv6.google.com shown below.

The hops you are seeing are from the teredo server itself is actually 8 hops from my computer. Since the Teredo server is tunneling IPv6 through UDP, I can trace to the server and find that it is 8 hops away - so in reality, to see all the hops from you to the target, you have to do two traces. But the important thing here is that IPv6 traceroute is now in NetScanTools Pro.

NetScanTools Pro version 11.30 released May 8, 2012

NetScanTools Pro v11.30 was released yesterday, May 8. There is a new tool designed for IPv6 called Network Neighbors. Several existing tools have changes to them: Traceroute now does IPv6 traces even through Teredo. Whois can now do Global IPv6 lookups and many new domain extension servers have been added to the database. Network Interfaces - Wireless now shows the MAC address (BSSID) of available access points even if you are not connected to them. And more - much more.

If you already have NetScanTools Pro v11, click on Help, then on Check for New Version and follow the instructions. If you want a demo, please visit http://www.netscantools.com/nstprodemorequest.html to get a version of the demo based on a slightly older version of 11.

IPv6ScopeFinder

What? It's a new freeware tool designed to quickly help you locate the right Scope ID to use when trying to send packets to a neighboring link local IPv6 address. For instance, you could use it to find the ScopeID when you needed to use command line ping to find out if IPv6 is working on the workstation across the room. I'm talking about the part of the link local address after the percent sign: fe80:11:22:33%6, where '6' is the Scope ID of the network interface on your machine that connects to the network that routes packets to the machine with the IPv6 address fe80:11:22:33.

Read about it and download it here.

IPv6 on Windows XP

Back on June 21 I posted about IPv6 teredo interface not working on Windows 7 and how to correct this using commmand prompt netsh commands.

Just in case anyone is having the same problem on Windows XP, here is the solution for it. The problem is the same, the commands are slightly different.

Command for showing the teredo interface state:
netsh interface ipv6 show teredo

If it says the state is offline with error of none, try this:
netsh interface ipv6 set teredo enterpriseclient

That should do it. The IPv6 network components were incorrectly thinking your computer was in an enterprise situation.

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.

IPv6 Teredo Problems and Solutions on Windows 7-64 bit

I came back from the Wireshark Sharkfest '11 Conference excited to try some of the things I had learned. Imagine my dismay when I fired up my Windows 7-64 test box only to find that certain parts of NetScanTools Pro 11 that are IPv6 aware ceased working. Immediately I was able to see that it was the parts of the program that depended on the getaddrinfo function call that were failing. How did I know that? I used the other 'home-grown' NetScanTools resolver functions to talk with DNS (they bypass Windows resolver entirely and talk directly to any DNS) and by using Wireshark I could see the AAAA records coming back from DNS. I could see that the getaddrinfo function was not getting and reporting the IPv6 AAAA records. Very strange.

So I looked at a couple of things. First I did a cursory check of the network settings with ipconfig. All appeared normal. Then I spent some time recompiling NetScanTools Pro while playing around with various options in the addrinfo hints structure passed into getaddrinfo. That was not fruitful. Nothing I did could make the getaddrinfo function return the AAAA record. I was seeing the 11004 WSANO_DATA error. So I put that aside and looked more carefully at the IPv6 networking subsystem.

Next I tried to see if it was NetScanTools failing or something deeper. So I tried using command line "ping -6 ipv6.google.com". This failed with a message effectively admitting that it couldn't resolve the hostname to an IPv6. Good - sort of. Next I tried the other way doing a "ping -6 2001:4860:b006::69". That came back with even more ominous wording "Ping transmit failed. General Failure.". But I could use both command line ping and NetScanTools Pro IPv6 Ping to contact Link-Local IPv6 addresses on my local network - as I should be able to do. The IPv6 routing table didn't yield any real clues either.

Using both NetScanTools Pro, ipconfig and various netsh command line things I was able to see that while isatap was active, I was not seeing teredo - I had seen it before when using command line ping and when using NetScanTools Pro. Teredo was what I wanted to try decoding with Wireshark. NetScanTools Pro showed me that Teredo was there but it had an admin status of 'Down'. So I tried various netsh commands to reactivate Teredo. They all appeared to work, but Teredo never reappeared in the list of hidden devices in Device Manager. I tried the solutions floating around on the internet for making sure IPv6 was active and getting Teredo to show up in Device Manager, but still no luck.

A little history might help. I had recently installed VMware Workstation 7.1.4 on that machine because it's a test machine and I needed lots of OS's available. Could it be that? I don't know for sure because I spent time on VMware forums looking for similar problems - but didn't see any. It could have been a Windows Update patch that turned off Teredo, but I just don't know for sure. The two VMware Virtual Ethernet Adapters both had link-local fe80 IPv6 addresses, so IPv6 wasn't entirely dead. AND of all things, I could start Windows Server 2008 in a virtual machine with all of it's IPv6 functions working perfectly including NetScanTools Pro. I did find this page dealing with firewall settings for Teredo and found that everything was OK: http://support.microsoft.com/kb/968510

So today I spent lots of time with the netsh commands. I used "netsh interface IP show config" to see all the interfaces similar to ipconfig. By doing a "netsh interface ipv6 show interface" I could see all the active connections. What was missing was Teredo. I used "netsh interface set interface teredo set state default" to make sure it was there and it answered OK. But still no Teredo. Then I found this interesting command "netsh interface IPv6 show teredo". It said the State was 'offline' and the Error value was "client is in a managed network". Progress. Big progress.

So I put that error string into google and found a reference to this blog: http://blogs.msdn.com/b/p2p/archive/2007/03/22/teredo-and-the-pnrp-global-cloud.aspx
Essentially Teredo detected (incorrectly) that the machine was in a corporate environment - this is probably due to multiple OS's and several switches being active with all their chatter. So the fix was to use "Netsh interface teredo set state enterpriseclient". Once I did that, there was no need for rebooting or anything. "netsh interface IPv6 show teredo" now showed the correct info like Local Mapping and External NAT Mapping. And all of a sudden both command line ping and NetScanTools Pro IPv6 enabled tools began to work again.

I guess the thing that bugs me is this: why is there this huge dependency on Teredo for IPv6 in Windows 7? If I ask for a name resolution using getaddrinfo with a hint of AF_INET6 I EXPECT a response if AAAA records are coming back from the default dhcp assigned system DNS. It shouldn't matter that IPv6 is fully enabled on the system using Teredo or anything else. So my workaround will be to write EXTRA CODE to resend an AAAA or PTR record request from my own private resolver on failure of getaddrinfo because I can't trust it. I hope someone at Microsoft reads this and helps me understand why it was behaving this way.

All I wanted to do was try to decode Teredo traffic with Wireshark...

Kirk Thomas
NetScanTools Developer and Sharkfest '11 attendee

NetScanTools Pro 11 finally released!

After a year+ of work, NetScanTools Pro version 11 was released. There are many new and improved things in this release that I'm sure you will be interested in. This is a true major release.

New Interface - completely update and it is still an 'outlook' style interface, there is a left panel control bar and tools appear on the right side. This new interface gives us the ability to bring back 'Favorites' - something that was present in the old 'tabbed' interface of the earlier versions of NetScanTools Pro. You can see a slideshow of it in the screenshot section of the product grid on http://www.netscantools.com/.

The goal of this release was to enhance yet simplify by clearly showing the intended use of each tool. This meant that some tools were split into two parts, for example the ARP tool became the ARP Cache Tool and the ARP Scan Tool. Some tools and things within tools were renamed to conform to industry standard conventions, for example 'Setup' was a more common term when NetScanTools was first released, but now 'Settings' is more common and better understood.

New Tools - Connection Monitor, MAC Address to Manufacturer, Network Interfaces - Wireless, Routing Table - IPV4, and SNMP Scanner Tool.

Additions to current tools:

DNS Tools - Core now has IPv6 Simple Query lookups, Get Basic DNS Records now retrieves the IPv6 AAAA records, we added Flush Default DNS Cache and Edit DNS HOSTS File.

DNS Tools - Advanced has three new tools, IPv4 or Hostname to ASN, Get VOIP SRV Records and Get Misc SRV Records.

Packet Generator now supports sending ARP/RARP packets and RAW packets. RAW packets means that you craft the whole packet from the destination and source ethernet header MAC addresses all the way to the end. And we've added a new tool to help you do that: a Hex Editor.

Ping now supports IPv6 addresses.

Ping Scanner (AKA NetScanner) has the ability to translate IPv4 addresses using either the Default System DNS or a specific DNS. We also added Scan Delay Time to slow it down if necessary and added a way to import an IPv4 list into it. To simplify results, we made the columns dynamic in other words they appear and disappear according to the additional scan tasks settings.

Port Scanner was completely rewritten and works much better than the v10.x predecessor. It's much faster and more accurate. We've added a section for scanning commonly used ports and there's an editor for that list in case you need to change it.

Promiscuous Mode Scanner adds the Multicast Address 3 test.

Service Lookup replaces the old Database Tests.

SMTP Server Tests now supports STARTTLS and you can select the Protocol (TLS1, SSL2, SSL3), Algorithm (DES, 3 DES, MD5, RC4, SHA) and Minimum Key (40-256 bit) Preferences (not all settings are supported in all operating systems).

SNMP was split in two for clarity, Core and Advanced. It now supports all modes of SNMPv3 (you may need to obtain the OpenSSL libeay32.dll for support the authPriv encrypted mode - we cannot distribute that). We have added WalkBulk, GetNext and GetBulk to the Core tool. The Advanced tool has a launcher for both the Dictionary Attack Tool and the new SNMP Scanner Tool. The Dictionary Attack tool is much faster than before in terms of loading a list of IPs and clearing the display.

Whois now supports IPv6 input queries and if you enter a domain, we attempt to do an IPv6 and IPv4 address resolution on the 'www.' prefixed hostname. History buttons have been added so that you can view previous whois queries made during the current session.

This brings us to overall design considerations. Favorites was a common request during the lifetime of version 10. It was not easily done in version 10, but it was a priority goal in version 11. You can now check a box on each manual tool to add it to the left panel Favorites group. As in NetScanTools LE, we now have a mandatory results database. This is required so that we can bring up historical reports from each tool both manual and automated. Automated Tools was completely rewritten. The Automated Tools use an engine to operate each manual tool given the input and the results are saved to the database. In previous versions, the Automated tools were actually a duplicate of the manual tool that did the same action - not efficient. Running more than one tool at a time is important to some customers, so this new program shell gave us the methods for doing so. As in 10.x, reports are shown in the web browser - the database gives us the method to be able to show old reports from other sessions. The left panel now has tool groupings like DNS Tools, Packet Tools etc. This helps users find tools they need quickly. IPv6 will be a focus of version 11. We have some support in there now, but as version evolves, more IPv6 compatibility will be added - stay tuned!

Please review the video and image gallery on the main netscantools.com page. More information will be posted shortly along with new images and videos.

NetScanTools Pro 10.98.2 Released

On February 23, 2011 we released NetScanTools Pro 10.98.2 both installed and USB versions. Many of the changes have to do with privileges and will primarily affect Windows 7 and Vista users.

Here are the release notes.
-Improved messages that show if writing to a registry location fails. They now suggest escalating the privileges by starting the program with 'Run as administrator'.
-All temporary snmp files are now removed on program exit.
-Improved handling of WinPcap interfaces where both IPv4 and IPv6 addresses are bound to the interface. Affects several programs.
-Internal changes to DNS Tools resolver.
-Port Scanner and NetScanner (Ping Scan) now show warning messages if privileges are not sufficient to run UDP scan and Subnet Mask test respectively.
-Updated SQLite to version 3.7.4.
-Updated database files.

Enjoy!

XP IPv6 Weirdness

This article is about a computer that has IPv6 installed on Windows XP SP3.

I was using Wireshark today checking on the operation of the NetScanTools Pro v11 port scanner when I noticed something weird. Every 10 seconds a set of regularly spaced AAAA record queries were going to my ISPs DNS (default DNS for this system). The AAAA queries were all for 'mycomputername.domain.actdsltmp' and each time the DNS would respond back with 'no such name'. So I started closing down the browser and all the open programs - no change, the queries continued. Since this amounts to DNS harassment and a waste of bandwidth, I decided to find the cause. The 'domain.actdsltmp' part of the request is there because we have an Actiontec GT701 that provides that to my computer as a default domain name.

I could not find a way to shut it off short of uninstalling IPv6, so I did a nice workaround that works well. I added these two records to my hosts file using NetScanTools Pro - you can use something else if you want, it's just a text file. The first record is for IPv4 and the second for IPv6:

127.0.0.1 mycomputername.domain.actdsltmp
::1 mycomputername.domain.actdsltmp

The purpose of those records is to intercept outgoing DNS queries before they happen. This is because Windows DNS queries start with the hosts file, then failing to find the mapping in there, the actual outgoing DNS query is made to the default system DNSs.

Those two records tell whatever is asking for those hostnames that the loopback addresses (IPv4 and IPv6) are the addresses to use. This makes sense anyway because it's asking for a translation of your own computer name.

IPv6 eliminating NAT

I just saw an IPv6 tweet where the guy said he set up IPv6 DNS entries for all his home machines. He can now connect to them directly from his office to any home machine. He was happy to eliminate NAT.

I realize that you don't need NAT when your computers can all have their own IPv6 address - but NAT does provide some safety - think about it:

Now anyone knowing those IPv6s can contact (hack) his machines that are now sitting directly on the internet. Kind of like going back to the mid 1990s. IPv4 NAT was keeping him safe from alot of hazardous traffic that will now hit each PC directly...

Kirk

November Newsletter Published

Yesterday I posted our November Newsletter. Key topics center around NetScanTools Pro version 11.

In case you missed it, our first IPv6 capable tools are making their appearance in this new release of NetScanTools Pro and there is even a new WIFI/WLAN/wireless tool.

Something else we talk about is using NetScanTools Pro on an Apple Mac - find out how.

http://www.netscantools.com/newsletters.html

NetScanTools Pro 11 status

Another week has passed. This week included quite a bit of work on version 11 - again in the area of IPv6. NSLOOKUP and Dig both now accept IPv6 address inputs.

Most importantly, whois now accepts IPv6 inputs. Whois' ip to hostname to ip now work with IPv6. So if you enter a domain name, it will check for both IPv4 and IPv6 addresses. Plus, the whois servers for showing ownership or delegation of the IPv6 addresses are now in the database and it will make the correct query based on the input IPv6 address.

A few more new things next week and then wrap up for release.

Kirk

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!

IPv6 and DNS Tools

NetScanTools Pro v11 Status as of today.

Working on IPv6 additions to NetScanTools Pro v11. We now have two new IPv6 capable DNS tools. I should have the other DNS tools I'm adding complete in the next day or so. Then I will add one or two more IPv6 tools soon after.

Kirk