This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
NetWitness Discussions

Windows Legacy Log Collector problem after upgrade to v10.4

Anonymous
Not applicable

‎2014-10-27 10:23 PM

Has anyone had a problem getting the legacy windows collector working after upgrading to v10.4?

 

I've upgraded both the SA Log Collector/Decorder and the Legacy Windows Collector to v10.4 and now I cannot add the Legacy Collector back into the SA console and when attempting to add it to the log collector as a remote collector it won't allow me to do so.

 

The connection attempt fails under the 'services' section.

0 Likes
2 REPLIES 2

Anonymous
Not applicable

‎2014-10-28 02:33 AM

IS the services running ?

Trusted connections will not work for windows legacy service.
You would still have to use admin/netwitness.

0 Likes

Anonymous
Not applicable
In response to Anonymous

‎2014-10-28 04:12 AM

Thanks for the suggestion

 

Services are running on the legacy collector. Using the admin/netwitness as the username and password when adding the service on port 50001 also fails.

 

From the SA Log Collector, and SA Appliance I can telnet to the legacy log collector successfully.

0 Likes
© 2022 RSA Security LLC or its affiliates. All rights reserved.