sbs 2008 migration cannot find source server

Discussion in 'Windows Small Business Server' started by Jim Budde, Oct 21, 2008.

  1. Jim Budde

    Jim Budde Guest

    I'm trying to perform a migration of an SBS 2003 environment. During the
    Migration process the "Source and Destination Server information" dialog box
    is shown and a dialog box Title: "Cannot find the Source Server" with the
    following details: "Verify that the Source Server name is correct, and then
    try again."

    My SBS 2008 server is running in VMware with a bridged NIC configuration. I
    have tried several things and placed wireshark on the VMWare host. It
    appears the NetBios Name resolution request for my source server is not
    being answered. The VMWare host is NOT part of the existing SBS 2003
    domain. When I ping the simple SBS 2003 Source server name I don't get an
    ack back, but I do if I use the FQDN.

    I've performed all of the prep steps on the Source Server and resolved all
    critical items in the Best Practices Analyzer Report. I never had to worry
    about WINS on the original server before but with this issue I've added
    static entries for my source server and the WINS service doesn't seem to
    have any requests for Name Resolution coming to it.

    Any thoughts on how to further troubleshoot or create a work-around so the
    Destination server can resolve the Source Server name (The source server has
    two NICs in it, but both nics are on the same subnet, i.e. I'm not running
    ISA).


    -Jim
     
    Jim Budde, Oct 21, 2008
    #1
    1. Advertisements

  2. Jim Budde

    Les Connor Guest

    I presume you're using an answer file?

    If the fqdn works, why not use that? It seems to me (from memory) that the
    answer file requires fqdn.
     
    Les Connor, Oct 21, 2008
    #2
    1. Advertisements

  3. If your server is configured 2 NICs Internal and WAN they can't be on same
    Subnet. Your best bet is to convert to single NIC and disable the second NIC
    since you are not using ISA
     
    Frank McCallister SBS MVP, Oct 22, 2008
    #3
  4. Jim Budde

    Jim Budde Guest

    Son of a B! In the process of following your advice and switching to a
    single NIC I poked around the advanced settings of the TCP/IP settings and I
    remember a while back I had turned off NetBIOS over tcp/ip to test various
    security options to determine impacts on several applications. Once I
    enabled netbios over tcp/ip the migration process proceeded.

    Thanks for the advice all.

    -jim
     
    Jim Budde, Oct 22, 2008
    #4
  5. Jim Budde

    Jim Budde Guest

    Found the Solution. After much searching and some additional posts on
    technet, I suggest others follow the link below.

    There are several troubleshooting steps provided by Msft there, including my
    ultimate solution which was two-fold 1) I still had a stray IP address for
    the 2nd NIC that I had disabled on the SBS 2003 Sourve Server (when I ran
    nslookup on domain.local DNS returned the disabled IP address first). This
    first step only got me a bit further in the dcpromo process and I still
    recv'd the same error box as below. My ultimate solution related to
    granting "Everyone" "Access this computer from the network" permission to
    the correct GP object.

    http://social.technet.microsoft.com...n/thread/659ecd7f-ab02-48d0-a7e6-4fb87572cdaa

    -Jim
     
    Jim Budde, Oct 23, 2008
    #5
  6. Make sure you temporarily have the source and destination server on the same subnet of 255.255.255.0

    You cannot use any other subnet than this....

    I had a 255.255.0.0 subnet and had to change mine to get through this...




    Jim Budde wrote:

    sbs 2008 migration cannot find source server
    21-Oct-08

    I'm trying to perform a migration of an SBS 2003 environment. During the
    Migration process the "Source and Destination Server information" dialog box
    is shown and a dialog box Title: "Cannot find the Source Server" with the
    following details: "Verify that the Source Server name is correct, and then
    try again."

    My SBS 2008 server is running in VMware with a bridged NIC configuration. I
    have tried several things and placed wireshark on the VMWare host. It
    appears the NetBios Name resolution request for my source server is not
    being answered. The VMWare host is NOT part of the existing SBS 2003
    domain. When I ping the simple SBS 2003 Source server name I don't get an
    ack back, but I do if I use the FQDN.

    I've performed all of the prep steps on the Source Server and resolved all
    critical items in the Best Practices Analyzer Report. I never had to worry
    about WINS on the original server before but with this issue I've added
    static entries for my source server and the WINS service doesn't seem to
    have any requests for Name Resolution coming to it.

    Any thoughts on how to further troubleshoot or create a work-around so the
    Destination server can resolve the Source Server name (The source server has
    two NICs in it, but both nics are on the same subnet, i.e. I'm not running
    ISA).


    -Jim

    Previous Posts In This Thread:

    sbs 2008 migration cannot find source server
    I'm trying to perform a migration of an SBS 2003 environment. During the
    Migration process the "Source and Destination Server information" dialog box
    is shown and a dialog box Title: "Cannot find the Source Server" with the
    following details: "Verify that the Source Server name is correct, and then
    try again."

    My SBS 2008 server is running in VMware with a bridged NIC configuration. I
    have tried several things and placed wireshark on the VMWare host. It
    appears the NetBios Name resolution request for my source server is not
    being answered. The VMWare host is NOT part of the existing SBS 2003
    domain. When I ping the simple SBS 2003 Source server name I don't get an
    ack back, but I do if I use the FQDN.

    I've performed all of the prep steps on the Source Server and resolved all
    critical items in the Best Practices Analyzer Report. I never had to worry
    about WINS on the original server before but with this issue I've added
    static entries for my source server and the WINS service doesn't seem to
    have any requests for Name Resolution coming to it.

    Any thoughts on how to further troubleshoot or create a work-around so the
    Destination server can resolve the Source Server name (The source server has
    two NICs in it, but both nics are on the same subnet, i.e. I'm not running
    ISA).


    -Jim

    I presume you're using an answer file?If the fqdn works, why not use that?
    I presume you are using an answer file?

    If the fqdn works, why not use that? It seems to me (from memory) that the
    answer file requires fqdn.

    --
    Les Connor [SBS-MVP]


    ____________________________

    If your server is configured 2 NICs Internal and WAN they can't be on same
    If your server is configured 2 NICs Internal and WAN they can't be on same
    Subnet. Your best bet is to convert to single NIC and disable the second NIC
    since you are not using ISA

    --
    Frank McCallister SBS MVP
    MCP Microsoft Small Business Specialist
    COMPUMAC


    Yes, using answer file.
    Yes, using answer file. The Source Server Name has to be a netbios name,
    attempting to enter fqdn in this field does not work (at least for me it
    does not becuase the host + fqdn > 15 characters.

    Son of a B!
    Son of a B! In the process of following your advice and switching to a
    single NIC I poked around the advanced settings of the TCP/IP settings and I
    remember a while back I had turned off NetBIOS over tcp/ip to test various
    security options to determine impacts on several applications. Once I
    enabled netbios over tcp/ip the migration process proceeded.

    Thanks for the advice all.

    -jim



    "Frank McCallister SBS MVP" <anonymous> wrote in message

    Found the Solution.
    Found the Solution. After much searching and some additional posts on
    technet, I suggest others follow the link below.

    There are several troubleshooting steps provided by Msft there, including my
    ultimate solution which was two-fold 1) I still had a stray IP address for
    the 2nd NIC that I had disabled on the SBS 2003 Sourve Server (when I ran
    nslookup on domain.local DNS returned the disabled IP address first). This
    first step only got me a bit further in the dcpromo process and I still
    recv'd the same error box as below. My ultimate solution related to
    granting "Everyone" "Access this computer from the network" permission to
    the correct GP object.

    http://social.technet.microsoft.com...n/thread/659ecd7f-ab02-48d0-a7e6-4fb87572cdaa

    -Jim





    Submitted via EggHeadCafe - Software Developer Portal of Choice
    Excel 2007 Filter Tool
    http://www.eggheadcafe.com/tutorial...a2cb-1f3a46fbea8f/excel-2007-filter-tool.aspx
     
    Cor Knijnenburg, Apr 24, 2010
    #6
  7. I had this same issue and none of the fixes I found online worked. Here's how I worked around it:

    While on the wizard dialog, press Ctrl+Alt+Del and bring up the Task Manager. Go to File > New Task and type CMD to bring up the Command Prompt.

    Ensure your SBS2008 box has been assigned an IP address, and that you can ping the SBS2003 box by IP. Most likely you won't be able to ping via Netbios name - the reason the wizard is bombing out.

    Click File > New Task again and this time type Explorer, to bring up Windows Explorer. Browse to C:\Windows\System32\drivers\etc and open up hosts in Notepad. Add an entry at the bottom with the IP address and the NetBIOS name, then save and close the file.

    You should now be able to ping the SBS2008 box via NetBIOS name and therefore continue to the next phase of the migration.
     
    Andrew van Alphen, Feb 9, 2011
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.