vonney0281 :
Hello, I've tried about everything to get a connect to my second desktop. I've asked Walmart associates and they sold me the wrong router. I've asked Bestbuy Geek Squad and they trying to sell me a 100 dollar plus router. I've done the Internet searches on how to connect two PC to share a signal but can not figure it out.
I tried adding hoc, internet sharing option, and changing properties. I have a Trendnet product that came with the PC I think it's used to help get a signal because I can pick up someone elses signal or modem. I've been working at this for three days and I don't want to call it quits yet because I know it can be done, I must just be missing something wrong or missing something.
Can anyone give me some advise I would really appreciate it. The host computer is running Windows XP and is an older model so it doesn't have a ITP protical version 4 or 6 it just has a regular one will that work as well when setting up ICS. The other desktop run Windows Vista and I'm using a cricket Broadband.
I've tried asking help from stores where to associates should know but it seems they just trying to sell me stuff.
It might have been better to start your own thread since I'm not sure how much of what has already been posted is relevant. Anyway, let’s describe the goal, then how to achieve it.
Let's say you have two computers, A and B. Computer A has a broadband connection (doesn’t really matter what type; cable, dsl, cellular (Cricket), etc., it’s all the same for the purpose of this exercise). You now want to share that broadband connection w/ computer B. To keep it simple, let's assume computer B is strictly a wired-only machine (i.e., has an ethernet port).
< -- broadband (to isp) -->[computer A](lan)<-- wire -->(lan)[computer B]
In order for this to work, computer A and computer B must minimally have an ethernet port (that's the lan to lan connection in my diagram). Computer A needs to "route" the traffic between its broadband network interface, and its local network interface (the lan to lan connection to computer B). In fact, we can legitimately say computer A needs to become a router!
But none of this happens my magic. We have to have the necessary software to bring this all together. That software is called ICS (Internet Connection Services). Thankfully it’s already installed by default, just not configured. You enable ICS on the network interface w/ the broadband connection. ICS then detects the other (local) network interface, assigns it a static IP address of 192.168.0.1, and starts its own DHCP server. Any computers on the other end of that local network interface can then use that DHCP server to obtain their TCP/IP configuration. That configuration includes a unique IP in the 192.168.0.x address space (e.g., 192.168.0.2), DNS servers (usually obtained from the broadband connection), and gateway IP (ICS itself, 192.168.0.1). Once ICS is configured, you merely reboot computer B (so it renews its DHCP request) and it should be working. Computer A is now a router. It manages the traffic back and forth between its two network interfaces on behalf of any computers on the local (192.168.0.x) network.
Of course, we could extend this routing capability to additional computers (C, D, …) by using a switch and/or wireless AP.
< -- broadband (to isp) -->[computer A](lan)<-- wire -->(lan)[switch/wireless AP](lan)<-- wire(s) -->(lan)[computer B, C, D, …]
That's how it works. Once you have the physical connections setup correctly, there actually isn't a whole lot to do other than enable ICS. It pretty much does all the things I described behind the scenes, w/ little to no intervention on your part. Perhaps the only gotcha I can imagine is if computer B is not configured to use DHCP. If that was the case, computer B would obviously not obtain the correct TCP/IP configuration from ICS’s DHCP server, and thus wouldn’t have Internet access.
You could also replace the wired connection between computer A and computer B w/ a wireless ad hoc connection.
< -- broadband (to isp) -->[computer A]<-- wireless (ad hoc) -->[computer B]
Notice this has no bearing AT ALL on ICS, routing, or anything related to Internet access. Any problems you have in establishing that particular connection have nothing to do w/ ICS. That’s why I strongly suggest, even if you wish to use a wireless connection between computer A and computer B, that you start w/ a wired connection and get it working. Then deal w/ any wireless connection issues later. The simpler you keep it in the beginning, the more likely your chances for success.
Yes, it’s definitely a complex process to implement (from the software's perspective), but for YOU, it's actually just a few clicks here and there. I don’t normally go into such detail, but I’m hoping it helps you visualize things better so perhaps it doesn’t seem so intimidating.