Computer migration problems

Discussion in 'Windows Small Business Server' started by Mark mucher, Mar 2, 2004.

  1. Mark mucher

    Mark mucher Guest

    In migrating fro SBS 2000 to SBS 2003 (on a new box), some
    computers have migrated sucessfully, but others give an
    error (when using the computer migration wizard) "The RPC
    server is unavailable"

    I have had some luck in removing and the reinstalling File
    and Printer Sharing but other machines refuse to cooperate.

    All PCs are XP Pro.

    Thanks in advance.

    Mark
     
    Mark mucher, Mar 2, 2004
    #1
    1. Advertisements

  2. If Winsock Proxy Client is on the client machine, remove.
    Make sure the client is at the highest SP level available.


    Robert King
    Microsoft Product Support Specialist
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    |
    | In migrating fro SBS 2000 to SBS 2003 (on a new box), some
    | computers have migrated sucessfully, but others give an
    | error (when using the computer migration wizard) "The RPC
    | server is unavailable"
    |
    | I have had some luck in removing and the reinstalling File
    | and Printer Sharing but other machines refuse to cooperate.
    |
    | All PCs are XP Pro.
    |
    | Thanks in advance.
    |
    | Mark
    |
     
    Robert King [MSFT], Mar 2, 2004
    #2
    1. Advertisements

  3. Mark mucher

    Mark Mucher Guest

    Not sure what Winsock Proxy Client is, but pretty sure
    it's not on.

    All clients are totally up to date.

    Thanks,

    Mark
     
    Mark Mucher, Mar 2, 2004
    #3
  4. Hi Mark,

    Could you please try the following steps and see if they help?

    On the Clients:

    1. Make sure the Remote Procedure Call (RPC) service is running.
    2. Make sure that File and Print Sharing is checked on the properties of
    the Local Area Connection.
    3. Make sure there is an IPC$ and Admin$ share.
    4. At a command prompt run IPConfig /release then IPConfig /renew. Verify
    that the IP address is in the same range as the SBS 2003 server.

    On the SBS 2003 server:

    1. Check to see if the client machines have A (host) records in DNS. If
    not, manually create host records and check the box to create the associated
    PTR record.
    2. Test a couple of machines to make sure they are listening for RPC
    traffic on Port 135. Go to a command prompt and type the following:

    telnet <IP address of the workstation> 135

    You should get a blinking cursor.
    3. Test a couple of workstations to make sure the admin shares are
    available. Go to a command prompt and type:

    net use \\<workstation name>\admin$

    It should come back and tell you the command completed successfully.

    If any computer migrations fail, test with Telnet and net use to make sure
    that RPC is available and that the Admin share can be connected to.
    Check the Application log on the client machine for errors.

    David Jones
    SBS Product Team
     
    David Jones [MSFT], Mar 2, 2004
    #4
  5. The winsock proxy client is a little green globe at the bottom right of the
    screen. You can remove it from add remove programs.

    Robert King
    Microsoft Product Support Specialist
    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    |
    | Hi Mark,
    |
    | Could you please try the following steps and see if they help?
    |
    | On the Clients:
    |
    | 1. Make sure the Remote Procedure Call (RPC) service is running.
    | 2. Make sure that File and Print Sharing is checked on the properties of
    | the Local Area Connection.
    | 3. Make sure there is an IPC$ and Admin$ share.
    | 4. At a command prompt run IPConfig /release then IPConfig /renew.
    Verify
    | that the IP address is in the same range as the SBS 2003 server.
    |
    | On the SBS 2003 server:
    |
    | 1. Check to see if the client machines have A (host) records in DNS. If
    | not, manually create host records and check the box to create the
    associated
    | PTR record.
    | 2. Test a couple of machines to make sure they are listening for RPC
    | traffic on Port 135. Go to a command prompt and type the following:
    |
    | telnet <IP address of the workstation> 135
    |
    | You should get a blinking cursor.
    | 3. Test a couple of workstations to make sure the admin shares are
    | available. Go to a command prompt and type:
    |
    | net use \\<workstation name>\admin$
    |
    | It should come back and tell you the command completed successfully.
    |
    | If any computer migrations fail, test with Telnet and net use to make sure
    | that RPC is available and that the Admin share can be connected to.
    | Check the Application log on the client machine for errors.
    |
    | David Jones
    | SBS Product Team
    |
    | --
    | This posting is provided "AS IS" with no warranties, and confers no
    rights.
    |
    |
    |
     
    Robert King [MSFT], Mar 2, 2004
    #5
    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.