AnsweredAssumed Answered

Problem adding destination with a Windows Legacy Collector

Question asked by Maximiliano Cittadini on Jun 19, 2019
Latest reply on Jun 24, 2019 by Maximiliano Cittadini

Like • Show 0 Likes0
Comment • 5

Community:

I'm facing an issue trying to add two different WLCs to two different Log Collectors with Netwitness 10.6.6. In both cases when I configure the destination of the collection the GUI throws me the following error:

failed to add destination for "Windows": "HttpOps: GET: SSL connection error: A request to send or recieve data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied"

I have no clue what that error means nor how to solve it.

Any suggestions?

Regards,

Max

No one else has this question

Outcomes

5 Replies

Con O'Donnell Jun 19, 2019 4:06 PM
Mark Correct
Correct Answer
Dell Customer Communication - Confidential

Could be port 50101 is blocked from head unit to WLC, what happens if you curl to the WLC port from the head unit ?

curl :50101
Like • Show 0 Likes0
Actions
- Maximiliano Cittadini @ Con O'Donnell on Jun 19, 2019 4:32 PM
  Mark Correct
  Correct Answer
  Con, thank you so much for your reply! I really appreciate that! Could it be, but... the strange thing here is the last part of the message: "A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied" its exactly the same error message as Winsocket error number 10057 (ref.: https://docs.microsoft.com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2 ) so, it seems to be the windows side trying to connect to something else (I think to the log collector) and the connection is reset or something like that. In other hand, I also tried to create the connection from the Log Collector side, and after the WLC is added it shows an error "shovel error" so it seems to be something in the rabbitmq side of the WLC....
  Any suggestion?
  regards,
  Max
  Like • Show 0 Likes0
  Actions
  - Con O'Donnell @ Maximiliano Cittadini on Jun 19, 2019 5:16 PM
    Mark Correct
    Correct Answer
    Dell Customer Communication - Confidential
    
    Could be, it will be trying to contact the collector on port 5671
    
    Would be useful to get a wireshark is possible from WLC to head unit and WLC to LC
    Like • Show 0 Likes0
    Actions
    - Maximiliano Cittadini @ Con O'Donnell on Jun 20, 2019 6:00 PM
      Mark Correct
      Correct Answer
      Thank you again for your response. I'll try that tomorrow and I will let you know the results.
      Like • Show 0 Likes0
      Actions
Maximiliano Cittadini Jun 24, 2019 12:31 PM
Mark Correct
Correct Answer
Ok, I end up reinstalling both WLCs prior backup of the WLC files.
Like • Show 0 Likes0
Actions

Problem adding destination with a Windows Legacy Collector

Outcomes

Related Content

Recommended Content