Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Knowledge Partner
Knowledge Partner
929 views

Blackberry 10 not connecting to Mobility pack

A new install that was working fine for the first two devices, but then
they both stopped working (partially due to the GroupWise server
overheating after a failed fan and plugged filters, now fixed)

We have one Q10 that connects just fine, but the other two units tried
so far get the following when we try to reconnect them.
"Your device is connected to a network,
but the internet service is not available.
Check your network settings."

The default.pipeline1.mobility-AppInterface.log shows just three
entries per attempt, and they really don't say anything to me (detailed
below).
A packet capture shows no actual content, just the TCP cycle of SYN,
SYN ACK, ACK, FIN ACK, ACK

The only thing we've done none default is that we are using port 88 and
using PAT to get it to the mobility server where as the rest of that
public IP goes to the GroupWise server. No encryption turned on yet.



Mobility:/var/log/datasync/connectors # tail -f
default.pipeline1.mobility-AppInterface.log |grep Device
2013-05-23 14:17:23.605 INFO [Device_Thread-24] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 60: Total: 15 ,Idle
Threads: 15.
2013-05-23 14:17:23.674 INFO [Device_Thread-23] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 60: Total: 15 ,Idle
Threads: 15.
2013-05-23 14:17:23.764 INFO [Device_Thread-11] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 60: Total: 15 ,Idle
Threads: 15.
2013-05-23 15:19:49.817 INFO [Device_Thread-25] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 43: Total: 15 ,Idle
Threads: 15.
2013-05-23 15:19:50.118 INFO [Device_Thread-22] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 43: Total: 15 ,Idle
Threads: 15.
2013-05-23 15:19:50.343 INFO [Device_Thread-12] [__init__:1314]
[userID:] [eventID:] [objectID:] [WSRThread] Socket 43: Total: 15 ,Idle
Threads: 15.



-rw-r--r-- 1 root root 10493952 May 6 15:34
novell-data-synchronizer-mobility-pack-1.2.5-x86_64-299.iso
mobility:/ISO/Datasync # rpm -qa | grep mobil
datasynchronizer-mobilitypack-release-cd-1.2.5-1.2
datasynchronizer-mobilitypack-release-1.2.5-1.2
datasync-syncengine-connector-mobility-1.2.5.4417-1.1
mobility:/ISO/Datasync # cat /opt/novell/datasync/version
1.2.5.299
mobility:/ISO/Datasync # cat /etc/*release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x
86_64:core-3.2-x86_64:core-4.0-x86_64"

dual core, 4GB RAM, 180GB drive with over 170GB freee



Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
Labels (1)
0 Likes
3 Replies
justen Absent Member.
Absent Member.

Re: Blackberry 10 not connecting to Mobility pack

It's possible that different versions of BlackBerry 10 might handle things differently, but my Z10 gave the same error until SSL was enabled with a non-self-signed certificate on the Data Synchronizer server. It now connects and syncs fine.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Blackberry 10 not connecting to Mobility pack

In article <VA.00000538.0180f502@no-mx.forums.novell.com>, Andy Konecny
wrote:
> The default.pipeline1.mobility-AppInterface.log shows just three
> entries per attempt, and they really don't say anything to me (detailed
> below).
> A packet capture shows no actual content, just the TCP cycle of SYN,
> SYN ACK, ACK, FIN ACK, ACK
>

This happening with multiple Z10 running version 10.1.0.273
And this has applied to several different ports used, including port 80.
So it really looks from available data that there is a problem with this
version of the OS on the Z10 and that is where I will take my trouble
shooting.



Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Knowledge Partner
Knowledge Partner

Re: Blackberry 10 not connecting to Mobility pack

In article <justen.5w57hz@no-mx.forums.novell.com>, Justen wrote:
> It's possible that different versions of BlackBerry 10 might handle
> things differently, but my Z10 gave the same error until SSL was enabled
> with a non-self-signed certificate on the Data Synchronizer server. It
> now connects and syncs fine.
>

That is what I am thinking.
Now that I've allocated an IP to this vs port translation, I do still get
the error on port 80, so next will be to get a cert set to get this client
going.


Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.