未解決
この投稿は5年以上前のものです
40 メッセージ
0
1156
Proxy経由のCECT実行
ESRS GW ClientをProxyなしの直接接続からProxyを経由した接続に変更するため
CECTで環境チェックとおこないましたがTCPのチェックがすべてFailとなりますが
HTTPSの通信はPassしており、また、FailするTCP項目を実行しているタイミングで
CECTからProxyへパケットがでていないとプロキシの管理者からは言われております。
この状態でProxy環境への移行は可能なのでしょうか？
CECTバージョン : 2.2.8.008
Failする項目：
TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 DRM core service via TCP. STATUS : Failed
TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 client provisioning service via TCP. STATUS : Failed
TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 Access Server via TCP (443). STATUS : Failed
TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 Access Server via TCP (8443). STATUS : Failed
CECTの設定で、SRS Proxy Configurationsの項目は有効にして、Proxy設定を指定済み
CECTログ抜粋：
| 2017/04/04 12:21:49 | TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 DRM core service via TCP. STATUS : Failed |
2017/04/04 12:21:49
| 2017/04/04 12:21:49 | ************************************************************************************ |
| 2017/04/04 12:21:49 | Test Notes : Test EMC SRS DRM client listening service Test Failed. |
| 2017/04/04 12:21:49 | Test Notes : Failed socket connection to address esrs-core.emc.com on port= 443 |
| 2017/04/04 12:21:49 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 128.221.192.14:443 |
| 2017/04/04 12:21:49 | Test Notes : Test EMC SRS DRM 3.0 client listening service Test Failed. |
| 2017/04/04 12:21:49 | Test Notes : Failed socket connection to address esrs3-core.emc.com on port= 443 |
| 2017/04/04 12:21:49 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 128.221.236.246:443 |
| 2017/04/04 12:21:49 | Test Notes : Test EMC SRS DRM client listening DR service Test Failed. |
| 2017/04/04 12:21:49 | Test Notes : Failed socket connection to address esrs-coredr.emc.com on port= 443 |
| 2017/04/04 12:21:49 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:21:49 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 168.159.218.21:443 |
| 2017/04/04 12:23:26 | ************************************************************************************ |
：
| 2017/04/04 12:24:38 | TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 client provisioning service via TCP. STATUS : Failed |
2017/04/04 12:24:38
| 2017/04/04 12:24:38 | ************************************************************************************ |
| 2017/04/04 12:24:38 | Test Notes : Test EMC SRS Client Provisioning service network connection Test Failed. |
| 2017/04/04 12:24:38 | Test Notes : Failed socket connection to address esrs.emc.com on port= 443 |
| 2017/04/04 12:24:38 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 128.221.192.13:443 |
| 2017/04/04 12:24:38 | Test Notes : Test EMC SRS Client Provisioning service 3.0 network connection Test Failed. |
| 2017/04/04 12:24:38 | Test Notes : Failed socket connection to address esrs3.emc.com on port= 443 |
| 2017/04/04 12:24:38 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 128.221.236.245:443 |
| 2017/04/04 12:24:38 | Test Notes : Test EMC SRS Client Provisioning DR service network connection Test Failed. |
| 2017/04/04 12:24:38 | Test Notes : Failed socket connection to address esrs-dr.emc.com on port= 443 |
| 2017/04/04 12:24:38 | Test Notes : Host application is either not running or port is currently in use. |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly respond after a period of ti |
| 2017/04/04 12:24:38 | Test Notes : Error Msg : me, or established connection failed because connected host has failed to respond 168.159.218.20:443 |
| 2017/04/04 12:24:39 | ************************************************************************************ |
：
：
| 2017/04/04 12:43:27 | TEST NAME : EMC SRS Enterprise Connect Test of ESRS 2.0 Access Server via TCP (8443). STATUS : Failed |
2017/04/04 12:43:27
| 2017/04/04 12:43:27 | ************************************************************************************ | |||||||||||||||||||||||||
| 2017/04/04 12:43:27 | Test Notes : Test Westboro SRS Global Remote Access Server esrgweprd01.emc.com Test Failed. | |||||||||||||||||||||||||
| 2017/04/04 12:43:27 | Test Notes : Failed socket connection to address esrgweprd01.emc.com on port= 8443 | |||||||||||||||||||||||||
| 2017/04/04 12:43:27 | Test Notes : Host application is either not running or port is currently in use. | |||||||||||||||||||||||||
| 2017/04/04 12:43:27 | Test Notes : Error Msg : connection attempt failed because the connected party did not properly res ：
2017/04/04 13:02:15
|
Mineo1
12 メッセージ
0
2017年4月4日 19:00
はい、プロキシ経由の場合はCECT TCPテストは無効ですので、
HTTPSテストの結果だけをチェックする形になると思います。
なお、プロキシ経由のHTTPSテストでは443ポートだけしかテストされないと思います（8443ポートはテストされない）。
8443ポートはリモートアクセスの際に使用されますので、移行後にリモートアクセスに何か問題など出るようでしたら、
プロキシやファイアウォールでポート8443の設定の再確認をおすすめします。