Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Jack Russell who wrote (18303)	4/3/2001 10:46:23 AM
From: mr.mark	Read Replies (1) \| Respond to of 110652

steve one of the best networking tutorials #reply-15215706 also, i have these sites bookmarked as being very good practicallynetworked.com cablemodeminfo.com good luck :) mark

To: Jack Russell who wrote (18303)	4/3/2001 10:47:56 AM
From: tanstfl	Respond to of 110652

Hi Steve, I have a cable modem at my other house and it is much simpler to network than DSL (although I prefer DSL for everything but large downloads. Just too much latency in that cable modem. I will say the cable modem is quite a bit more responsive under Win2K than it was under WinME). But back to your question. First,unless you buy extra IP addresses from you cable provider you cannot take the simplest path of running it into a hub and running multiple computers off the hub. With the default single IP address only one computer at a time can access the internet through the hub and obviously ICS won't work since there's no unique connection to share. So you'll need a multihoned setup (two ethernet cards) in one computer with the RJ-45 from the cable modem attached to one ethernet card and the other ethernet card attached to the hub. The other computers are also attached to the hub. I have Eastern@Home cable network and the server computer must not be part of a domain and must be in a workgroup named @Home. The computers that are looking to share the connection also must be part of the @Home workgroup. The TCP settings on their ethernet card must be set to obtain TCP/IP address automatically and they should not have a gateway or DNS server assigned. However, I have often found that I have to assign a gateway pointing to the ICS computer (Gateway = 192.168.0.1) or assign a manual IP address (ie 192.168.0.XXX where XXX is between 2 and 254) or both, in order to allow the computer to find the ICS computer and get assigned the proper TCP setup. Thus you would need to do assign the address; ping the DHCP server (ICS computer) or find it in network neighborhood so they can become buds; and then set things back to get address automatically (requires a reboot afterwards). Sometimes this has to be done multiple times and/or you need both a gateway and address, but you'll need to set it back to get automatically assigned address for the shared connection to work properly. Hope this helps. Good luck, Steve