(Bluetooth & MS Stack) Unable to set outgoing port

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › (Bluetooth & MS Stack) Unable to set outgoing port

neo_tech

4 posts

Wannabe Geek

Topic # 5635 13-Nov-2005 16:10

Hello,
i am facing a peculiar problem. my bluetooth dongle is easily detected by windows xp sp2 and then it installs it nicely. i then add a device through bluetooth devices and it detects my Nokia 6630...we exchange passkeys and my phone is paired. now the problem is that the PC is only able to recieve and NOT send files to my Nokia 6630. whenever i try to send a file to the mobile it says that the Bluetooth device did not respond and some OBEX need to be present there. when i try to add an outgoing port then it is unable to find my device(though the incoming port is easily installed)...this is ridiculous...i mean it is able to receive files from my nokia but not send to it.
most annoying thing is that when i installed my device this morning for the 1st time it worked nicely both send and receive but when i booted my computer in evening and then tried to send a file this probem started to surface :-(. am really very saad at this. i have seacrhed a LOT on google but without any luck. i know theres some minor config. problem but what is it...pls guys help me out.
my nokias bluetooth settings r set out perfectly...show device, bluetooth on etc etc.

Thanks

freitasm

BDFL - Memuneh
58764 posts

Uber Geek
+1 received by user: 10162

Administrator

Trusted

Geekzone

Subscriber

Reply # 23150 14-Nov-2005 10:25

You don't need an outgoing port to send files. Bluetooth uses "profiles", services that are specialised. In this case the phone probably does not support the OBEX File Exchange profile.

Not much you can do about it. It may be a restriction from the manufacturer to prevent file copying, implement digital rights, etc.

You will only need to set a new port to this device if you want to use a program that requires a serial connection to it. Then you have to create a serial port. Bluetooth File Transfer will not use this port though - only other programs.

Geekzone broadband switch | Amazon (Geekzone aff) | MightyApe (Geekzone aff) | Backblaze cloud backup (personal and business) | My technology disclosure

neo_tech

4 posts

Wannabe Geek

Reply # 23186 14-Nov-2005 17:43

my mobile is nokia 6630..and it does support the obex profile....the proof- it was working perfectly for so many days...but now when i did some windows updates and booted it stopped working...so it did work nicely with the default microsoft bluetooth stack. tell me 1 thing does OBEX profile has something to do with .NET Framework? coz my norton utilities shows that many dll files of .net r missing. that might be the cause of this annoying problem.

freitasm

BDFL - Memuneh
58764 posts

Uber Geek
+1 received by user: 10162

Administrator

Trusted

Geekzone

Subscriber

Reply # 23187 14-Nov-2005 17:54

Nothing to do with it. Are you running any firewall on your PC? They don't usually work well with Bluetooth and some other programs...

But since you say you're missing some .DLL and other files for some unrelated software, I can't stop thinking that perhaps your PC is completely messed up - time for a rebuild?

Geekzone broadband switch | Amazon (Geekzone aff) | MightyApe (Geekzone aff) | Backblaze cloud backup (personal and business) | My technology disclosure

neo_tech

4 posts

Wannabe Geek

Reply # 23190 14-Nov-2005 18:30

ya same thinking here...presently am trying to repair .net framework....what annoys me the most is that everything working so fine and suddenly a total collapse of the bluetooth system...i mean this raelly pisses me off! :S

anyways i'll keep u updated with my progress

neo_tech

4 posts

Wannabe Geek

Reply # 23278 15-Nov-2005 16:21

hi m8,
just solved the issue ;). it was .NET framework that had some missing .dll files. corrected them and re-installed bluetooth microsft stack drivers(default) and all is again UP and working again :).
to all those who r facing the probem of installing OBEX profile...i suggest them to check there .NET framework dlls. they might be malfunctioning. just give it a thorough check.

bye