You May Get an Error "Verify that the Source Server Name is Correct" While Trying to Install SBS into an Existing Domain

You May Get an Error "Verify that the Source Server Name is Correct" While Trying to Install SBS into an Existing Domain

  • Comments 7
  • Likes

[Today's post comes to us courtesy of Rod White and Damian Leibaschoff from Commercial Technical Support]

When migrating to Small Business Server 2011 standard you may receive the following error message.

Cannot find the Source Server
Verify that the Source Server name is correct, and then try again.



The problem is usually due to a timing issue. The network card is provisioned with DNS servers right before a ping of the source server name is attempted. In some cases, the network card is not yet ready to handle this. When this happens, an exception will happen and the error will be displayed.


The first thing you should do is acknowledge the error by pressing OK and then wait at least 30 seconds before clicking Next to proceed again.  If you receive the same error a second time, then it is most likely NOT the issue described in this article and further troubleshooting would be required to understand why the new server is failing to ping the source server.

To confirm you are experiencing this issue you can check the SBS Setup log by doing the following steps: 

  1. 1. Press <Shift + F10> to open a command prompt.
  2. 2. Run notepad “C:\Program Files\Windows Small Business Server\Logs\SBSSetup.log”
  3. Look for the following exception stack trace:

Setup: Pinging old server name.
Setup: InvalidOperationException while pinging: System.Net.NetworkInformation.PingException: An exception occurred during a Ping request. ---> System.Net.Sockets.SocketException: The requested name is valid, but no data of the requested type was found
  at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
  at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
  at System.Net.NetworkInformation.Ping.Send(String hostNameOrAddress, Int32 timeout, Byte[] buffer, PingOptions options)
  --- End of inner exception stack trace ---
  at System.Net.NetworkInformation.Ping.Send(String hostNameOrAddress, Int32 timeout, Byte[] buffer, PingOptions options)
  at System.Net.NetworkInformation.Ping.Send(String hostNameOrAddress)
  at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MigrationInformationPagePresenter.ValidateServerName(Boolean runCostlyValidation)

If you are not seeing this exception and still getting the same error, verify that you can resolve the name of the source server properly:

  1. Select <Shift + F10> to open a command prompt.
  2. Ping the Source Server Netbios name (i.e. SBS2003).
  3. Ping the Source Server internal FQDN (i.e. SBS2003.R2.local).

Note: Make sure you have not misspelled the name of the source server or internal domain.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I just ran into this over the weekend. Following advice I found on Susan Bradley's blog (SBS Diva), I hit Shift-F10, typed explorer.exe, then navigated to the Control Panel and set the correct time on the server. Problem solved.

    Also, another problem that can come up at this same stage, make sure that Netbios is Enabled on the source servers network adapter.

  • I just wanted to take a moment and let you know how helpful that your advice has been. Your site is full of fantastic information. Thank you very much and keep up the good work!

    Regular reader, first time commenter...

    Thomas Francois

    Marketing Director

    Web Price Right

  • I can't get past this error.   I can ping the IP address of the source SBS server, no problem.  I can ping the FQDN of the source SBS server, but not the Netbios name.   I have enabled Netbios on the source server adaptor.  I have created a static WINS and static DNS entry for the Netbios of the source server on the source server.  On the source server I can successfully ping itself by Netbios name.  I have rebooted both servers several times, clear DNS cache, registered DNS.  I have verified time, date and timezone are equal on both servers.  No luck.  What a headache.

  • I finally got it.

    Go to command prompt, fire up explorer.exe, open control panel in c:\windows\system32, edit the adaptor settings.  In my case, there was no gateway defined, I enabled Netbios and specified a WINS server.  Problem solved.

  • Different Issue fixed this problem for me

    Cntl-Shft -Esc to bring up Task Manger

    Run CMD

    Time -matched with Source DC time manually

    Date - matched with Source DC manually

    This was under a VMware Esxi 4.1 hypervisor that did have time matched in the hypervisor??

  • If you have miscorrect configured time zone on new SBS 2011 during migration, date or time you could see error "ping OK, networking might not ready with three times". Correct time, date or time zone and everything is OK.