Built in NIC
or
Are they connected ?
Your description leads me to believe that your motherboard may have a built in NIC. If that is the case, you should be using that built in NIC to avoid conflicts. A second NIC can usually be added to any machine but you will have to make sure that they are using different resources. Check your machine to see if you do indeed have a second NIC installed. You will be able to see the RJ-45 connection point on the both NIC's. Computers can be connected NIC to NIC but you require a crossover cable to make it work. If your machine has a built in NIC then you can take the 3Com adapter out and use only the Dlink. Using a regular (not crossover) cable you would connect your 500 to the hub and a regular cable would connect your 600 to the same hub. If they have the same protocols loaded and are on the same network they should be able to see each other. The problem is usually in the fact that your DSL machine is already connected to a network and you want it to live on two networks. You should run Winipcfg to obtain your DSL enabled machine's network settings, make a note with these settings, you will require them later to share your DSL.
When you connect your DSL, connect to a regular port on your hub as opposed to the uplink port.
Try this first, plug in the hub, take the cable going from the computer to the DSL connection and move it to the hub (not to an uplink port), you should see a linklight on the hub. Take a new cable (not crossover) and connect the DSL to the hub (not to an uplink port), you should see a linklight and your DSL should still be working on your 600. Now using just the Dlink adapter, run a cable from the 500 to the hub (not to an uplink port). If you are loading the right protocol (TCP/IP) and have the same Workgroup name your 500 should get a linklight and be able to see your 600 and vice versa. If you haven't changed anything on your 600 setup, it should still be DSL enabled. Now you are ready to use Wingate to share the connection (and you didn't need to mess around with a single IP octet.)
The 500 will not be able to get information from the DHCP server that your ISP is running. You will need to assign the machine an IP, a default gateway and a subnet mask. You will also require the DNS information for your ISP's servers so that the information can be entered into the 500's Network Configuration. |
