Shows Wrong Internal IP Address; and Port Mappings' Status = Unmapped

What steps will reproduce the problem?
1. Run Port Map 1.0, possibly with VirtualBox installed.
2. Create a Port Mapping (e.g. external: 3000, internal 22)

What is the expected output? What do you see instead?
The IP address it's accessing makes it look like it's connecting to the correct 
device, 192.168.2.1, my router, and when it finds the device, the device name 
it shows is the same as my router, as it should be. But, it shows the internal 
IP address is 192.168.56.1, instead of 192.168.2.3 which is what my IP address 
actually is. 192.168.56.1 is the IP address my VM service (VirtualBox) assigns 
me. When I create port mappings, the status icon is always red.

What version of the product are you using? On what operating system?
Port Map 1.0

Please provide any additional information below.
UPnP is enabled on my router.
If I block access to 192.168.2.1 (my router) with my firewall, Port Map shows 
"No Port Mapping Protocol Found"; otherwise, it seems to work fine except the 
internal IP address is wrong, and all mappings have a status of red.

Original issue reported on code.google.com by mcsierra...@gmail.com on 11 Dec 2010 at 5:51

pomepome / dotnetportmapper

Shows Wrong Internal IP Address; and Port Mappings' Status = Unmapped #6