In ignorance I installed BES on a server that did not have ESM installed on it hoping I could point it toward my ESM server. Obviously, this did not work so uninstalled and then reinstalled on the box that did have ESM on it. I pointed the SQL path toward another box and the install went fine.

Except, the SRP Status reports as disconnected. We have not received our new phones yet so I have not had a chance to test the server with a mobile device yet. But I would like the peace of mind of knowing that it is working before we get the new phones.

I have my server behind a SonicWall which is configured properly to allow bi-directional traffic through port 3101. The wierd thing is, is that when I run, netstat -n | find "3101", it returns no results as though the BES service is not even listening on that port.

Event view reports:

Event Type: Warning
Event Source: BlackBerry Dispatcher SERVER NAME
Event Category: None
Event ID: 20000
Date: 6/26/2008
Time: 12:43:04 PM
User: N/A
Computer: SERVER NAME
Description:
[SRP] Connection failed

Event Type: Warning
Event Source: BlackBerry Dispatcher SERVER NAME
Event Category: None
Event ID: 20000
Date: 6/26/2008
Time: 12:43:04 PM
User: N/A
Computer: SERVER NAME
Description:
SRPClient::Connect: Error calling host "localhost" [127.0.0.1] (0)

I receive these error messages over and over.

I would greatly appreciate any help I could get.

Thanks

I think you set up the firewall "backwards".
BES doesn't listen on port 3101... it initiates an outbound connection to the Internet (SRP) on port 3101.

You need to configure your Sonicwall to allow BES to talk to the Internet (LAN-->WAN) on TCP Port 3101.

You don't need to do any port forwarding for this.

How is that any different from forwarding the port to my server?

Also, why does netstat report that the server is not listening on port 3101?

It's entirely different... and you're talking about two different things.

Port Forwarding is used for inbound traffic from the Internet to your Servers.... such as hosting a Web Server or Mail server on your LAN. (WAN ---> LAN)
This is NOT how BES functions.

BES operates like any desktop computer would. It initates an outbound connection (over TCP 3101) from your LAN out to the Internet. (LAN ---> WAN) There's no port forwarding involved.

Because it's NOT listening. It does the talking.
Please read my original reply again.

I apologize if that came off as an attack as it was meant only as a very curious question.

So how exactly should my SonicWall be configured?

Because it is not...all you need is outbound TCP port 3101. Forwarding to your server is an inbound connection 3101 and it is not needed. You just make another door into your network and you don't need it.

You need to set up an access rule that basically says:

ALLOW TCP 3101 FROM LAN {bes ip address} to WAN {any}

Whomever manages your Sonicwall should be able to set this up in a few seconds.

ah-hah! I got it... thanks.

You guys are amazing!