How to share @Home

[jb0506]

I currently use @Home at my house and i want to be able to share it through a hub, i have a Intel Inbusiness 8-port hub, and on @home's website it says connect the modem to the hub through cross-connect, which i did. and DHCP assigned my IP address and everything except it wouldnt let me surf the net. I dont know if my gateway wasnt right or something, but i was also wondering if i had to pay the extra 9.95 a month for another ip so my second computer could have internet access also. i currently have my main computer running MS-ICS routing all the traffic but i want to rearrange my house and have my computers in another area and i wanted to know how i could get the hub in the picture. thanks!

 

[Fallen Kell]

There are a few options.

1) Get a router, hook the output of the cable modem to the input of the router, use cross-over from output of router to HUB, use standard patch cables from HUB to comps.

2) Buy extra IPs from @HOME (one per computer, and I can't believe it is $9.99 a month more for you, its only $2.99 where I am), use cross-over to hook cable modem to HUB, connect all computers to HUB with standard patches.

3) Install 2 NIC's in main computer. Hook cable modem into one NIC, hook HUB to other NIC. Hook all other computers into HUB. Run a NAT program on the main system (downside: main computer has to be on, or no computer can get internet access).

As in terms of easiest things to do, I would say that #2 is easiest, but you pay for it every month. #1 is the second easiest and you have a 1 time fee involved in buying the router (~$60 for a router with DHCP services, firewall, and PPPoE support). Then #3 is the most difficult to setup properly and like I said the main computer has to be on for any others to get internet access.

I personally use the #2 method. The added protection of a hardware firewall is almost immeasurable.

 

[Phil21]

put two NIC's in your computer, and connect the cable modem directly to it via an x-over cable. then the second NIC should be set to an internal IP (192.168.0.1 for example) and you should enable ICS or whatever via that interface. connect that NIC to the hub, and your second computer to the HUB with an internal IP as well. Set the second boxes gateway to the internal IP of the box with ICS, and you should be set (assuming your @home is working on the first box).

Of course, you can connect the cable modem to the hub via an x-over (or to the uplink port on the hub with a normal cable) and do the same thing, only have the first NIC (@home NIC) on the ICS box connect to the hub as well.

hope it helps you a bit,

-Phil

 

[RiceDiGiZ]

i agree wit them... i have @home also... but if you got 100 bucks to spend get a router... it would save u time... and power.... and its better

 

[spidey07]

and it is easier to manage, and it more flexible, and, and, and, and, and.

buy a router.

 

[Tominator]

Router...nuf said.

 

[Cyberclix]

I have set up the SMC Barricade 7004BR for clients. Works great! But for @Home service, it works better if you hardcode an IP address in the router. Outpost.com has delivered my routers overnight ... everytime - ontime. The Barricade also comes with a Print server built in and when I tested it for vunerability on Shields UP site ... it passed with flying colors.
UPDATE: did I forget to mention has built in DHCP and NAT and ... and...

 

[jb0506]

thanks ill look into buyin a router when i get paid again

 

[crazychicken]

whatever you do, DO NOT pay for multiple IPs unless you have a specific purpose in mind for them. They don't deserve the extra money. All you need to do is get a simple 1 port router that you can plug into your hub. The software with the router will allow you to set it up with no problems

later
david

 

[Hoober]

I've got @Home and have it networked to five computers through a Linksys router. I bought one extra IP address so I can play QIII Arena on the same server as somebody else on my network without any problems. other than that, I'm not going to shell out the extra $10 a month for more IP's when @Home can't even tell how many computers I have behind the router's firewall. Its the only way to fly.