Software Development => Win32Whois => Topic started by: Gena01 on November 09, 2006, 12:49:38 pm

Title: Win32Whois 0.9.12
Post by: Gena01 on November 09, 2006, 12:49:38 pm
Please report issues, bug reports, ideas here.


Title: Re: Win32Whois 0.9.12
Post by: shuisman on January 10, 2007, 07:18:39 am

First of all... Great program!

But the program doesn't work anymore, i think its has to do with of the (new) buildin firewall in the router.
Do you have suggestions, is there a special port that needs to be set open?

Hope to hear soon, thanks!

Title: Re: Win32Whois 0.9.12
Post by: therube on January 11, 2007, 01:03:01 pm
Shouldn't have anything to do with your router.

If anything, I would think it is your software firewall that would be blocking it.
New version, different from older.  Firewall is seeing a different application, so blocks it.

Title: Re: Win32Whois 0.9.12
Post by: garlic22 on March 16, 2007, 08:04:16 am
With the latest version (0.9.12), it may not work unless RWHOIS is disabled from the Options menu.
After disabling that, it should work fine.

Title: Re: Win32Whois 0.9.12 IP Lookup
Post by: CAOgdin on May 14, 2007, 02:10:02 pm
My own domain is  Because I have a website inside the firewall, I have used a static assignment in C:\WINDOWS\system32\drivers\etc\HOSTS so my local browser will open the website for maintenance.  This is to circumvent a firewall restriction that prohibits internal requests for (local) external addresses.

That means my report from Win32Whois starts:

Querying for domain =

Note the non-routable internal address.

In fact, my external IP address for * is in a static range (which, no doubt, you can lookup   ;) )

Might I suggest, therefore, that you exclude local HOSTS file lookups from your DNS resolution of a domain name?  It's the same problem that every Dynamic DNS client faces; some are rather smart, and report the first routable address retrieved from an arbitrary trace-route to some friendly site (e.g.,  That excludes all the 10.*, 172.16.* and 192.168.* IP address ranges from being equated to the domain name in your neat program.

If you think the existing feature needs to remain, you might want to make it an Option ("Bypass LAN").

Thanks for the wonderful program,

--Carol Anne