Re: More than a month later, my Xbox 360 still won't connect to my

Tech-Archive recommends: Fix windows errors by optimizing your registry

Gabe: you might also want to try updated drivers for your network card

They are available here.
http://www.realtek.com.tw/downloads/downloads1-3.aspx?lineid=1&famid=4&series=2003072&Software=True

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

"Jenelle Coberly [MSFT]" <jenellec@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:e$R71IwIGHA.3176@xxxxxxxxxxxxxxxxxxxxxxx
> Gabe,
> According to your logs the Media Center PC address has changed since
> your last report to 192.168.1.47. Is this correct?
> If so the Media Center is sending out the UDP/SSDP packets to discover the
> Xbox 360 but is not recieving a reply. Your registry does not show any
> device data which means that it has not seen the Xbox 360 on the network.
> I also saw other traffic coming from other devices on the network.
> (particularly 192.168.1.45) Which acorrding to your previous post is the
> Media Center PC. There are no other devices that show up in the trace.
>
> Please validate the addresses and provide clarity of what is on the
> network when the trace was taken.
> Recommendations:
> If you have a spare PCI network card, please install on the MCE PC,
> disable the Realtek RTL8169/8110 and attempt to connect again.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Gabriel" <Gabriel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:34B72F97-D5C3-4CD0-B8AD-8433AC090CC3@xxxxxxxxxxxxxxxx
>> The information has been sent.
>>
>> "Jenelle Coberly [MSFT]" wrote:
>>
>>> Gabe,
>>> Your reg file was blocked and Trace file was corrupt. The tool that I
>>> directed you to earlier at analogx.com does not appear to be working
>>> correctly. All the traces that we are receiving are un-
>>> readable. Please download and use the NETCAP MS Support Tool to gather
>>> your
>>> trace. I have provided the instructions below.
>>>
>>> Please also export the media center extender specific entries of your
>>> registry, save them as a txt file, and send it in.
>>>
>>> Thanks
>>> Jenelle Coberly
>>>
>>>
>>> NETCAP
>>> 1. Install the Windows XP Service Pack 2 Support Tools from the
>>> following link
>>> http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-
>>> 9761-BA8011FABF38&displaylang=en
>>>
>>> 2. Once installed, open a cmd window and change active directory to the
>>> Support Tools directory
>>> 3. Start the network capture using "netcap.exe". The /n: parameter
>>> specifies
>>> which network interface should be monitored. To discover the network
>>> interfaces on your machine type "netcap /?" The interfaces will be
>>> listed at
>>> the end to the executables help details.
>>>
>>> Example: C:\Program Files\ Support Tools>netcap /n:1
>>>
>>> 4. Conduct the steps to repro the problem you are seeing. Once complete
>>> return back to the command window and hit the space bar.
>>> 5. Send the file created
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "Gabriel" <Gabriel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:E1B9074B-62DB-405A-8A0C-AF59897A542C@xxxxxxxxxxxxxxxx
>>> > My information is sent.
>>> >
>>> > I apologize for the delay.
>>> >
>>> > "Jenelle Coberly [MSFT]" wrote:
>>> >
>>> >> This is very strange. Looks like we will have to really dig into to
>>> >> discover
>>> >> this issue.
>>> >>
>>> >> Can you please both get a network trace and provide the export the
>>> >> media
>>> >> center extender specific entries of your registry. Please send both
>>> >> of
>>> >> these
>>> >> to
>>> >> msft_mcx at hotmail
>>> >>
>>> >> Instructions for sending a network capture are as follows:
>>> >> 1) download and install
>>> >> http://www.analogx.com/contents/download/network/pmon.htm (freeware)
>>> >> on
>>> >> your
>>> >> Media Center PC that's experiencing the problem
>>> >> 2) go to the Windows desktop, Start menu, Programs, AnalogX,
>>> >> PacketMon
>>> >> folder and start the "PacketMon" program
>>> >> 3) press the "Start" button in the upper-right corner of PacketMon
>>> >> 4) go through the setup on the Media Center and Xbo 360 to reproduce
>>> >> the
>>> >> problem
>>> >> 6) on the Media Center PC, press the "Stop" button on PacketMon
>>> >> 7) go to the "File" menu of PacketMon and "Save As..." to a CSV file
>>> >> on
>>> >> your
>>> >> machine
>>> >> 8) send the CSV file
>>> >>
>>> >> Please complete the following to export the Media Center Extender
>>> >> registry
>>> >> keys
>>> >>
>>> >> 1. Run regedit
>>> >> 2. Navigate to
>>> >> HKEY_Local_Machine\software\Microsoft\MediaCenterPeripheral
>>> >> 3. Right click on MediaCenterPeripheral and select Export.
>>> >> 4. Save the file type as Txt.
>>> >>
>>> >> Thank You
>>> >>
>>> >> --
>>> >> This posting is provided "AS IS" with no warranties, and confers no
>>> >> rights.
>>> >>
>>> >> "Aryn" <Aryn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> >> news:5FACA5FB-6EBA-4613-B98C-58C6DC466ABF@xxxxxxxxxxxxxxxx
>>> >> > I'm having the exact same problem as described... in the setup I
>>> >> > see
>>> >> > that it's saying 'Verifying Setup Key...' for a few seconds, then
>>> >> > goes
>>> >> > to the 'Xbox 360 Not Found' screen. Xbox live and Media Connect
>>> >> > work
>>> >> > just fine... not Media Center...
>>> >> >
>>> >> > Setup:
>>> >> > Windows Media Center edition w/ Rollup 2
>>> >> > .NET 1.1 w/ SP1
>>> >> > D-Link 624 Router (with live certified firmware)
>>> >> > NO firewalls are enabled (or have ever been installed)
>>> >> >
>>> >> > The following is a snippet from c:\windows\DvcConn.log
>>> >> >
>>> >> > ---cut---
>>> >> >
>>> >> > 7:46:09 PM : Searching device table for unaffiliated bobsleds.
>>> >> >
>>> >> > 7:46:09 PM : Found 1 matching device(s).
>>> >> >
>>> >> > 7:46:09 PM : Found a device matching the security code. DVCID =
>>> >> > {00000000-0000-0000-0200-00125A3B1AC9}
>>> >> >
>>> >> > 7:46:10 PM : Sanity Check : Making sure device is not already
>>> >> > affiliated with this PC.
>>> >> >
>>> >> > 7:46:10 PM : Starting affiliation.
>>> >> >
>>> >> > ***********************************************************
>>> >> > ERROR
>>> >> > ***********************************************************
>>> >> > Timed out waiting for affiliation status.
>>> >> >
>>> >> > 7:46:54 PM : Cancel confirmed by user.
>>> >> >
>>> >> > 7:46:54 PM : Resetting the device table entry to a clean state.
>>> >> >
>>> >> > 7:46:54 PM : Turning off the InOOBE flag.
>>> >> >
>>> >> > 7:46:54 PM : Exiting
>>> >> >
>>> >> > ---cut---
>>> >> >
>>> >> > I can also verify that both the SSDP Discovery Service and
>>> >> > the Universal Plug and Play Device Host service are running.
>>> >> >
>>> >> > I've been attempting to get this thing to work since launch. Any
>>> >> > ideas?
>>> >> >
>>> >> >
>>> >> > "Gabriel" wrote:
>>> >> >
>>> >> >> The services.msc list is sent.
>>> >> >>
>>> >> >> I reviewed my eventvwr and didn't see anything out of the
>>> >> >> ordinary.
>>> >> >> Should
>>> >> >> I be looking for a specific log?
>>> >> >>
>>> >> >> "Jenelle Coberly [MSFT]" wrote:
>>> >> >>
>>> >> >> > Gabriel,
>>> >> >> > Please run services.msc once more and export the list of
>>> >> >> > services
>>> >> >> > currently running on your Media Center PC
>>> >> >> >
>>> >> >> > To export complete the following:
>>> >> >> > - right click on services and select "Export List..."
>>> >> >> > - save as a tab delimited text file
>>> >> >> >
>>> >> >> > email this text file to msft_mcx at hotmail for review
>>> >> >> >
>>> >> >> > Please also review your eventvwr messages logged at the time of
>>> >> >> > install
>>> >> >> > and
>>> >> >> > report any messages you recieved.
>>> >> >> >
>>> >> >> > Thanks
>>> >> >> >
>>> >> >> > --
>>> >> >> > This posting is provided "AS IS" with no warranties, and confers
>>> >> >> > no
>>> >> >> > rights.
>>> >> >> >
>>> >> >> > "Gabriel" <Gabriel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> >> >> > news:2BB86C2F-7D85-4F54-81B7-3A6E7F857AE7@xxxxxxxxxxxxxxxx
>>> >> >> > >I turned the Windows Firewall off completely during the
>>> >> >> > >attempts.
>>> >> >> > >
>>> >> >> > > "Jenelle Coberly [MSFT]" wrote:
>>> >> >> > >
>>> >> >> > >> Gabriel,
>>> >> >> > >>
>>> >> >> > >> Please review the Windows Firewall settings and see if the
>>> >> >> > >> option
>>> >> >> > >> to
>>> >> >> > >> "Don't
>>> >> >> > >> allow exceptions" is currently enabled. If this is enabled
>>> >> >> > >> please
>>> >> >> > >> disable
>>> >> >> > >> and attempt setup again.
>>> >> >> > >>
>>> >> >> > >> --
>>> >> >> > >> This posting is provided "AS IS" with no warranties, and
>>> >> >> > >> confers
>>> >> >> > >> no
>>> >> >> > >> rights.
>>> >> >> > >>
>>> >> >> > >>
>>> >> >> > >> "Gabriel" <Gabriel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>> >> >> > >> message
>>> >> >> > >> news:7AA5460F-E7AD-4F41-9765-FF4E23D07799@xxxxxxxxxxxxxxxx
>>> >> >> > >> >- I only use Windows Firewall
>>> >> >> > >> > - My only antivirus is NOD32, and I was not able to connect
>>> >> >> > >> > with
>>> >> >> > >> > NOD32
>>> >> >> > >> > uninstalled.
>>> >> >> > >> > - I do not have other third-party privacy, security center,
>>> >> >> > >> > or
>>> >> >> > >> > intrusion
>>> >> >> > >> > detection installed.
>>> >> >> > >> > - I do not have an Nvidia motherboard chipset.
>>> >> >> > >> > - SSDP and UPnP services are running.
>>> >> >> > >> >
>>> >> >> > >> > Connecting my Xbox 360 directly to my MCE PC and following
>>> >> >> > >> > your
>>> >> >> > >> > directions
>>> >> >> > >> > did not work.
>>> >> >> > >> >
>>> >> >> > >> > Contents of the new DvcConn.log:
>>> >> >> > >> >
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > Wednesday, 11 January 2006 12:12:53
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > 12:12:53 PM : CmdLine: DvcConn launched from DvcSetup.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Checking OS version.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Checking MCE version.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : MCE version = Emerald.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Checking only instance of installer.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : CmdLine: Connection Wizard.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : CmdLine: Security code passed in via cmdline:
>>> >> >> > >> > 8332-6080
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : CmdLine: Skin = Xenon.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : CmdLine: Skipping Pre-Run Checks.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Verifying user is Administrator.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Verifying EULA is present.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:53 PM : Verifying MCE is NOT installed on a dynamic
>>> >> >> > >> > disk.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:54 PM : Start conditions met.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:54 PM : Searching device table for unaffiliated
>>> >> >> > >> > bobsleds.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:54 PM : Found 1 matching device(s).
>>> >> >> > >> >
>>> >> >> > >> > 12:12:54 PM : Found a device matching the security code.
>>> >> >> > >> > DVCID
>>> >> >> > >> > =
>>> >> >> > >> > {00000000-0000-0000-0200-00125A4AA3C9}
>>> >> >> > >> >
>>> >> >> > >> > 12:12:55 PM : Sanity Check : Making sure device is not
>>> >> >> > >> > already
>>> >> >> > >> > affiliated
>>> >> >> > >> > with this PC.
>>> >> >> > >> >
>>> >> >> > >> > 12:12:56 PM : Starting affiliation.
>>> >> >> > >> >
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > ERROR
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > Timed out waiting for affiliation status.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:49 PM : Resetting the device table entry to a clean
>>> >> >> > >> > state.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:49 PM : Clearing the device ID.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:49 PM : Clearing the security code.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:51 PM : Verifying security codes.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:51 PM : Security Code: 8332-6080
>>> >> >> > >> >
>>> >> >> > >> > 12:13:51 PM : Searching device table for unaffiliated
>>> >> >> > >> > bobsleds.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:51 PM : Found 1 matching device(s).
>>> >> >> > >> >
>>> >> >> > >> > 12:13:51 PM : Found a device matching the security code.
>>> >> >> > >> > DVCID
>>> >> >> > >> > =
>>> >> >> > >> > {00000000-0000-0000-0200-00125A4AA3C9}
>>> >> >> > >> >
>>> >> >> > >> > 12:13:52 PM : Sanity Check : Making sure device is not
>>> >> >> > >> > already
>>> >> >> > >> > affiliated
>>> >> >> > >> > with this PC.
>>> >> >> > >> >
>>> >> >> > >> > 12:13:52 PM : Starting affiliation.
>>> >> >> > >> >
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > ERROR
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > Timed out waiting for affiliation status.
>>> >> >> > >> >
>>> >> >> > >> > 12:15:28 PM : Cancel confirmed by user.
>>> >> >> > >> >
>>> >> >> > >> > 12:15:28 PM : Resetting the device table entry to a clean
>>> >> >> > >> > state.
>>> >> >> > >> >
>>> >> >> > >> > 12:15:28 PM : Turning off the InOOBE flag.
>>> >> >> > >> >
>>> >> >> > >> > 12:15:28 PM : Exiting
>>> >> >> > >> >
>>> >> >> > >> > Contents of the new DvcSetup.log:
>>> >> >> > >> >
>>> >> >> > >> > ***********************************************************
>>> >> >> > >> > Wednesday, 11 January 2006 12:10:53
>
>


.

Quantcast