Print

[Bomb Bloke]

Hmm. 50% packet loss is not good. Typically means some bit of hardware is busted. Presumably you pinged in each of those five scenarios you listed and got that result with each?

If so, it certainly looks like an issue with the console's NIC. You might try taking an earwax cleaner to it... I wouldn't expect that to work, but you might get lucky.

[Heimdall]

Just use your original xboxhdm disc to unlock the 500GB disk (or use Configmagic to unlock it on Xbox 2), then use a new xboxhdm disc with the Xbox 1 eeprom to relock it to Xbox 1.

[Bomb Bloke]

I can't think of any reason why this would indicate a problem with the HDD.

What speed is your computer's NIC? What speeds is the router capable of?

[Heimdall]

Packet loss can often be caused by autonegotiation failing and creating a duplex mismatch, which can be caused by a whole pile of things, including a poor quality cable, electrical noise, etc. It can also be caused by the NIC on the Xbox and the NIC on your PC being at opposite ends of the allowable tolerance for Ethernet physical layer performance. So, it's not DHCP that's fixing the problem, its the fact that you are no longer connecting the PC to the Xbox via a crossover cable, but connecting them both to the NIC chip in the router using different cables.

You could check this. With the Xbox connected directly to your computer (your original setup) check the duplex status of the Xbox and the PC. However, that might be inconclusive - I'm not absolutely sure that the Xbox NIC reports its duplex status to the UnleashX dashboard, and don't currently have any way of checking (I don't have a power lead for my 10 Mbit/s switch!). Even if it does turn out to be a duplex mismatch, there's not much you can do about it. You could force the settings on your PC to match those on your Xbox, but your best solution is to keep them attached via your router.

[Heimdall]

QUOTE(marcozd @ May 5 2009, 02:56 PM)

Why all of a sudden would this be happening?

Difficult to tell. Maybe the NIC on the Xbox has started to fail, and drifted out of tolerance?

QUOTE

Also, how do I check the duplex status of my computer?  I am using Windows Vista Home Premium Edition.

I don't think you can - I was confusing Windows with Linux! Apparently some NIC chip utilities give you this information in Windows, but not all. Probably not worth pursuing if you have another Xbox to try.

QUOTE

If I take the HDD out of the not working xbox and then install it in a different xbox that I know is working, will that fix the problem?

It might. You'd have to unlock it, then relock it with the eeprom of the new Xbox. You might have to change the kernel version in the softmod to match the destination Xbox kernel before doing the unlock and swap.

QUOTE

And if I have the same problem can I assume that it is a software issue and not the xbox itself?

It's unlikely to be a software issue because changing the network connection fixes the problem. I'd do the swap first, rather than trying to second guess the cause of one of the possible outcomes.

[Heimdall]

With Krayzie you don't need to. With Kingroach you run System - NDURE Toolset - Fonts Menu, then select your kernel version - or select Generic if you don't know your kernel version. Obviously, before you do anything, make sure you have backups of the eeproms from both Xboxes on your PC, in case something goes wrong.

[marcozd]

I am now sure it has to be the software.

I unlocked drive in the not working xbox, re-locked it with the eeprom from an xbox that I know I can ftp into via static IP.

I started it up, tried to FTP with static settings and I am getting the same problems - time out errors and 25 %- 75 % packet loss via a cross over cable.

BUT when I hook it up to my router it works fine - I can ftp in no problem.

How is this possible?

Am I just going to have to get myself a cheap, wired router and have it sit next to my xbox if I need to transfer files to it?

[Heimdall]

Maybe it's the NIC on your PC?

The easiest way to tell if it's the software is to put a clean copy of UnleashX into a temporary directory, boot with Frosty's rescue disc (to load a different BIOS), then use the file manager to run your temporary copy of UnleashX. If it works then the problem is your current software, if it doesn't then it's your hardware - the Xbox, the PC, or the cable, or some horrible interaction between the three.

[marcozd]

QUOTE(Heimdall @ May 6 2009, 12:12 AM)

Maybe it's the NIC on your PC?

The easiest way to tell if it's the software is to put a clean copy of UnleashX into a temporary directory, boot with Frosty's rescue disc (to load a different BIOS), then use the file manager to run your temporary copy of UnleashX. If it works then the problem is your current software, if it doesn't then it's your hardware - the Xbox, the PC, or the cable, or some horrible interaction between the three.

Hey.

It turned out that it was the software for some reason.  I copied a fresh version of XBMC into a temporary directory on E by hooking my xbox up to the router and using DHCP settings.

Then used Frosty's Rescue disc, went to the file manager and started up my fresh XBMC.  I set it to static IP address and BAM! worked like a charm.  

So my final fix was to completely remove my old XBMC directory and copy over a fresh version.  I think it is because I use XBMC as my default dash and I was running the unleashX dashboard as a program after booting into XBMC that unleashX ftp was also not working.

Go figure.  I am up now and I just wanted to say a HUGE thankls to Heimdall and Bomb Bloke for all of their help.

Cheers!