xboxscene.org forums

OG Xbox Forums => Xbox Online Gaming (Xbox Live, Xlink, and others) => Xbox Live - Online Gaming Service => Topic started by: gerzand on November 16, 2004, 10:15:00 PM

Title: Communication Error...
Post by: gerzand on November 16, 2004, 10:15:00 PM

Make sure the eeprom was from the same version as ur xbox. Wrong regions and stuff can cause those errors. It happened to me a few months back

Title: Communication Error...
Post by: prplehz on November 16, 2004, 10:35:00 PM

I am haveing the same problem with a banned box. I installed a new hd new eeprom an d locked the drive installed fresh MS install with slayers 2.6. and it says it cannot connect? WTF I thought that was supposed to work.. this sucks... I am starting to think they blocked my modems Ip address...

Title: Communication Error...
Post by: stan on November 17, 2004, 05:39:00 PM

Are  you still unable to connect?

I can't seem to get mine to work no matter what I try.  Does this sound like a messed up eeprom load maybe?  Did I screw up or have I just been banned?  I've heard talk that a "Cannot Connect" message implies bannishment, but I get a different message.  What gives?

Title: Communication Error...
Post by: stan on November 17, 2004, 06:28:00 PM

Now I'm really confused.  I reloaded my old eeprom and am still getting this communication error message.  

Title: Communication Error...
Post by: prplehz on November 17, 2004, 07:42:00 PM

It sounds like the router is stoping it.


Try going through just the modem.. and if that dont work fill in the mac address that your isp is looking for in your xbox net settings.  This is usualy the mac address of the first device that was hooked up to the modem I think, or even the modem itself if that dont work. If if connects you know the router is stopping it. Then just set up a static ip on the xbox and  tell the router to allow your xbox static ip that you asign and you should be good to go..

Title: Communication Error...
Post by: airviper127 on November 17, 2004, 10:06:00 PM

hey i was playing on live the day Halo 2 came out and the next day i got an error just like the one you are describing.  i never touched any thing and i know that my family didn't touch it so i would have to say that we are banned because i lost XBL with the same error but i changed nothing. im 90% sure of this.

Title: Communication Error...
Post by: sicrecords on November 18, 2004, 01:02:00 AM

That is .. unless we can confirm that they are scanning LPC ports.. in which case you're screwed right?

Title: Communication Error...
Post by: prplehz on November 18, 2004, 09:43:00 AM

True, but I dont think they are. I have never seen my chip lights do anything strange since I have been using it. And it would be very noticeable if the chip changed modes since it lights up my entire xbox.  Lets keep fingers crossed because if they are scanning lpc then we are all screwed. unless we come up with an lpc switch.

Title: Communication Error...
Post by: SoloTSi97 on November 24, 2004, 08:16:00 PM

QUOTE (stan @ Nov 18 2004, 02:42 AM)

Are  you still unable to connect? I can't seem to get mine to work no matter what I try.  Does this sound like a messed up eeprom load maybe?  Did I screw up or have I just been banned?  I've heard talk that a "Cannot Connect" message implies bannishment, but I get a different message.  What gives?

Where did you hear/read about this banishment thing?  What do they banish, your IP address?  Your MAC address?  Something else?

To avoid being banned (I haven't yet gotten the dash update that is causing all the problems) ... I bought a new EEPROM and stuck in a never-before-seen-by-Live OEM hard drive.  Got it all set up, and now it is unable to connect (gets all the way to the last step in the troubleshooter, "Xbox Live not Found") to XBL.

My XYZ codes do not indicate that I've been banned (yet) ... and I don't think I should be.  Yes, I used this EEPROM on XBL before with a different hard drive, but that was over a year ago and the consensus appears to be that they didn't start to track the EEPROM/HDD thing until more recently than that.  Besides, if this one gets banned, I have a brand new never-seen-XBL EEPROM and another OEM hard drive I can try.

In any case, I'm curious to hear more about this banishment thing.  Back in January, I had this same thing happen to another Xbox of mine.  It couldn't connect to XBL, but could FTP to/from it all day long.  I ended up selling it to a buddy who didn't need XBL and bought a new one.  I really don't wanna have to explain to my wife why I have to do that again. ;-)

-Solo