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.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Can't add DHCP Sensor - The device needs a static IP

Votes:

0

Your Vote:

Up

Down

Hi everyone,

I facing this issue, I can't add DHCP Sensor. I'm getting this message that the device needs a static IP, but my server is configured with static IP.

I'm using PRTG latest version and the DHCP Server is a Windows Server 2012 virtualized on Hyper-V Core Server.

dhcp-sensor prtg wmi

Created on Feb 18, 2016 1:19:06 PM by  ReynaldoST (0) 1



9 Replies

Votes:

0

Your Vote:

Up

Down

Hi Reynaldo,

Did you make sure the static IP is configured directly in the network interface of the Probe running the sensor (not like "static" in the sense of "gets always same IP by DHCP")?

Kind regards.

Created on Feb 19, 2016 3:26:15 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Erhard

Thank you for your reply. Yes my server is configured with static IP directly in the network.

I don't know if this is a relevant information, but both server (PRTG and DHCP) are virtual machines. I double check and both server are configured with static IP.

Best regards.

Created on Feb 19, 2016 5:54:19 PM by  ReynaldoST (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Reynaldo,

  • Do you get this error when adding the sensor or later (after first scan)?
  • Could you please post the output of ipconfig /all from the Probe running the sensor (=PRTG Core Server or Remote Probe if applicable)?
  • Does the Probe-VM run on the same Hyper-V host as the DHCP-VM?
  • How many virtual switches are assigned to the Probe-VM?

You can also write us an email with those details, if you like ([email protected]). Make sure to mention this KB post in your email and put (Case PAE660046) in the subject (our internal Ticket-ID for this post).

Kind regards.

Created on Feb 22, 2016 8:28:52 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Erhard,

I'm getting this error when I try to add the sensor. PRTG don't let me add for first scan.

ipconfig /all from PRTG Server: Windows IP Configuration

Host Name: BR-PRTG

Primary Dns Suffix: br.undp.local

Node Type: Hybrid

IP Routing Enabled: No

WINS Proxy Enabled: No

DNS Suffix Search List: br.undp.local

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix:

Description : Microsoft Hyper-V Network Adapter #2

Physical Address: 00-15-5D-78-10-06

DHCP Enabled: No

Autoconfiguration Enabled: Yes

IPv4 Address: 172.16.120.4(Preferred)

Subnet Mask: 255.255.254.0

Default Gateway: 172.16.120.1

DNS Servers: 172.16.120.5, 172.16.120.6

NetBIOS over Tcpip: Enabled

----------------

ipconfig /all DHCP Server: Windows IP Configuration

Host Name: BR-NAP

Primary Dns Suffix: br.undp.local

Node Type: Hybrid

IP Routing Enabled: No

WINS Proxy Enabled: No

DNS Suffix Search List: br.undp.local

Ethernet adapter Ethernet:

Connection-specific DNS Suffix:

Description: Microsoft Hyper-V Network Adapter

Physical Address: 00-15-5D-78-CB-10

DHCP Enabled: No

Autoconfiguration Enabled: Yes

IPv4 Address: 172.16.120.13(Preferred)

Subnet Mask: 255.255.254.0

Default Gateway: 172.16.120.1

DNS Servers: 172.16.120.5, 172.16.120.6

NetBIOS over Tcpip: Enabled

---------------------

Probe-VM and DHCP-VM are running from different servers and there is only one Virtual Switch

Best regards, Reynaldo

Created on Feb 22, 2016 3:18:18 PM by  ReynaldoST (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Reynaldo,

I also received your email, I talk to one of the developers about this and get back to you (by email) as soon as I know more.

Kind regards.

Created on Feb 23, 2016 7:45:15 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi

Did this get resolved? I'm getting the same error and have a static assigned to probe machine.

Created on May 13, 2016 1:36:13 AM by  cat007 (0)



Votes:

0

Your Vote:

Up

Down

Are you trying to add the DHCP sensor to a device on your probe or the probe itself? The sensor only works directly on probe devices. That turned out to be the problem :)

Created on May 13, 2016 9:13:44 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,

i'm facing the same issue within same platform, same outputs as Reynaldo did. Could you give me some idea how to fix it ?

Created on Dec 18, 2017 7:07:43 AM by  melihk (0)



Votes:

0

Your Vote:

Up

Down

More than one active network card (HyperV, Docker, etc.) on the target server that is a DHCP server?


Kind regards,
Stephan Linke, Tech Support Team

Created on Dec 18, 2017 7:35:16 AM by  Stephan Linke [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.