The fact that ICS claims the 192.168.0.0 network as its own is a very-good reason nobody should be using it as their LAN subnet. Not just because it makes it harder to use ICS when you want to, but because it poses a security risk putting ICS DHCP'd nodes on the same subnet as your LAN. You may notice nearly all the home router manufacturers have stopped using that network as their default subnet too.
If you enable ICS on your wired adapter, ICS should then change the IP on your wireless adapter (not the IP of the wired adapter)... and vice-versa - if you enable ICS in the properties of the wireless card, ICS would then set the wired adapter's IP to 192.168.0.1, so the scenario you're telling us now doesn't make sense.
Going back to the scenario you outlined in message
http:#a23040884, set the WLAN and Windows Mobile devices to use DHCP. Whatever adapter you have enabled ICS on, UNcheck those boxes in the ICS section of that adapter's Properties. Delete the persistent routes you added to the routing table trying to make ICS work. Reboot.
Connect to your work LAN so the wired adapter has an address in the 192.168.2.0 network.
Open the wired adapter's properties (right-click it in Network Connections and choose Properties).
On the Advanced tab, check the box next to Allow other network users to connect through this computer's Internet connection. If you usually use the windows firewall, make sure it's enabled before the next step.
Click OK, and wait... ICS will set the wireless adapter to the static IP of 192.168.0.1, and open the necessary ports (67, 68, 80, et al) in the windows firewall so other computers can connect to your wireless adapter and share the wired connection. It often takes several minutes for this step to complete while it makes all the setups.
Now you should be back in Network Connections.
Right-click the wireless adapter and choose Properties.
Check the Internet Protocol (TCP/IP) properties to see that it has indeed been set to 192.169.0.1 (just to confirm ICS made the changes correctly).
Then on the Wireless Networks tab, click Add. A dialog like the one attached should open.
In my example I named it ''SharedHoc'' (sans quotes).
Down at the bottom check the box to make it an ad-hoc network.
You can either set Data encryption to Disabled or select WEP.
If you choose WEP, enter a 10 character passphrase to (semi) secure your ad-hoc network.
(A phone number is as good for a key as anything else... any hacker that wants in can break it in less than 5 minutes anyway, so don't count on it to secure that connection.)
On the Connection tab, UNcheck that box if it's checked, so you never automatically connect to someone else's ad-hoc network that happens to use the name SharedHoc.
Click OK.
Open the wifi setups on the PDA and connect to SharedHoc. Because that box is UNchecked on the Connection tab (and that's for security - you should NOT check it just for convenience) you'll also need to manually connect to the PDA with your laptop once the ad-hoc network is created on the PDA... you'll need to do that each time, not unlike a 2 PDAs talking to each other over bluetooth. Once the PDA is connected to the laptop, AND the laptop connects to the PDA, the PDA should receive an IP address in the 192.168.0.x range and if you do ROUTE PRINT at that point you'll see the laptop's routing table has been modified by ICS to allow the sharing. As soon as the ad-hoc connection is lost, the routing table will go back to normal. If you suspect someone is connecting to it that shouldn't be, just right-click the adapter's icon in the tray (or in Network Connections) and choose Disable.
