Apparently I'm a network idiot (360 related)

[Fender]

Yeah yeah... T&T. Move there after a bit of exposure, ok?

Equipment:
cable modem connected to router via CAT5
DLink DI-614+ "router"
DLink DWL-810+ wireless access point/bridge
XBox 360

I had this working just a couple of days ago. The wireless network performance suffered when the wireless AP was running, so I told my wife I'd double check the setup. I upgraded the firmware on the router and the wireless AP to the latest. Desktop (wired) and laptop (wireless) both work fine. But now I can't get my 360 connected.
Router (172.24.99.1) is serving a small DHCP pool (.15 - .20). I've tried manually assigning an IP to the wireless AP and leaving it as DHCP assigned. I can connect to the web-based setup when I manually set the IP, but it doesn't seem to fetch an IP when set to DHCP. I've tried manually assigning an IP to the 360 and leaving it as automatic. Nothing seems to work. This shouldn't be difficult and I've had it working quite easily in the past. Does anyone have any ideas?

edit: Arrrrghhh... I just saw my 360's MAC addy in the DHCP list, but it still didn't work. wtf?

[R00k]

http://www.quake3world.com/forum/viewto ... =1&t=33761

[Chupacabra]

I could tell you.... if only you could read my posts

now that I find funny

[Fender]

What, should I enable NetBIOS?

R00k, that's not it. My 360 won't even fetch an IP from the router.

[Fender]

I can't seem to find older versions of the firmware to go back to, either. It seems like the new firmware on the wireless AP has fucking crippled it.

edit: Maybe I can find the old firmware!
ftp://ftp.dlink.com/Wireless/dwl810%2B/Firmware

[creep]

In my experience dlink wireless is pretty buggy. Had a lot of trouble with their WAPs... my only advice is buy something else. Sorry.

[l0g1c]

What, should I enable NetBIOS?

BAHAHAHAH! *deep breath* AAAAHAHAHAHA!

[l0g1c]

Only help I can offer is from my experience with my D-link wireless router, but I'll give it a shot.

Do you have any sort of MAC filtering enabled?
Maybe reserve a specific IP for your 360 by MAC address if possible.
Try expanding your DHCP pool a bit in case the router isn't "letting go" of some ip's.

[Fender]

Fuck, I think one of my cables is an unmarked cross-cable.

[creep]

Unless your router or WAP have an uplink port, it should be a xover between them.

[l0g1c]

Fuck, I think one of my cables is an unmarked cross-cable.

Hehe, I don't have that problem because all of my crossover cables are ugly, mangled beasts.

[FragaGeddon]

Mine doesn't connect to live when I turn on my 360.
I have to goto the network settings and test xbox live, then it'll hook up.

[Fender]

Unless your router or WAP have an uplink port, it should be a xover between them.

Yeah, I know. But what is strange is that this was working just yesterday. I'm going to see if I can grab one from work tomorrow. If not, I'll make my own tomorrow night and label the damn thing as such.

[FragaGeddon]

I know you need to port forward 88 UDP and 3074 UDP & TCP.

[creep]

I know you need to port forward 88 UDP and 3074 UDP & TCP.

untruth.

[FragaGeddon]

Well true, but mine seems to work better with those ports forwarded. Now if it'd just connect to live when I fire it up.

[creep]

If it doesn't connect to live... how is it working better?

Port forwarding is for incoming connections, not outgoing.

[FragaGeddon]

It's connecting now. Originally it's IP was 192.168.1.109. Then I was having problems connecting.
In my router settings I saw DHCP Clients for the connected computers.
Then there was one client with no name and with that IP, so I deleted it, this was before I knew it was the xbox IP.
So anyways I figured after that it was for the 360 and changed it's IP to 192.168.1.123 through the 360.
But it still wasn't connecting. Then I checked for port forwarding and used those settings. http://support.microsoft.com/kb/908874

It would connect if I tested the connection. I decided to change the IP back to 192.168.1.109 and now it seems to be connecting fine.

Edit: ok now it's not connecting again. It use to connect fine until I updated the stupid thing.

[Fender]

k, x-cable didn't work. Of course it really shouldn't have worked, since I wasn't using one before.
At this point I'm just going to assume that the bridge is kaput.
Anyone know if a standard USB based wireless adapter will work on a 360? I"m not going to pay $100 for the MS one.

[creep]

There are some available that claim to work with 360's. I don't have one to recommend since I bought the MS one

[Fender]

Well, if I'm going to shell out $100, then I might as well shell out $120 and upgrade to G from B.
Anything really worthwhile in the upcoming N spec? It is faster... wow great...

[Fender]

I got a Linksys WRT54GL and WAP54G for $98 after $20 off and $10 rebate. Also have to love free "7 - 9 day business days" shipping that only takes 2 days. Up and running w/ WPA instead of WEP and nice and speedy @ 54 instead of 11.
The WRT54GL will take 3rd party firmware, which is nice. I installed DD-WRT and can now ssh/cron/samba mount my router. Pretty cool, although I don't really have any practical use for the embedded Linux on it other than the regular DHCP/DNS/NAT stuff.