I'm not a networking expert, and I haven't found a solution for this. My debug Xbox is connected though a ethernet hub to my comp (PC or Mac Pro running a WinXP VM). What happens is that I constantly get the bogus IP address, which takes too long to connect sometimes. I can still access Xbox Neighbourhood in all, but it doesn't work the way I need it to work. When I had an ethernet cable plugged into the router directly from a modem, it will give me the 192.168.0.x IP address I want. Right now, I don't have internet service, and I'm using my neighbour's wifi to get on the net. So, what's a solution to this? Thanks. Shogun.
169.254.x.x is the address range Windows and Windows-based OSes deal when they couldn't get a DHCP response. Somehow it seems that hub is messing with your modem's DHCP messages.
Using VMWare on my Mac Pro, I always seem to have to toggle the NAT settings or play with the Internet Sharing in OSX. Once it finally sticks and gives a proper IP address, it seems to function without issue for a while, or until I mess with things.
If your using your neighbors wifi, and the PC and XBOX are both plugged into the same HUB, static each one. Do not set a gateway for the PC as this will cause havoc with your wifi connection. Example: PC 192.168.0.10 255.255.255.0 XBOX 192.168.0.11 255.255.255.0 192.168.0.10 (Put this as the gateway if you have to put one in) Fire up a command prompt and ping 192.168.0.11 , it should reply.
^ I will try this in a few. Right now, I'm in the middle of dumping Cel Damage... and it's taking forever. EDIT: Works. Thanks.
Not "just" dumping games. I like to port stuff from time to time. That's why I'm so anal about the debugger in Visual Studio not working. Shogun.
