[MDA III, XDA III, PDA2k, 9090 Software Upgrading] fraser:
I'm looking into this now. It's possible the device name needed for the registry is similar to windows naming i.e. a string. For example, on my pc here I have several interfaces listed via "ipconfïg" such as "Ethernet adapter BT". When you manually drop/request an IP using this command, you use this string as a parameter (quoted IIRC). Looking in vxUtil under info we have several possible candidates. The seems to be a naming convention in all of the names listed with a " - " separator and two parts. Some don't have the latter part so it's a possiblity that it's vxUtil that's printing them like that and we only need the alternatives.

However, vxIpConfig has a drop-down list with all of the active connections that may seem like a better candidate for these values. I note that the BT one is "BTPAN1". The number suggests to me that these are unique values.

Here's what I think may be a possibility (from vxIpConfig):

WiFi: tiacxwln1

BT: BTPAN1

GPRS didn't appear in ipconfig even while I was downloading mail. According to vxUtil, the "current IP" listed was the same as the one listed under "Cellular Line". Hmm, not sure about that one.

Using either method, the wifi and BT ones are the same. I'm going to try this first as it should be easier.

Another thing; along with the key "Public Interface" in the registry, there is also a "Private Interface" key that may need set. The unset value may mean "all" however. That probably isn't desirable in the long term.

WRT to the packet filtering, the default on win2000 and pre SP2 XP for the basic network filter is "allow all" as far as I can understand. We probably want to switch that off just now.

I'm experimenting with a setup just now. I've got the laptop connected to a BT pan network to the phone. I've got the phone hooked up to my wifi network which routes to the net. Once ICS is running, all I should need to do is launch a "route add" command on the laptop to instruct it to send traffic to unknown networks (the default route) to make it go via BT.

If I can hit www.google.com's IP we are over the biggest hurdle. Let's see how it goes, will post back after playing around.

Once done, we don't need to bother with a dhcpd as I suggested in the other topic. That's done for us by the BT pan. However, I'm not sure if it deals with DNS so I recommend that if anyone is trying this that they stick to hitting remote ip addresses only. That's the first step that needs to be established. The phone may need a default route set, but I suspect that will be done if you can already route out over the wifi network.

EDIT:

OK, no success yet. Setting IP address manually on the BT PAN allowed me to ping the phone. The default route was set to the BT IP and the pc attempted to connect over that interface. As far as I could tell from the (limited) msdn docs on this topic, I had it enabled. I also tried changing "disabled on boot" to "0" with no success.

With the BT interface on the pc set as DHCP, I could not get an IP. According to http://msdn.microsoft.com/library/d...en-us/wceics/html/_wcecomm_dhcp_allocator.asp , the mini dhcp server is limited but to be honest it seems to have most of the options you'd expect from an ICS one, even going so far as allowing static hostname/ip allocation. Interesting, that's a useful feature. I mention this because I could not get an IP. I suspect that the problem is that I simply haven't enabled ICS at all.

Are there any applications that anyone can think of that use ICS internally? ActiveSync probably does, but it'll be the pc doing the dhcp bit I'd presume. How about someone who has BT/GPRS running on another device? Can they share their related registry settings (while connected) for the keys that joe mentioned? What would be best would be the whole set of keys for:

HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms\

HKEY_LOCAL_MACHINE\Comm\ConnectionSharing\