Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
However that PC is gone to shit and I'm about to dump it so I've decided to use my main PC as the sharing center for my 360.
Problem is it doesn't work.
I have the settings, as far as I can tell, identical to what they were on my old PC even though this one is Windows 7 instead of XP.
Previously my problem was that my LAN was on the wrong network location so when I changed it to my "Home" network it just worked fine after that.
The problem now is that I can't change the LAN connections location for some reason. There is no option to change it at all and I'm going nuts. I've checked troubleshooting etc and it says to just "click the network location to change it" but when I look at my network lists it lists my wireless connection as my home network fine and dandy but under it it lists the LAN as an "Unidentified network" that is a "Public Network" and it won't allow me to change the name nor the location.
Is there something I'm missing here? This is really getting on my nerves and I'd like to get this taken care of so I can use my 360 online again.
In a bit of pissyness I just bridged the two connections instead of dealing with the connection sharing for the time being.
It seems to have worked but now I'm back to getting dumbass NAT level errors. I don't recall having to open any ports on the PC itself before; only on the router, and I've done that.
Better than nothing atm but I'm not sure if just bridging the connections like that is idea. For one my stupid wireless icon is gone off my taskbar and there seems to be really limited options for fiddling with the bridge.
I think you have to bridge it now, and I also got NAT level errors when I had mine like this. The errors didn't affect MW2's multiplayer or voice, so I just disregarded them
Apparently bridging the connection lets me set up a static IP on my 360 instead of letting my adapter do the IP setting for me; so I just set up my port forwarding for the NAT settings on my router for the 360 specifically instead of my PC like I had before and it worked perfectly.
Weeeee.
I was totally overthinking this whole ordeal.
Just FYI for folks, I noticed in a similar thread a few pages back that everyone was saying you needed a crossover cable to do this. I'm using the 360 cable that came in the box so I can verify that you don't.
EDIT: I can now get back to playing Final Fantasy XIII which requires no internet connection anyway! :lol:
Just FYI for folks, I noticed in a similar thread a few pages back that everyone was saying you needed a crossover cable to do this. I'm using the 360 cable that came in the box so I can verify that you don't.
Not really. Either the NIC on the 360 does autosensing or the NIC on your PC does. Going between two PC like devices requires a crossover cable, its just that newer NICs autosense and simply change pinouts electronically to make sure things work regardless of the cable plugged in.
So, an odd side effect of all this crap is that every time I turn on my 360 now it tells me XBox Live cannot be reached. However, if I go to the "test connection" section and test the connection it works perfectly fine. I then go back out to the dashboard and sign back in and it works fine.
WTF.
Every time. I'm not entirely sure what the deal is.
So, an odd side effect of all this crap is that every time I turn on my 360 now it tells me XBox Live cannot be reached. However, if I go to the "test connection" section and test the connection it works perfectly fine. I then go back out to the dashboard and sign back in and it works fine.
WTF.
Every time. I'm not entirely sure what the deal is.
Again, mine did this, it's annoying, but better than paying $100 for MS's thing
I bought a WRT54GL, and used DD-WRT to make a 4-port wireless bridge. Works great downstairs.
Also got a second random NETGEAR router for the same use in the bedroom.
Works great, and doesn't require the PC to be on.. a good wrt54gl is about half the cost of Microsoft's wireless adapter, and it may be overkill for your situation.
So, an odd side effect of all this crap is that every time I turn on my 360 now it tells me XBox Live cannot be reached. However, if I go to the "test connection" section and test the connection it works perfectly fine. I then go back out to the dashboard and sign back in and it works fine.
WTF.
Every time. I'm not entirely sure what the deal is.
The official wireless adapter actually has this problem too
Posts
It seems to have worked but now I'm back to getting dumbass NAT level errors. I don't recall having to open any ports on the PC itself before; only on the router, and I've done that.
Better than nothing atm but I'm not sure if just bridging the connections like that is idea. For one my stupid wireless icon is gone off my taskbar and there seems to be really limited options for fiddling with the bridge.
A cool side effect of doing this is now I can use my 360 with my main PC with Media Center, so that's cool.
I'm gonna just put the ports I need in my firewall and see if that helps, but I know I have them all open on my router.
Apparently bridging the connection lets me set up a static IP on my 360 instead of letting my adapter do the IP setting for me; so I just set up my port forwarding for the NAT settings on my router for the 360 specifically instead of my PC like I had before and it worked perfectly.
Weeeee.
I was totally overthinking this whole ordeal.
Just FYI for folks, I noticed in a similar thread a few pages back that everyone was saying you needed a crossover cable to do this. I'm using the 360 cable that came in the box so I can verify that you don't.
EDIT: I can now get back to playing Final Fantasy XIII which requires no internet connection anyway! :lol:
Not really. Either the NIC on the 360 does autosensing or the NIC on your PC does. Going between two PC like devices requires a crossover cable, its just that newer NICs autosense and simply change pinouts electronically to make sure things work regardless of the cable plugged in.
WTF.
Every time. I'm not entirely sure what the deal is.
Again, mine did this, it's annoying, but better than paying $100 for MS's thing
Also got a second random NETGEAR router for the same use in the bedroom.
Works great, and doesn't require the PC to be on.. a good wrt54gl is about half the cost of Microsoft's wireless adapter, and it may be overkill for your situation.
The official wireless adapter actually has this problem too
and Operation Flashpoint: Red River code to trade/sell
and Halo: Reach code
and Portal 2 code