Kbase P142579: Getting errors 10060, 1432 and 1451 when trying to connect remote client outside the firewall to a O
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/03/2009 |
|
Status: Unverified
SYMPTOM(s):
Getting errors 10060, 1432 and 1451 when trying to connect remote client outside the firewall to a Oracle database
** Could not connect to server for database sports, errno 10060. (1432)
Failed to connect to ORACLE database . (1451)
FACT(s) (Environment):
The port 1025, 1026 and the range of ports from 1029 to 1050 are listed on the services file on the DataServer machine
Oracle Database and the Oracle DataServer are on UNIX and inside the firewall
_probrkr is running on port 1029 on the Oracle DataServer machine
Firewall has port range 1029 to 1050 opened to both inbound and outbound
UNIX
OpenEdge 10.x
Progress 9.x
Progress 8.x
Oracle DataServer
CAUSE:
On UNIX, the default minport for the _probrkr is 1025. Since the port 1025 and 1026 are listed on the services file, _probrkr skips those two ports, and use port 1027 to spawn _orasrv. On the other hand, firewall only has the port range 1029 to 1050 open to both inbound and outbound. Therefore, the port 1027 is being blocked on the firewall.
FIX:
In order to avoid the port used by the _probrkr, list ports 1027 and 1028 in to the services file so all the ports from 1025 to 1029 are listed on the services file. Then comment out all the ports ranges from 1030 to 1050 from it. _probrkr does not use any ports that are listed on the services file to spawn _orasrv DataServer process. However, the port 1029 needs to be listed on the services file as _probrkr itself runs on that port. _probrkr requires service name instead of the port number when command to run the broker is submitted.