HI All, I need assistance in understanding the issue as one of our DMZ client is not reporting to DMZ relay using Clientsettings.cfg and shows the below errors:-1:
Client Logs:-1:
RegisterOnce: Attempting secure registration with âhttps://Root FQDN:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.3.211&Body=0&SequenceNumber=0&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Root FQDN%3a52311&AdapterInfo=00-50-56-99-15-5d_30.31.69.0%2f24_IPADDFORDESTINATIONRELAY_0â
At 10:29:24 -0500 -
RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://Root FQDN:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.3.211&Body=0&SequenceNumber=0&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Root FQDN%3a52311&AdapterInfo=00-50-56-99-15-5d_30.31.69.0%2f24_IPADDFORDESTINATIONRELAY_0
At 10:31:29 -0500 -
RegisterOnce: Attempting secure registration with âhttps://Root FQDN:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.3.211&Body=0&SequenceNumber=1&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Root FQDN%3a52311&AdapterInfo=00-50-56-99-15-5d_30.31.69.0%2f24_IPADDFORDESTINATIONRELAY_0â
At 10:31:51 -0500 -
RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://Root FQDN:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.3.211&Body=0&SequenceNumber=1&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Root FQDN%3a52311&AdapterInfo=00-50-56-99-15-5d_30.31.69.0%2f24_IPADDFORDESTINATIONRELAY_0
At 10:33:55 -0500 - Screenshot of portqry from client shows TCP is filtered:â
As per screenshot if TCP is filtered for 52311 at client side then is it be a cause of endpoint not able to perform registration for the first time?
The winsock error means that the client is not able to resolve the parent relay name while registering. In your case it appears to be âRoot FQDNâ. Can you please confirm that âRoot FQDNâ is your DMZ relay ? I canât read the hostname in your âportqryâ command, please make sure the client is capable to resolve and connect to the parent relay on port 52311.
Root FQDN is the root server name and its not a DMZ relay. The hostname in portqry is the DMZ relay server which shows the communication from client via port 52311 is filtered.
Based on the log snippet you posted, it doesnât look like itâs attempting to register with a relay other than the root server? Can you post the clientsettings.cfg file, removing any sensitive information?
The client will initially try to register with the root server, when that fails it should drop back to the relays you set in the clientsettings.cfg. It looks to me like tcp/52311 is being filtered or blocked on the relay? Are you able to open tcp/52311? This should resolve the issue.
I was guessing the same, it seems at client level the TCP is filtered which ma be the cause of this issue. I will check if we can open the port so that communication can be setup. But do you think client should first register to root even if I am placing the clientsettings.cfg file in the installer folder by marking automatic selection to 0 and forcing endpoint to register to a particular relay?
To make it very clear, you should see the attempt to register to the actual DMZ relay in the client log at the very beginning after the client start up. The log that you have posted only shows an attempt to register to the server. My suspicion is that the client is not reading the clientsetting.cfg file. Please restart your BES client and see if it first attempts to register with the DMZ relay. If not then the ârelayâ settings have not been added to the client registry for some reasons. Let me know
