Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
11-03-2012 05:00 PM - edited 11-03-2012 05:03 PM
I'm sure you're right. Just gonna take some experimentation to track it down.
Here is the thread I posted that has some screen shots that may or may not help you. I am using an N router. I too had flaky connections but managed to fix them. See if you can replicate any of the settings I used.
Also, it could be something as simple as interference on the particular channel your router is using. Try switching the router channel.
11-03-2012 05:53 PM
Many thanks for that, I'll read it properly and give it a go tomorrow. Eyes going a bit square at the moment.
OK, good luck. I'll check in tomorrow to see if you have any luck.
11-05-2012 04:45 AM
sorry I didn't get back with an update yesterday. Minor crisis to deal with. Managed to get some testing done last night though - with some interesting results.
First off, I looked carefully at my wlan configuration.
Like I said, oldish router, G only, nothing on adjacent channels, no ability to do qos etc and no ability to change or bond channel widths. About the only thing that could (conceivably) have any impact is the ability to run in "mixed mode" i.e have both b and g supported. I set that to "G Only"
Checked the playbook config. Not a lot to do there really, and started transferring files.
Interesting (although a little tedious )
I used a 1.65 GB avi - must get 'round to handbraking that !
Sometimes it copied across ok !
Sometimes I got an error saying the connection was interrupted.
Sometimes I got an error saying that the file could not be read or written to. This particular message was written in such a way as to indicate that the mac DIDN'T KNOW if the problem was reading the file or writing the file ! Very telling.
No pattern at all that I could identify.
Really suspicious now......
I ran the ftp server on my mac and using ESfileexplorer on the pb copied the file several times without failure !
I think the first thing I'd like to say is that my conclusion is only based on what I've seen in MY setup i.e equipment and environment.
I think broadly what is happening is that networking under smb is not awfully robust and that what I'm seeing is basically a timing problem. My evidence is backed up by my own experience of seeing things like this before.
The giveaway for me is that the error(s) thrown on the mac is/are sufficient to say that it doesn't really know what the heck happened. It efectively is saying "I don't know what happened, I'll throw an error. Which error shall I throw ? Oh that one will do"
For me, the killer evidence is that I never had a failure using ftp.
Thanks to those you who came through with suggestions and made me think
For mac users out there who would occasionally like to take a deeper look at their wireless environment. Take a look in /System/Library/CoreServices and drag "WiFi Diagnostics" to your desktop. You can just run it where it is if you'd like.
One of these days, I'll get an "n" router, I'm confident the problem will go away (or change) Like I said I'm talking about MY environment and setup. In the meantime I'll make a choice between smb and ftp by intuition.
11-05-2012 05:27 AM
If you go for N then you need to go for WPA2 AES encryption, Playbook is very fussy with N in that they actually followed the rules and many routers don't!
I find that Mac is more robust than Windoze any day. Not many people have problems just establishing a connection with MAc as opposed to countless problems with Windoze. However I do find sometimes that Finder will not allow copy and paste were it will allow drag and drop, and may not establish a connection with wifi occasionally until I reboot Mac and playbook. Permissions in Samba are not so robust.
But once you've had Mac you never go back.
11-05-2012 05:35 AM
Hi there, thanks I'll take heed of that.
With particular regard to smb on the mac - Apple changed the implementation in Mountain Lion (Samba 3) and broke a lot of little things in the process (Sigh)
"Once you've had a Mac, you never go back"
Oh, you're **bleep** right.
Thanks and Regards