[WINDOWS] Specify specific Network Adapter to use

Well guys, here is where it gets strange. On my other PC, browsing the network in XBMC works perfectly. After seeing that I thought someone had fixed it. So that's when I started playing with it on my HTPC, which can't browse the network. I guess it just works with some adapters and not others.

That is very strange. Run wireshark concurrently and see if anything gets transmitted and returned from the network.

okay.

kraqh3d Wrote:I've not tried using SMB on the Win32 build, but I have seen reports here that it doesn't work right. There seem to be various problems. On Win32, the ultimate goal should be to use the OS to browse the workgroup, and not Xbmc's samba client. Until then, you're probably better off using drive mappings or mount points to make the remote locations look like local ones.

It works quite well if you don't want to browse for shares (smb://). Windows still uses the old smbclient code from xbox because switching to a newer version would imply some effort to get all changes done to compile and run it on Windows.
I started with a light implementation of using windows functionality (see WIN32Util.cpp) but give up after discussion with the team that we should use the same code for all ports where possible.
What I was thinking off was the same functionality as Linux had/has before the HAL manager was introduced. Once you have the smb sources saved in your xml the user can decide via a setting to mount those shares when XBMC starts or to use smbclient for every connect.

This is probably a moot point, but I just wanted to update since kraqh3d asked me to run wireshark.
Well. I installed wireshark on the devPC that could browse for shares in XBMC. I ran wireshark then XBMC. I did this to have a baseline for what to expect on the HTPC which could not browse for shares. Now that devPC can no longer browse for Shares. I have removed wireshark and still can no longer browse for shares. I did test before installing wireshark and I could definately browse for shares. At least it appeard to be. I could hit browse, then see the workgroup, then see my HTPC (but not the devPC) and could connect to it.

Ugh. While I agree its nice to have consistency between the platforms, it seems silly to not to use Win32's native API for browsing in Windows. Whatever. As long it works

I did a system restore and can browse the network again. Just so you guys know I am not crazy here is a video of it.
http://www.danielpatton.com/kricker/down...browse.mov

kraqh3d Wrote:Ugh. While I agree its nice to have consistency between the platforms, it seems silly to not to use Win32's native API for browsing in Windows. Whatever. As long it works

feel free to implement something