[Cobra]

About a week ago i tried to install my router so i could connect my xbox to the internet. the router is deciding to be a *****. it won't let me get a connection through, and everyone i called for help (LinkSys and Verizon) couldn't help me, (LinkSys wouldn't help me because i didn't have a connection, and Verizon doesn't know **** about routers), so i thought i'd come to a  reliable source once i could connect through my modem again.

so, help?

and don't flame me.

this is the info i got after the shut-down-everything-for-3-minutes procedure:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>ipconfig

Windows IP Configuration


Ethernet adapter Intel LAN:

        Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter LinkSys LAN:

        Connection-specific DNS Suffix  . :
        Autoconfiguration IP Address. . . : 169.254.197.137
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        IP Address. . . . . . . . . . . . : fe80::212:17ff:fe58:9923%5
        Default Gateway . . . . . . . . . :

Ethernet adapter Hamachi:

        Media State . . . . . . . . . . . : Media disconnected

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%7
        Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::5efe:169.254.197.137%2
        Default Gateway . . . . . . . . . :

[achtung]

Now that you have a connection why not try linksys again?

[Cobra]

did that 10 minutes ago, didn't work.

[MatthewPapa]

IIRC you have to forward a TCP port to the xbox but i dunnot know for sure; ive never owned an xbox

[Nix]

What kind of connection are you using?  Cable/DSL, and is your Cable or DSL modem a router as well?  If you do this, an easy way to get this to work is to switch off routing capabilities in the modem to make the router "route" traffic.  A router hitting another router requires some odd setup that I'm not quite too familiar with.  Most of my modems use transparent bridging which makes the DSL modem a "dumb modem" and the router behind the modem does all the routing work.  Why can't you get this to work using a switch, and letting your DSL modem do the routing?  (assuming it actually is a router)

[Stealth]

what Nix is referring to is the ability some cable/dsl modems to be put in "Bridged" mode, meaning they just bridge the connection, they don't assign any internal IP address or anything, and you can make your linksys have a public address, or whatever (only use with static IPs though).

OK this is going to be long and tiresome, but here goes:
1) 1st step, you've got your linksys connected directly to your cable or DSL modem, right?  what lights are on and what colors on the cable/dsl modem? 
2) you have your computer attached to your linksys, right?  do you have your internet connection defined as DHCP or static?  make sure it's DHCP.  if necessary, assign yourself an IP on the same subnet as the linksys, and try to get into its webinterface (i.e. http://192.168.1.1 or http://192.168.0.1/)

anyway,

[Scuddie]

Are you intentionally running your router in IPv6?  If so, stop it.  Stop it right now.  Stop it and use IPv4.  And why the hell are you running two IP tunnel controllers?  Your network configuration scares me.  Take it away!!  Please!

Anyhow, when a 169.254.x.x IP is given, it is saying that essentially your connection is not syncing at the IP level, or at the MMC level.  Answering these will help clear things up for us:
Are you using a crossover cable or a patch cable? 
Is the cable going from your modem to your router connected to the WAN port? 
Are you sure it's a router and not a switch? 
Mind telling us the model number?

EDIT: Clarity is always a good thing.

[Cobra]

Meh. here's the deal: in theory, this is all set up right. i just got off the phone with a linksys technician, who helped me set up the router and stuff. and, i didn't know what i was doing so that's why i have a crappy setup, scuddie.

the problem is that my modem doesn't 'hand out IP addresses' to the computer and xbox, as the technician put it.

[Martinus]

Then set it static, set the modem as 192.168.0.1 and all of the computers attached to it as 192.168.0.* , where * is any number between 2 and 10 (it goes higher but don't worry about that for now). Make sure the netmask is set to 255.255.255.0 in all cases and if necessary set your gateway to 192.168.0.1 .

If you still can't connect to the net make sure the computer/xbox are retrieving the DNS IP properly. If you type ipconfig /all into a CLI you'll get the DNS servers.

[Cobra]

well i'll be damned. i checked my other adapter's settings and unchecked the network monitor driver and TCP/IP 6 as i did with my other one, and it worked!

[Scuddie]

Told ya so .

[Cobra]

i actually didn't realize it until i checked.

[Martinus]

Now that you've got the xbox on the internet you can softmod it and turn it into a NAS!

pre-requisites:
Know how to softmod.
Understand Linux.
Understand Networking.
Understand why an xbox based NAS is good.

It's really the best use for it anyhow.