• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Error message when adding IP adress

Schrikbeest

New Pleskian
A Plesk 17.5 (2012r2) server gives back the following error when adding an additional ip:

Error: ifmng failed: Execute netsh interface ipv4 add address NIC1 xx.xxx.xx.xxx 255.255.255.240 failed[1]: The object already exists. at (execExtUtilChecked line 137) at Unable to add IP address(IFmng::IPManager::addIP line 286) at execute console command --add(vconsoleapp::start line 122) at execute C:\Odin\Plesk\admin\bin\ifmng --add "\"NIC1\"" xx.xxx.xx.xxx 255.255.255.240(vconsoleapp::run line 139) (Error code 1)

The ip was initially added under a wrong subnet mask so we deleted the ip and re-adding under the right subnetmask but it gave back the error.

I also pressed the "reread ip" button but no luck.
It's presumable that the ip adres lives somewhere in the server but we cannot find it. We tried to manually remove it via netsh command:
C:\Windows\system32>netsh interface ipv4 add address NIC1 xx.xxx.xx.xxx 255.255.
255.240
The object already exists.

Trying to remove it gives back:
C:\Windows\system32>netsh interface ipv4 add address NIC1 xx.xxx.xx.xxx 255.255.
255.240
The object already exists.

I looked into the registry but no luck on finding it somewhere, trying to add it via the GUI of the NIC doesnt work either.

We already rebooted the server.
 
Issue has been resolved due to the fact that the network size was a /28 network and the last one wouldnt fit in the range.
 
Back
Top