Rick Coughenour wrote: > Specifically, the problem occurs because of the way that SAS has > designed communications to occur between ports. This is orchestrated by > the broker.exe on your web server. Your app server is configured to > 'listen' on port 5001. That is the only port exclusively 'hard-coded' > in the entire process. The broker randomly selects the outgoing port > from the web server (say, port 6931) upon a client request, and passes > info on to the application server instructing the app server to respond > back via a random outgoing port (not the incoming port, 5001) and to > direct the return communication to port 6930 (n-1 from the outgoing web > server port) of the web server. > > If you want to discuss this matter further, contact me at: > rcoughenour@highmark.com > > Rick Coughenour

Rick,

SI solved this same problem with respect to SAS/CONNECT by including the FIRSTPORT and LASTPORT options when starting up a SAS/CONNECT server session. These options limit the range of port numbers from which SAS will choose when selecting a random unassigned port for SAS/CONNECT communications with the client. If you make FIRSTPORT and LASTPORT the same, you restrict SAS to just a single port. Strange that they didn't forsee the same problem with the broker.

Tim Churches