Hello,

i have installed PRTG 12.3.4.2994 on a Windows 7 machine (VM on ESXi Host). Configured a DHCP Sensor on the Probe Device, but the sensor doesn't work. Error: Could not open UDP Port 68. Please make sure this port is not in use. (code: PE091)

But my DHCP server is working correctly in my network and there a enough IP's free.

On both machines (PRTG and DHCP server) the firewall is off. i played with the timeout setting is 10, 20 and 200 seconds, but no luck.

deleted the sensor and added a new with the correct network interface of the PRTG server, no luck.

regards


Article Comments

Hello,

the error means that PRTG cannot use the DHCP port on the machine it is running on to send out a DHCP-request. Please check with netstat what other application is blocking the port.

best regards.


Oct, 2012 - Permalink

Hi,

on the PRTG server no entry found for Port UDP 68. On the DHCP server UDP 68 is showing his own server IP.

On the PRTG server I have 2 network interface configured as packet sniffer interfaces.

is this a problem? netstat showes me not a entry for the udp 68 port on these both NIC's

only these:

UDP 169.254.80.159:137 *:*

UDP 169.254.80.159:138 *:*

UDP 169.254.80.159:1900 *:*

UDP 169.254.80.159:56373 *:*

UDP 169.254.213.199:137 *:*

UDP 169.254.213.199:138 *:*

UDP 169.254.213.199:1900 *:*

UDP 169.254.213.199:56372 *:*

regards


Oct, 2012 - Permalink

Does restarting the PRTG Probe Service help then?


Oct, 2012 - Permalink

Not really, after restarting the Probe Service i have now the error: No data yet. trying repeatedly "check now" but no luck.


Oct, 2012 - Permalink

Now is have the same error message: Error: Could not open UDP Port 68. Please make sure this port is not in use. (code: PE091)


Oct, 2012 - Permalink

The error means that PRTG cannot listen on UDP port 68 (on the machine where PRTG is installed), maybe this is blocked by the firewall or similar. In anyway, if PRTG cannot listen on this port, it can't use the DHCP-Sensor. This needs to be possible.


Oct, 2012 - Permalink

The Firewall is off. there is no other security software installed , like a Antivirus or Internet Security Suite. When i check with wireshark and filter the result with (bootp.option.type == 53) i can't see any package no DHCP Discover, Offer, Request, ....

any idea?


Nov, 2012 - Permalink

Hi Paessler, we have the same problem here. DHCP Sensors throw the UDP Port error periodically on all our (3) probes. Netstat does not show any service blocking port 68. Any insights on your side?

Regards

Matin Schiemann


May, 2014 - Permalink

Hello, which exact version of PRTG are you running? How long does the error on the sensors persist? Does it resolve itself, or do you need to add the sensor(s) anew? Or maybe restart the Probe Service?


May, 2014 - Permalink

Hi Paessler, sorry for the delayed answer. We do still experience this problem periodically on all our 4 probes with DHCP sensors. We are running prtg latest stable. All probes are win 7 with no firewall or other blocking software. netstat shows the connection to our prtg core server only.

The problem occurs about 5-10 times a day on each of our probes. The dhcp sensors check server ip and resultstring. Interval is 5 minutes.

Would you like me to open a support issue? Our license is 1000 sensors.

Kind regards

Matin Schiemann


Jul, 2014 - Permalink

How many DHCP - Sensors do you have per Probe Device?


Jul, 2014 - Permalink

We have one DHCP sensor per probe device.


Aug, 2014 - Permalink

We only have one DHCP sensor per probe device.


Aug, 2014 - Permalink

I'm afraid such sporadic errors are very hard to catch and may not be caught here. Please try working around the issue, with using latencies on potential triggers, that allow for at least another scan after the error.


Aug, 2014 - Permalink