   Complicated routing under Windows 2000
  Anyone with more experience in network setup want to comment on this?Computer A is connected to the internet via a PPP connection on network card #1 (technically network card #1 is a virtual PPP adapter, which is really going through physical network card #0, but that shouldn't have any bearing on things).Computer A has a second physical network card, network card #2, which connects it to Computer B (crossover cable). Computer A and B can thus see each others shares, and through internet connection sharing Computer B can use the internet from Computer A. Also because of internet connection sharing, Computer A's network card #2 must be 192.168.0.1 (Computer B having only 1 network card and being 192.168.0.2).Now, I have a USB Wifi Adapter, and a PDA with Wifi (Palm TX). I want to setup an encrypted wireless connection that will let me access shares on Computer B and use the internet.My progress so far:I've tried setting up the Wifi adapter on both computers. I can get an encrypted connection working if I allow the PDA to assign it's own IP and leave the Wifi adapter to come up with it's own IP (when I try to assign them both IPs in the 192.168.0.* range it fails).In both cases I can see the shares on the computer the adapter is connection to, but not the other computer (this isn't a problem so long as I can run the adapater on Computer B, which is the only one that has shares I want).In both cases I can access a website hosted locally on Computer B, though I need to use an IP, and the IP differs (if connected via Computer A, I need to use the cable IP [192.168.0.2], which if connected to computer B, I need to use ipconfig to find out what the IP of the Wifi adapter is and use that).In both cases I cannot connect to any internet website, even if I manually enter DNS information (Computer B manually uses the same DNS information) and even if I use the IP address of the website.This is my main dilemma - routing does not seem to be able to get to my 69.*.*.* card, yet on Computer A, it does seem to be able to jump from the Wifi adapter (169.*.*.*) to the local network (192) to reach Computer B's website.If I try manually setting IPs and gateways (on either the device or Wifi adapter), everything stops working.   
  What is displayed if you connect the wifi adapter to Computer A, and run a ROUTE PRINT from CMD? On Computer B?Off the top of my head I'd say hook the wifi adapter to Computer B and run ICS on it to daisy-chain out to Computer A and the internet beyond.   ;  Bridging networks in Windows can be tricky. Here's a thought: Set up the WiFi adapter on computer B, then share the internet connection from computer B's ethernet to the WiFi adapter. Then, turn off DHCP for the shared connection. I've never tried this, and I don't really know if Windows' connection sharing will even allow it.Other than that, I believe you can manually add routes to a machine with the "route" command from the CLI. I've never used it, but I just checked on Windows XP Pro and it exists here so I'm going to take a leap of faith on broken wings and assume it exists on Windows 2000. If I had a Windows 2000 machine around to test this would be a bit easier. Anyway, assuming you've got the setup that almost worked (connected to computer B) you would probably have to add a route on both computer A and computer B.Oh, in the route command help it mentions something about a flag not being backwards compatible to Windows 95 so you had better have it. Good luck. Networking can be tricky sometimes.edit: Or you could just leave DHCP on for the ICS. I didn't catch whether you tried that or not.   ;Quote:Original post by BinchoBridging networks in Windows can be tricky. Here's a thought: Set up the WiFi adapter on computer B, then share the internet connection from computer B's ethernet to the WiFi adapter. Then, turn off DHCP for the shared connection. I've never tried this, and I don't really know if Windows' connection sharing will even allow it.When you turn on Internet connection sharing for an adapter, Windows wants to make that adapter 192.168.0.1. However that is already used by Computer A - computer B needs to be 192.168.0.x where x > 1.;Quote:Original post by MichalsonWhen you turn on Internet connection sharing for an adapter, Windows wants to make that adapter 192.168.0.1. However that is already used by Computer A - computer B needs to be 192.168.0.x where x > 1.Right, but what I was hoping for was a way to manually set the IP addresses. I know you can turn off DHCP for the connections, yet I'm not sure if it would still work correctly. I'm going to guess that it won't, and that you're probably going to have to manually configure routes for the wireless device.Set everything up so it's almost working, with the wireless adaptor plugged in to computer B and using the 169 network and all. Then, use "route print" on the command line of both PCs and show us what you get. I'm guessing computer A doesn't have any information about the wireless network. Apoch had the right idea.   ;  I've been working in that direction (ROUTE). Sharing can't be done, as even trying to turn it on (and planning on changing the IPs after) doesn't work due to the conflict. And this is Windows 2000, so no bridging.Interface List0x1 ........................... MS TCP Loopback interface0x2 ...00 a0 0c 90 63 af ...... Intel DC21143 PCI Fast Ethernet Adapter0x3000004 ...00 40 f4 e0 10 d0 ...... 802.11g USB 2.0 Wireless LAN Adapter======================================================================================================================================================Active Routes:Network Destination   NetmaskGateway  Interface  Metric0.0.0.00.0.0.0 192.168.0.1    192.168.0.26  1   127.0.0.0   255.0.0.0   127.0.0.1  127.0.0.1  1 169.254.0.0 255.255.0.0   169.254.148.30  169.254.148.30  1   169.254.148.30  255.255.255.255   127.0.0.1  127.0.0.1  1  169.254.255.255  255.255.255.255   169.254.148.30  169.254.148.30  1 192.168.0.0    255.255.255.0192.168.0.26    192.168.0.26  1192.168.0.26  255.255.255.255   127.0.0.1  127.0.0.1  1    192.168.0.255  255.255.255.255192.168.0.26    192.168.0.26  1   224.0.0.0   224.0.0.0   169.254.148.30  169.254.148.30  1   224.0.0.0   224.0.0.0192.168.0.26    192.168.0.26  1  255.255.255.255  255.255.255.255192.168.0.26    192.168.0.26  1Default Gateway:  192.168.0.1===========================================================================;Quote:Original post by MichalsonNetwork Destination   NetmaskGateway  Interface  Metric0.0.0.00.0.0.0 192.168.0.1    192.168.0.26  1   127.0.0.0   255.0.0.0   127.0.0.1  127.0.0.1  1 169.254.0.0 255.255.0.0   169.254.148.30  169.254.148.30  1   169.254.148.30  255.255.255.255   127.0.0.1  127.0.0.1  1  169.254.255.255  255.255.255.255   169.254.148.30  169.254.148.30  1 192.168.0.0    255.255.255.0192.168.0.26    192.168.0.26  1192.168.0.26  255.255.255.255   127.0.0.1  127.0.0.1  1    192.168.0.255  255.255.255.255192.168.0.26    192.168.0.26  1   224.0.0.0   224.0.0.0   169.254.148.30  169.254.148.30  1   224.0.0.0   224.0.0.0192.168.0.26    192.168.0.26  1  255.255.255.255  255.255.255.255192.168.0.26    192.168.0.26  1Default Gateway:  192.168.0.1Okay, so this is computer B. You've got the route to the wireless device, several times over (as well as an explicit route to the device's IP) so that shouldn't be the problem. The default gateway is set to the computer with ICS up and running so that isn't the problem either. Your wireless device can probably send a packet out to the internet just fine, but it's not getting any replies because computer A doesn't know where it is. Check to see if there is an entry for the 169.254.0.0/16 network in computer A's route table.edit: cut "You're behind some sort of router, right? Or is computer A acting as a gateway PC?" I can read.   ;Quote:Original post by BinchoOkay, so this is computer B. You've got the route to the wireless device, several times over (as well as an explicit route to the device's IP) so that shouldn't be the problem. The default gateway is set to the computer with ICS up and running so that isn't the problem either. Your wireless device can probably send a packet out to the internet just fine, but it's not getting any replies because computer A doesn't know where it is. Check to see if there is an entry for the 169.254.0.0/16 network in computer A's route table.edit: cut "You're behind some sort of router, right? Or is computer A acting as a gateway PC?" I can read.192.168.0.1 = Computer A, wired adapter connected to computer B192.168.0.26 = Computer B, wired adapter connected to computer A169.254.148.30 = Computer B, wireless adapter (it automatically gave itself that IP, that's not the IP of the PDA)Computer A is the router/firewall as such, it runs internet connection sharing from an adapter connected to the internet to the "internal" 192.168.0.1 adapter.Quote:Original post by sirobHave you tried putting the wireless adapter on ComputerB, selecting both connections and using the windows bridge function? What about bridging the two on ComputerA. One of these options should probably get you further.*Windows 2000*   ;Quote:Original post by Michalson192.168.0.1 = Computer A, wired adapter connected to computer B192.168.0.26 = Computer B, wired adapter connected to computer A169.254.148.30 = Computer B, wireless adapter (it automatically gave itself that IP, that's not the IP of the PDA)Computer A is the router/firewall as such, it runs internet connection sharing from an adapter connected to the internet to the "internal" 192.168.0.1 adapter.I misread the routing table from Computer B, that makes sense. Regardless, can you ping your wireless device from Computer A?   ;  I can ping my PDA from Computer B, but not from A.   