IP Conflict Detected

L Series. Error: IP Conflict Detected


If you are using terminals that are not compatible with vSpace Pro 11 or Enterprise edition, likely, these are outdated and need to be upgraded.  
You can see our new line of products and consult your sales representative or authorized partner about updating your product.
Also, "Classic Versions" like vSpace 6 will be permanently discontinued after June 30th, 2020.  
Please upgrade promptly to our latest platform  vSpace Pro. 

If you need technical support to guide you on your upgrade, you can contact us here. 

Legacy L Series device displays "IP address conflict detected" on the screen when it is powered on.
Applies to L230 and older devices. 

The cause of the issue is that a L-device or other device, such as a printer, on the network fails to synchronize with the Microsoft DHCP server and it continues to use the IP address assigned originally by the DHCP server. The DHCP server later could assign the same IP address to a different L-device. Once the second device receives the IP address, it displays "IP address conflict detected" on the screen and the user can't connect to a host. The first device does not display any error message. This only happens if the DHCP server is a Windows server.

Solution

  1. The best solution is to enable address conflict detection in the DHCP server and restart the server or the DHCP service. Detailed Microsoft instructions on how to "Enable address conflict detection" can be found at http://technet.microsoft.com/en-us/library/cc737924.aspx (the content is not available from the Microsoft website) 
  2. One temporary solution is to find and delete the DHCP lease for the second device and then manually power cycle the device.
  3. Another temporary solution to assign a static unused IP address to the second device. Click "Options" and then "Setup", enter the static IP address in the "Network" tab.

Article #KB017

Last Edited: May 21, 2020

    • Related Articles

    • VERDE User Side Error Codes

      Product Line:  VERDE If we talk about the VERDE VDI client mode then we need to distinguish between two types of communication: User authentication and enumeration of VERDE VDI desktops. Terminal connections to VERDE VDI desktops.   The RX-series GUI ...

    • L Series: Error: "Terminal server yet not ready, please retry attempt a bit later"

      If you use a L Series Legacy Device (L100, L110, L120, or L200) device, these are outdated, need to be upgraded and because of their age may have little or no support available.  Models L130 and L230 are more recent legacy products and will connect ...

    • L-series Legacy: Device cannot get IP address from DHCP

      If you are using terminals that are not compatible with vSpace Pro 11 or Enterprise edition, likely, these are outdated and need to be upgraded.   You can see our new line of products and consult your sales representative or authorized partner about ...

    • Error > can't establish connection to server connection ended unexpectedly

      Using vSpace Pro on a Client Operating system, if you receive the error can't establish connection to server You likely have installed vSpace without Properly Elevated Permissions if you view Windows System Event logs using Event Viewer (command ...

    • NetAPP IP Dupe Detection – Lost Network Shares when using NAT Networking

      Product Line:  VERDE   When the guest use NAT networking all CIFS connections in NAT mode come from the same IP, we suspect that NetApp starts disconnecting certain connections once newer connections come in.  According to the following article, this ...