Hi, check these posts out, they are both relevant and may shed some light on the issue you are having.
I think this may actually be the solution you are looking for...
Thank you for the information. I've read over these posts before as well. I am still having trouble getting the server to send the netflow data. It seems like it collects data for a while then stops, and the data it collects is in kbps whereas before it was in mbps and there was a lot more of it. I have had a successful iteration of nProbe running on a machine with Windows 7 OS, is the nprobe configuration different when installing on windows server? Just to clarify, I am using the spanned port (we'll call it port 1) as the -u to receive data and then the secondary port (we'll call it port 2) as the -Q to send the egress data? Thanks for your help
1 of 1 people found this helpful
Is it NTA not processing data or the Win 2003 nProbe installation not sending flows? Can you verify with Wireshark if you are receiving flows on the NTA server?
If flows from nProbe are reaching the server, you could try without the -b option (which is for limited logging). I have read multiple threads about the below configuration working well:
nprobe /i -i 1 -n 192.168.1.1:2055 -u 1 -Q 1 (will re-install the service and send all the data from interface 1 (-i 1) to IP 192.168.1.1 on port 2055 with all traffic tagged as coming from interface index 1. Make sure the interface specified is monitored with NPM)