We know that we need to use ICS on Windows machines to route access from Bluetooth networks to other resources, like the Internet. But ICS is fussy and requires a specific IP address (192.168.0.1) to work. What to do when this specific IP address is already in use somewhere else in your network in conflicts prevent your Bluetooth PDA or laptop accesing the Internet?
I've looked around for a solution for this problem. For some time I've recommended a product from Kerio, but it seems that the company removed the Lite version, leaving only the more expensive Pro version on their web site. It also happened that I've contacted the company in a few times and never received a reply to my e-mails. This could mean trouble for less experienced users trying to configure a software router and in need of support.
One of our users found that NAT32 works well for this task, and it's a cheaper option: US$25 for this software.
The NAT32 software allows you to configure the Bluetooth virtual adapter with ANY IP Address you want, even on a different subnet, and still have the sharing capability needed to allow Bluetooth devices to connect and use your computer as a passthrough connection to the Internet.
I've contact the author, and asked how to configure the software. Here is his reply:
1. In the NAT32 Interface Selection dialog box, select the second private LAN adapter (i.e. the Bluetooth adapter) as well as your first private LAN adapter in the NAT32 Interface Selection dialog box.
2. Be sure the Bluetooth has been configured under Windows so that it uses a fixed private IP address on some network other than that of the first private LAN adapter. A gateway must not be specified.
3. In the subsequent Interface Configuration dialog boxes, all the suggested settings will be correct, and so you just click OK for each of them.
It seems prety simple really. If you have problems with ICS and need a third-party solution for Internet Sharing, give a go to NAT32. The web site has a trial version available for download.