Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
New Contributor
jcosta123456
Posts: 6
Registered: ‎07-14-2013
My Device: Z10
My Carrier: Verizon

UDS Connectivity Issues on BES 10.1.1

I am having itermitent issues with UDS and iOS secure workspace on my BES 10.1.1 server. Most seem connectivty related.

 

Here's a quick list:

- IP connections required are more that what's listed in your KB341893. For instance, activation stopped working out of the blue because the BES all of a sudden was steered to an address within the 208.65.72.0/21 space...

http://btsc.webapps.blackberry.com/btsc/viewdocument.do;jsessionid=554B35CE24E90B452A486AB62FBA1388?...

 

-bbsecure.com (suddenly) does not resolve to anything but MX records..... No A records, no CN records..

r>nslookup
> bbsecure.com
Name:    bbsecure.com

 

> set type=mx
> bbsecure.com
Non-authoritative answer:
bbsecure.com    MX preference = 15, mail exchanger = mx06.rim.net
bbsecure.com    MX preference = 15, mail exchanger = mx07.rim.net

mx06.rim.net    internet address = 208.65.78.57

 

Please advise. I got the BDS piece of things running rather easily, but the UDS stuff is another story. Kind of makes me wonder how reliable it will be...

 

Thanks,

Jack

 

Please use plain text.
Contributor
lineassupport
Posts: 44
Registered: ‎06-26-2013
My Device: 8700
My Carrier: Germany

Re: UDS Connectivity Issues on BES 10.1.1

Hello,

can you simply telnet all the host with the ports?

like
telnet uk.swstps.bbsecure.com 443
or
telnet uk.uk.bbsecure.com 443
as an example.
Please use plain text.
New Contributor
jcosta123456
Posts: 6
Registered: ‎07-14-2013
My Device: Z10
My Carrier: Verizon

Re: UDS Connectivity Issues on BES 10.1.1

Thanks for the reply.

 

Actually, I had locked down my firewall to allow outbound access to only the ranges/ports defined in the BE10.1 documentation. The problem is that there seem to be IPs at play that are not in that documentation. For now, I have allowed the BES10 server out to all IPs on TCP 80, 443, and 3101 which seems to help, but that's less than ideal long term.

 

 

Please use plain text.