Same issue on this end. Linksys Wireless G, with Adapter. I've successfully
installed WMC. The Xbox shows up in WMC. However, when I go to access it from
the XBOX the XBOX cannot find the PC.
I've tried hours of combinations and checked that all services are in fact
running that are required. Judging from the number of posts and problems on
this issue there is some kind of definitive problem that isn't being
mentioned.
Can we start to zero in on why this doesn't work in some scenarios?
Regards
In order to work, the XBox and the computer must be on the same sub-net.
It could be that the wireless network is one sub-net and the wired
network is another.
Look at the IP address and Subnet Mask for both the xbox and the PC.
When you do a logical "AND" of the IP address and subnet mask and
compare the results, if they are the same then the two ip addresses are
on the same subnet. if not, then WMC isn't going to be able to
communicate.
Here are two IP addresses on the same subnet
192.168.0.1 255.255.255.0
192.168.0.101 255.255.255.0
When you do a byte-wise and of the IP and the subnet mask both are on
the 192.168.0.0 subnet.
Here are two IP address that are not on the same subnet
192.169.0.1 255.255.255.0
192.168.1.1 255.255.255.0
The first on is on the 192.168.0.0 subnet, and the other is on the
192.168.1.0 subnet.
Now, if the subnet mask was 255.255.254.0 then they would both be on the
same subnet
Hope that helps,

Signature
Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no
rights.
ryan - 30 Nov 2005 06:51 GMT
i checked that and both xbox and pc are on the same subnet...
192.168.1.100 - xbox
192.168.1.101 - PC
both on 255.255.255.0 subnet mask.... any other ideas?? turned off all
possiable programs that can block ports on my PC and still no luck...
> In order to work, the XBox and the computer must be on the same sub-net.
> It could be that the wireless network is one sub-net and the wired
[quoted text clipped - 26 lines]
>
> Hope that helps,
Dave - 30 Nov 2005 11:42 GMT
I have the exact same thing going on:
PC IP: 192.168.1.101
Xbox: 192.168.1.102
Subnet Mask: 255.25.255.0 for both
In Windows Media COnnect it shows the XBOX360 as being conencted, but my
xbox cannot find my PC :(
Any ideas guys? I've reset my firewall settings on media connect, also put
in WEP access codes, and opened up ports on firewall.
> i checked that and both xbox and pc are on the same subnet...
>
[quoted text clipped - 33 lines]
> >
> > Hope that helps,
Alan Ludwig [MSFT] - 01 Dec 2005 03:00 GMT
Have you checked out the README and FAQ
http://www.microsoft.com/windows/windowsmedia/devices/wmconnect/readme.aspx
http://www.microsoft.com/windows/windowsmedia/devices/wmconnect/faq.aspx
There is some good stuff in there on troubleshooting network issues.
Regards,

Signature
Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
ryan - 01 Dec 2005 04:36 GMT
no luck there either.. there has to be a problem with either the program or
the xbox since this is happening on more than one user...
> Have you checked out the README and FAQ
>
[quoted text clipped - 4 lines]
>
> Regards,
Alan Ludwig [MSFT] - 01 Dec 2005 18:49 GMT
Not necessarily. I've seen similar problems with discovery with
outdated router firmware. I've seen similar problems with routers that
had to have UPnP Enabled in order for the SSDP packets to be propperly
forwarded. I've seen simlar problems with 3rd party "security" tools
that lock-out UPnP Functionality in unexpcted ways. I've seen similar
problems because users have changed the configuration of UPnP Services.
And of course some of the problmes I'm sure I mistakenly put in there
myself. And I'll keep working on all of these problems no matter what
the cause.
In this case, the error is REGDB_E_CLASSNOTREG. So basically during the
function call to create the UPnP Device it is trying to create a COM
object that isn't registered.
The next step for you would be to use REGMON to try and determine what
COM object it is trying to create that it can't find. If you post the
GUID back to the newsgroup I can use that to look up the COM object and
figure out what DLL needs to be registered.
I remember seeing a similar issue in v1 where it was atl.dll that wasn't
registered propperly. You might try "regsvr32 c:\windows\system32
\atl.dll" and "regsvr32 c:\windows\system32\atl71.dll". If that fixes
the problem good. Otherwise you'll have to find the GUID using REGMON
or some other tool.
Regards,

Signature
Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no
rights.
ryan - 02 Dec 2005 06:11 GMT
Hey Alan...
thanks for you help... looks like the firmware was the issue...kept on
thinking it had to do with the PC since the PC can see the xbox.. but guess
you gotta look at everything...
> Not necessarily. I've seen similar problems with discovery with
> outdated router firmware. I've seen similar problems with routers that
[quoted text clipped - 23 lines]
>
> Regards,