Networking Prob...

Okay, I'm not new to networking at all, and having a weird problem. I have a small network setup in my home, with the Cable Modem, Wireless Router, hp 5800 printer and my roommate's Desktop in the living room. The desktop and printer are connected on cat5. In my room is my desktop, my xbox and a small file server. My desktop is connected via Wireless-G to the network. DHCP is assigning IPs by MAC Address. The IPs in use, and what is using them is as follows

Router - 192.168.0.5
Printer - 192.168.0.100
Roomie's PC - 192.168.0.101 (Running WinXP Pro)
My PC - 192.168.0.115 (Running WinXP Pro)

My PC has dual onboard NICs, so I want to use them to connect the xbox and server to the network, until I get Wireless for the server. I was originally going to just share the internet connection via Windows Internet Connection Sharing, but this is where the weird part comes in. When I try to enable it it says about setting one of my NIC's IP to 192.168.0.1 and I say okay... couple seconds later it gives an error stating that this IP is in use! Now, I have looked at the list of IPs leased by the router and 192.168.0.1 is not one of them, the router itself is using 192.168.0.5 like it's supposed to. I've restarted the router since making changes to clear the current IP Leases, but no matter what I do it says 192.168.0.1 is in use.

Because I am lazy, I would like to get it working the way it is, however I feel I may need to swap the Wireless card over to the Server (FreeBSD) and get it working there, and use NAT & IPForwarding to basically make a router out of it.

My main question is is there something I have overlooked?

ping the .1 address and use nbtstat with the -A switch to see if you can get a NetBIOS name out of it if it is pingable. Not sure why you say .5 is what the router is supposed to use unless you've manually changed it. Typically a router, even a SOHO NAT router, will be .1 as the gateway address.

also if you have a router already doing the routing, you cannot use ICS.
Although i think form your post you srent using it... err um nevermind...
If you are trying to use ICS while a router is running, you will get this IP conflict.

What you should do in this case is create a bridge between the two network cards. Go to network properties, right click on one of the connections and hit bridge. Not the most stable way of doing it, but its good enough and really easy.

ktwebb said:

ping the .1 address and use nbtstat with the -A switch to see if you can get a NetBIOS name out of it if it is pingable. Not sure why you say .5 is what the router is supposed to use unless you've manually changed it. Typically a router, even a SOHO NAT router, will be .1 as the gateway address.

Click to expand...

Yes I manually reassigned it because it gives an IP conflict saying 192.168.0.1 is in use (as ICS sets the port used for routing as 192.168.0.1), so i set it to use .5 and I still get the same IP conflict. Pinging .1 yields no returns, all packets are lost.

Phaedrus said:

also if you have a router already doing the routing, you cannot use ICS.
Although i think form your post you srent using it... err um nevermind...
If you are trying to use ICS while a router is running, you will get this IP conflict.

Click to expand...

Well, as I said, I had it working before when I was in the dorms, now however with the Wireless it is not working at all. Perhaps it's all my imagination, but i am pretty sure it was working back then. Mind you, this was when I was running Win2k Pro as well, so that may have something to do with it.

Karlos said:

What you should do in this case is create a bridge between the two network cards. Go to network properties, right click on one of the connections and hit bridge. Not the most stable way of doing it, but its good enough and really easy.

Click to expand...

This didn't work either, bridging the Wireless w/ Wired caused Wireless to be unable to connect to the router. Bridging the 2 wired connections would be pointless since they aren't connected to anything, so I assume the wireless/wired bridge is what you were referring to.

well, if your running a soho router, that is NAT. Then your running ICS, which is also NAT. You cant run two routing solutions on the same subnet. I'm assuming you have a router going and cant enable ICS, or get that error message. I think bridging is what you want to do on the multi-homed since you already have NAT running(router).
Bridge

You might have had it running, I've seen crazier things, but this is sort of one of the ground rules of soho routing, only one routing solution per subnet.

So from the looks of that article, I can't do Wireless LAN and Wired LAN bridge?

The USB thing I imagine would work, but I don't have a cable I could test it with.