[sdeviller]

Hi all,

I manage a BES server, v4.1.6.9. We have 13 users/devices connected. All but two of them are on Verizon Wireless. The other two are on Sprint, and have nothing but problems. One of them I cannot get activated, and the other just stopped working.

I cannot activate these devices via cable, because they are remote users in the US, and my server is at the head office her in Ottawa, Ontario, Canada.

Is anyone else having issues with sprint.

I have setup many, many BB, on many servers, and never had this much trouble.

Thank you,
Steve

[DarthBBerry]

Sprint/Nextel is famous for disconnecting their customers... at least in my area. They usually blame "the provisioning network" for the problems. I've been told it could take anywhere from 4 mintues, to 4 hours, to 4 days for a BB to get provisioned correctly.

Try calling Sprint T-Support back. Tell them you want the services removed and readded to the device. Then tell them to push the standard service books one by one. It should get it to the point where you can activate them OTA again.

[DBConz]

I have 90+ users on BES. about 4-5 Sprint, 1 on AT&T, and 85 on Nextel. Never had any issues activating with various carriers. Are there any policies in place that may be restricting them? how about IP issues, since you mentioned different locations/domain servers/subnets.

Sounds more like a BES or network config problem, and not a phone provider issue.

[knottyrope]

I have issues with most of the carriers.

Problem is newb at carrier just clicks on what they think you need and you end up with problems until you find someone that cares.

[DarthBBerry]

Originally Posted by knottyrope

I have issues with most of the carriers.

Problem is newb at carrier just clicks on what they think you need and you end up with problems until you find someone that cares.

N00Bs need to be pwn'd, ganked and teabagged so we can take their phat lewts! That would be l337!!!!1!!

[sdeviller]

Our BES setup is really generic, I have not added any policies.

I just got one working, had the user VPN to the office, and open his DM. the activation completed now. I will know shortly if it continues to work when he unplugs it.

Steve

[knottyrope]

Originally Posted by DarthBBerry

N00Bs need to be pwn'd, ganked and teabagged so we can take their phat lewts! That would be l337!!!!1!!

Too bad we will never see that happen.

[sdeviller]

Is there any test I can run on the BB to see if it can contact my server? Can I open a browser on the BB and browse to a website at the same address, will this verify anything?

Steve

[knottyrope]

If you have T support, BlackBerry Expert Support Center can see if a device is provisioned correctly


BlackBerryForums.com : Your Number One BlackBerry Community

[sdeviller]

I don's think our problems are due to provisioning. This has all been checked many many times. The one BB is now activated, but had to do in through the DM, would not activate wireless. The other BB just stopped working out of the blue. I cannot touch it from my server. The user is going to plug it into his desktop and use the DM tomorrow.

It is very strange that we only have problems with Sprint. When they try to activate, it just will not find our server over wireless. Once activated, seems ok.

I was thinking of a possible DNS issue with Sprint, or something along those lines.

Steve

[cruwl]

I may be wrong here but from my understanding doesnt the OTA EA email sent to your users mailbox come from RIM, and not the spicific carrier?

If my understanding is correct it wouldnt be a DNS issue with sprint.
If RIM can find your company for your other users nothing should be stopping it for your sprint users as long as sprint's network was passing the info to RIM's network.