Networking help?

[blueonblack]

Ok, I'm completely new to wireless networking. I'm in the middle of moving and will *finally* have cable Internet, and I want to share the connection among at least three computers. Can someone point me toward a good guide for getting that done? It seems everything I pull up with my admittedly anemic Google-Fu is outdated. "How to share you dial-up connecion with your kids!"

[slaveofconvention]

Usually, you just plug the cable modem straight into one of the PC's to get the connection set up and working, then unplug the PC and put the network cable into the WAN port of "a" router (Assuming you have a router heh) - then you simply connect to the router either by wires or wireless. PM me if you have any "random" router questions...

[x88x]

1) Either rent from your ISP or buy a wireless router. You can get a cheap, decent one from any local electronics store. Netgear makes a nice cheap one that usually goes for ~$30-40 at Best Buy.

2) Plug the LAN cable from the cable modem into the 'WAN' port on the router.

3) Connect a computer to a wired port on the router.

4) Connect to the router management interface (usually 192.168.1.1 by default).

5) Find the DNS server settings and change it to use the OpenDNS servers:
primary: 208.67.222.222
secondary: 208.67.220.220

if you have no wireless devices, skip to 7
6) Set up the wireless, wireless security (use WPA2), and any other configuration options you want.

7) Enjoy!

[OvRiDe]

Hey Shane that Trendnet router should fit the bill perfectly. The setup is similar to x88x's guide, except I believe the management interface is 192.168.10.1. I believe it is already setup for DHCP so there is no need to change the DNS settings to OpenDNS. Infact you really should be able to just plug it in and look for the wireless network that has TBCS in it. You have my number if you have any problems.

[x88x]

I believe it is already setup for DHCP so there is no need to change the DNS settings to OpenDNS.
DHCP assigns local IP addresses, DNS correlates url's to IP addresses. The reason I recommend setting up with OpenDNS is because in my experience ISP DNS servers tend majorly suck. Seriously, my browsing speeds felt like they almost doubled when I moved off the Verizon DNS servers.

[blueonblack]

Ok, lots of info there, thanks. Since it seems I will have to have the router physically plugged into a computer, I'm assuming I could stick the cable modem in a corner (or closet with cable access) connected to the router and a simple system to act as a server/network hub? Then just stick wireless cards in the other systems I want to network and they can access whatever is stored in the server system, correct?

Would this be fast enough to stream HD video via Netflix from the server to the HTPC without visible degradation? This is the router (http://www.trendnet.com/products/proddetail.asp?prod=160_TEW-673GRU&cat=41) I'll be using.

[x88x]

I assume you mean 'hub' in media terms, not networking terms? If so, then yes, that will work just fine. I regularly stream stuff from my server, everything up to 1080p and I've never had problems. If you want to transfer any large amount of data between computer, though, I would highly recommend plugging them both in. Even with 802.11n, the performance difference between wireless and gigabit wired is very significant.

EDIT:
TO clarify the 'hub' thing, the router will handle all the networking details. The server will just be another device as far as it is concerned.

[slaveofconvention]

If you aren't changing anything - do you remember the password for the wireless network?

[blaze15301]

i second the open dns servers. i have been using them for a year or so now and i cant be happier.

[OvRiDe]

DHCP assigns local IP addresses, DNS correlates url's to IP addresses.

Wow really!?!? :eek:

You would think the 18+ years I have been working with professional networks I would know that. :rolleyes:

What I was referring to is that the router he has is already setup to be a dhcp client on the WAN port. (Its the one we used in Vegas) So all he will need to do is plug the Ethernet cable from cable modem into the WAN port and he should be good to go. After that just open up the wireless section on your computers and search for the SSID.


The reason I recommend setting up with OpenDNS is because in my experience ISP DNS servers tend majorly suck. Seriously, my browsing speeds felt like they almost doubled when I moved off the Verizon DNS servers.

As for configuring OpenDNS.. he is moving from an air card to a cable connection, his browsing experience is going to increase anyways without adding a layer of confusion. I figure once he is more comfortable with the router he can make the changes if he desires.

[x88x]

I believe it is already setup for DHCP so there is no need to change the DNS settings to OpenDNS.

What I was referring to is that the router he has is already setup to be a dhcp client on the WAN port.
Still doesn't have anything to do with DNS.. -_^

He asked for advice, I gave my advice. If he doesn't want to follow it I have no problem with that. In my experience, DNS server settings are usually on the main settings page, making it a simple change to make if you know to do it. It doesn't matter if he were coming from dial-up, I would still recommend it. No sense wasting potential.

[dr.walrus]

It's so easy to set up these days i just sort of throw the router at my computer and it's done.

[AmEv]

That would be the day, Walrus.

[dr.walrus]

Wow really!?!? :eek:

You would think the 18+ years I have been working with professional networks I would know that. :rolleyes:


...


I believe it is already setup for DHCP so there is no need to change the DNS settings to OpenDNS.

Oh yeah, you did just fly off the handle after someone corrected you for posting something nonsensical.

I'm not sure what a professional network is, either. Is it one that wears a suit?

[dr.walrus]

That would be the day, Walrus.

To be honest, things are so easy to set up these days, you can practically just leave all the stuff in the box and breathe heavily, and suddenly you've got internet...

I spend extraordinarily small amounts of time setting up network connections these days - the industry really, really has got its act together for simple networking products.