What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Help - Error Could not bind socket. Address and port are already in use.

Votes:

0

Your Vote:

Up

Down

Router interface is pingable from monitoring server, tried rebooting monitoring server based on recommendation from separate thread. Still get same error Have other instances of netflow running on PRTG server, but for some reason when I try to monitor this router get the Address and port are already in use error

Router config seems ok. Remote router is a Managed router through an ISP. They added the netflow config to their router...

PNTEAS01#sh ip flow export
Flow export v5 is enabled for main cache
  Export source and destination details :
  VRF ID : Default
    Source(1)       192.168.209.1 (FastEthernet0/0.1)
    Destination(1)  192.168.254.213 (2055)
  Version 5 flow records
  550205 flows exported in 18344 udp datagrams
  0 flows failed due to lack of export packet
  0 export packets were sent up to process level
  0 export packets were dropped due to no fib
  0 export packets were dropped due to adjacency issues
  0 export packets were dropped due to fragmentation failures
  0 export packets were dropped due to encapsulation fixup failures

What are some of the other reasons that could cause this error? remote router config error? or is is something to do with the local monitoring server?

configuration netflow prtg

Created on Jan 11, 2012 7:58:17 PM by  ESUCP_ITS (0) 1

Last change on Jan 12, 2012 1:58:50 PM by  Torsten Lindner [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Hello,

"Error Could not bind socket. Address and port are already in use." refers to the host on which the Probe runs, so the Probe is not able to bind address/port, (usually because another application is blocking, or a firewall not allowing).

best regards.

Created on Jan 12, 2012 2:09:11 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.