RDC Problems

[Scroobius]

I have established a Bluetooth connection between my PC and laptop for RDC of the PC but cannot get RDC to work. Using the IPv4 address shown for the Bluetooth connection RDC will not connect but using the IPv4 ip address for the network connection works OK.

I have run out of ideas just now so if anyone can help I would much appreciate it.

Cheers

Paul

[PeterSt]

Paul, first a small question :

I can't keep track of everything, but did you ask for the Bluetooth driver (by email) ? I don't recall it.
When not, I don't even see how you got the driver installed.

When I'm still on the right track, tell me how you accomplished *that* (only because I couldn't with the standard one).

But maybe I'm on the wrong track !
Peter

[AlainGr]

Hi Paul,

I had a problem too at first, but I finally realized that I forgot to "authorize" connection to my music PC, since I just installed a new OS...

Control Panel > System > Advanced System Parameters > Remote Desktop Connection... Then click on "Authorize..." or something like that on the music PC.

I hope it helps

Alain

[AlainGr]

By the way, the reason why the "titles" of the option are not precise on my part is due to the fact that I have a French version of W8... I should have thought about this...

Alain

[Scroobius]

Peter - yes you did send me W8 bluetooth driver and that is what I installed on the PC. The laptop is windows 7 so I did not install the new driver on the laptop - should I?

Alain thanks - everything seems to be OK in remote connections security setting.

[PeterSt]

Not sure Paul. All I know is that I installed it on the both PC's I use. It's a very different driver you know.

But you don't hear me say it is that ...
I too once couldn't get it going for the life of me. Really.

Btw I am fairly sure that this is the RDC side (as you expected). MANY reasons can exist that this won't go, but I have tweaked so much that none of them is on the top of my head right now ...

Start out with uninstalling all what even smells like Bluetooth. From the newest to the oldest. Then reinstall this driver. Do not put in the dongle when you install, but do have it in when you UNinstall.

[AlainGr]

I have a desktop with W7 as a "general purpose" PC, then the dedicated music PC with W8. What I did at first was to install the 2 PCs with the download that Peter provided me for W8, but finally I reinstalled the previous on the general purpose PC, since I was receiving errors... Like it was indicating that the other PC was not there (but it was still working)...

Alain

[Scroobius]

The answer was to go out to the pub for a quick Sunday beer then come back try again a couple of times then suddenly it starts to work. Weird but seems OK now.

[Scroobius]

Well it lasted until the first reboot - now it does not work again. Not only does the RDC over Bluetooth not work XX software does not work. Specifically when I press play nothing happens XX gets as far as showing the track name that is to be played at the bottom of the XX screen but goes no further. I can get XX working by restoring back to pre Bluetooth install. So there seems to be some interaction between XX and the BT driver software.

[PeterSt]

Paul,

Whatever you do, try it with Attended. You probably are doing just that, but just in case.
I realize that I didn't put attention to processes and services which need to keep running and which will (?) have changed with this driver. I'd also have to notice that I don't use Bluetooth myself, so all I did was finding a driver which works. The combination though is something else.

Otoh, watch out please; I see no relation to the BT driver influencing XXHighEnd.

Then I can add that as far as I have heard at least two other persons have it running with BT, so ...

What is your W8 version ?

I can get XX working by restoring back to pre Bluetooth install. So there seems to be some interaction between XX and the BT driver software.

I believe you, but I would be very careful about the "conclusion" that the Restore helped. Of course it did, but a normal reboot may have helped just the same. So, this is not about not believing you, but about helping you to not make the wrong conclusions.
And FYI or fun or whatever, I think I managed to be in my 500th reboot of combined W7 and W8 before I could understand what was happening to W8 and finally got something running which took me ... well, 500 reboots (over the past weeks).

One tip maybe : put (wlansvc) in your Services to Keep. This *may* help your Bluetooth for after a reboot (this is just a huch). Also, go to Services (the button in TaskManager, not the tab) and set wlansvc to "Auto" instead of "Manual" (when it is at "Manual" at all) . Despite the above tip (Services to Keep) do not go to Minimized and see whether all keeps running, especially after a reboot.
Again, just hunches, but W8 does strange things in this area plus things explicitly have been changed in this same area.

If XXHighEnd doesn't want to play, try to sort out why please. The task seems to be too high for you, but only then we are able to find out the solution. I tell you : it can't be related. Still it may happen, so what's up.
And hey, don't use your remote for testing that "Play" of course !

Sorry I can't be more specific ...
Peter

[manisandher]

I'm having problems installing the Broadcomm driver. It seems to have installed perfectly on my W7 remote PC, but not on the W8 audio PC. I say this because when I check which BT drivers are being used, the remote PC says Broadcomm and the audio PC says Generic Bluetooth Adapter (Microsoft driver).

I've uninstalling all BT drivers from the audio PC and have tried reinstalling the Broadcomm. However, whenever I connect the BT dongle, the Microsoft driver is selected by default. It won't let me change the driver manually because it believes it already has the best driver.

Having said all this, I haven't even tried to make a BT connection - I just can't see how it's going to work. Will try anyway though and report back.

Mani.

[manisandher]

Nah, doesn't work. (Oh and BTW, I used inst.exe and not setup.exe.)

???

Mani.

[PeterSt]

Hi Mani,

Something seems wrong to me in your description;
The driver is an explicit install and it installs. Eh, period ? So I miss this part in your story. I think you don't even need the Dongle to be in.

Quite another things is that it could be so that you can get it to work even without installing the driver, which I described elsewehere (as a painful process which in the end I gave up upon). This leads to you *thinking* that it won't work because you already see the adapter while you actually didn't do a thing, and while at the same time for W7 this would not work (and you didn't see the adapter).

It won't let me change the driver manually because it believes it already has the best driver.

This also looks a bit smelly to me. You wouldn't even be able to point at something when you go this route. Or ?
So again, it is an explicit install (run the .exe I pointed out in the document provided) and it will go.

HTH
Peter

PS: In the mean time ...

Nah, doesn't work. (Oh and BTW, I used inst.exe and not setup.exe.)

So you did that right. But what "doesn't work" ??

[manisandher]

OK, it's my use of the word 'install' that is confusing.

Of course I can run the inst.exe and it 'installs'. Everything is as is should be. The Widdcomm folder is there in Program File(x86), etc. But when I then connect the BT dongle, W8 selects/installs the Microsoft driver and not the Broadcomm driver.

On the W7 remote PC, I did exactly the same, and when I inserted the dongle it said "installing device driver". A few seconds later it said "device is ready to use". In Device Manager it's clear that the Broadcomm driver is indeed being used.

None of the above happens in W8 when the BT dongle is inserted. The BT icon appears in the taskbar instantaneously (using the Microsoft driver).

A question: Might the W7 Shell be interfering in the install in some way?

Mani.

[PeterSt]

The shell won't interfere.

What about looking at it the other way around;
So, I already know it can work without installing any driver (but was a sheer pain for possibly other reasons at the time) and next I (for sure !) never checked whether I was using the MS driver perhaps. For others probably the same.

So ... just try it ?

Please notice that for me it is confusing just the same, because I did/tested/tried a lot of W8 stuff on a machine with the Consumer Preview W8, and after that all changed ...
(read : that sure needed a driver BUT ... now this was the driver we all used for W7 - go figure !).