KB: Networking errors (23801, 23753) when a virtual machine is assigned a static IPv4 address through System Center 2012 R2 Virtual Machine Manager

KB: Networking errors (23801, 23753) when a virtual machine is assigned a static IPv4 address through System Center 2012 R2 Virtual Machine Manager

  • Comments 6
  • Likes

 When you use System Center 2012 R2 Virtual Machine Manager to migrate a virtual machine, the job is completed successfully but one or both of the following errors are returned in the job result information:

Error (23801)
No available connection to selected VM Network can be found.
Recommended Action
Ensure host NICs have connection to the fabric network on which VM Network is created.

Error (23753)
The virtual machine or tier load balancer configuration requires an IP pool and there are no appropriate IP pools accessible from the host.
Recommended Action
Select a host with access to an appropriate IP pool and try the operation again.

This issue occurs if the virtual machine’s virtual network adapter is connected to a virtual machine network that does not have a static IP address pool defined for it. Additionally, the IPv4 address type was changed from dynamic to static by going inside the virtual machine and manually changing the IP address configuration.

For all the details and a resolution, please see the following:

KB2915463 - Networking errors (23801, 23753) when a virtual machine is assigned a static IPv4 address through System Center 2012 R2 Virtual Machine Manager (http://support.microsoft.com/kb/2915463)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • установить сертификат

  • установить сертификат

  • The solution mentioned in the KB to ignore or set a static IP pool is not really a solution. A lot of customers have an exisitng environment to manage, very often with third party IP mgmt. Please add an option to turn off the ip pool verification.

  • I agree with Stefan. This is not acceptable solution to not use VMM or ignore message. it is a bug and it must be fixed. obviously there should be third IPaddress type which said Static not managed by VMM so no requirement for IP pool.

  • I concur, My environment has static IP addresses that are managed manually and not by VMM as these IP address ranges stretch across both virtual and physical systems. This error has resulted some migration issues or tasks being unable to start because of the warning and for no reason. This should be fixed.