problems after uppgrade

Discussion in 'Server Migration' started by Simon P, Jul 4, 2005.

  1. Simon P

    Simon P Guest

    Hi
    Our company bought a new server and installed nt4 server BDC= domain1
    Then we made an isolated test network where we uppgraded the NT4 bdc to
    primary server and then uppgraded it to win2003 server=domain1.domain.se
    The whole purpose is to replace the old PDC.

    Everything look Nice whith DNS, Wins and AD (No errors in the logs)
    when we try to login whith one of the computers it will not accept the user,
    it complains that the user hasn't got the right password (not true we have).
    If i manualy connect it to the domain1.domain.se it works but it takes ages
    to start the workstation.

    1. Shouldn't I be able to just replace the server after an 2003 uppgrade so
    the workstations can connect to the new DC whithout me running around on
    every computer to connect to the new server?

    2. How important is the Wins in the uppgrade?

    3. When you are using Raid5 on server, is it no chance of the extension of
    the 4GB partition?

    thanks in advance
    Simon
     
    Simon P, Jul 4, 2005
    #1
    1. Advertisements

  2. Simon P

    Herb Martin Guest

    The other choice is to upgrade the PDC to Win2003 (and yes
    you can do that even if the old PDC hardware doesn't support
    Win2003.)
    have).

    Depends a lot on the timing -- for instance the user OR the user computer
    might have changed it's password with the domain after you removed the
    DC and before you tried it....
    That's usually a DNS issue -- I will post my AD DNS outline below.
    Probably. But you will need the DNS to work. And if you use WINS that
    will still be needed after the upgrade.
    Not at all to the direct upgrade but it is JUST as essential as it was in
    NT4
    for most purposes.

    If you needed WINS before you need it with Win2003.
    There is no 4GB limit for anything except FAT volumes. Use NTFS and
    it is quite possible to get beyond 4GB. (terabytes at least.)
     
    Herb Martin, Jul 4, 2005
    #2
    1. Advertisements

  3. Hello Simon,

    Good to hear from you.

    According to the message, I understand that you have done an upgrade from
    NT to win2k3 domain and met some issues.

    I agree with Herb that the issue on one computer may be caused by the
    password change which occurred after the BDC is taken offline.

    The long delay is probably caused by the DNS. Please check that the client
    has configured DNS correctly. Make sure all the clients point to the new
    win2k3 DC for preferred DNS server.

    I believe Herb has given all the answers to your questions. If you have
    further concerns, please let us know.

    As for the 4GB extension, please check the following article for more
    information.

    325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
    http://support.microsoft.com/?id=325857


    Hope this helps. Please feel free to post back if you have further
    questions.

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    ============================================================================
    ===================
    In an effort to secure NNTP access to partners only, the password will
    change every 6 months when using Outlook Express or other NNTP client to
    view the Microsoft Managed Newsgroups. The current password has been active
    since July 1, 2005.

    This does not impact the web-based newsreader at:
    https://partner.microsoft.com/global/technicalsupport/registeredsupport/4001
    3938

    The new password will be active from July 1, 2005 until January 3, 2006
    (9:00 am PST).

    Please visit and mark as a favorite the following link to obtain the new
    password information as well as the instructions for configuring OE for
    newsgroup access.
    https://partner.microsoft.com/global/40012653. You will need to sign in to
    the partner portal to access this page.
    ============================================================================
    =====================
     
    Frances [MSFT], Jul 5, 2005
    #3
  4. Simon P

    Simon P Guest

    Hi
    Thanx to both of you for your answers.

    1. I tried to uppgrade our old server(Netfinity5000 -98) to 2003 but it just
    gave me blue screen of death every time.
    Thats why we decided to buy a new one.

    2. Before I uppgraded the New server from NT to 2003 I followed the "325857
    How To Expand the Boot Partition During a Windows Server 2003 Upgrade" copied
    the unattend file and .... but nothing happend to my 4GB partition I hoped I
    could chose a bigger partition, but as I understand the 325857 document it
    only works on a singel disk not on a mirroring disk. It realy puts me in a
    bad situation when the new server just have 1,6GB free space on C boot parti.
    Can you please confirm if it is like that?

    3. Since I synced the BDC with the PDC before I isolated it I had the latest
    passwords and computers and I tried to logg in with 3 different admin
    accounts and still got error "wrong password for domain".

    Thanx again
    Simon
     
    Simon P, Jul 5, 2005
    #4
  5. Hello Simon,

    Thanks for the reply.

    According to the message, I understand that the original PDC cannot be
    upgraded to win2k3. It seems that the hardware may have conflicts with
    win2k3.

    As for the 4GB limitation, in the notes of the KB article, we find the
    following comments:
    If the boot partition is configured to use disk mirroring, it cannot be
    expanded. You must break the mirror before you use the In-place Upgrade
    option.

    From the comments and the test you made, it is proved to be true that we
    cannot expand the partition when using disk mirroring.

    At this time, I would like to suggest that you break the mirror to expand
    the partition. Please refer to the steps in the following article to break
    the mirror.

    128630 How to Recover From a STOP 0x00000058 FTDISK_INTERNAL_ERROR
    http://support.microsoft.com/?id=128630

    Or you can buy a new machine, install win2k3 on it and promote it to be a
    DC. You can transfer the FSMO roles to the newly installed DC, and then
    demote and format the upgraded win2k3 DC. It is always best to use a clean
    installed DC to hold the FSMO roles.

    As for the issue on the specific computer, if other computers in the domain
    don't experience the same issue, we can isolate it from a server side
    issue. If this is the case, we may trouble shoot the specific machine. It
    would be best to discuss the issue on the client side. For example, if the
    computer is a winXP machine, you may post in the winXP newsgroup for this
    issue. If other computers have the same issue, please give me the exact
    error message. You may take a screen shot of the error message as a .jpg
    file and send to . I will research on this and check
    what the possible cause is.


    Hope this helps. If you have further concerns, please get in touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    ============================================================================
    ===================
    In an effort to secure NNTP access to partners only, the password will
    change every 6 months when using Outlook Express or other NNTP client to
    view the Microsoft Managed Newsgroups. The current password has been active
    since July 1, 2005.

    This does not impact the web-based newsreader at:
    https://partner.microsoft.com/global/technicalsupport/registeredsupport/4001
    3938

    The new password will be active from July 1, 2005 until January 3, 2006
    (9:00 am PST).

    Please visit and mark as a favorite the following link to obtain the new
    password information as well as the instructions for configuring OE for
    newsgroup access.
    https://partner.microsoft.com/global/40012653. You will need to sign in to
    the partner portal to access this page.
    ============================================================================
    =====================
     
    Frances [MSFT], Jul 7, 2005
    #5
  6. Simon P

    Simon P Guest

    Hi
    After lots of coffee and long nights I have succeded in my uppgrade, almost
    everything works perfect. I m so happy that this newsgroup exist.
    Last question........
    How come that the XP workstations are slow during the profile startup after
    the login screen. all other win2K are fast and all XP are slow as ...#&@!....

    regards
    Simon
     
    Simon P, Aug 2, 2005
    #6
  7. Simon P

    Herb Martin Guest

    Hi
    ....#&@!....

    That's too vague but first check your name resolution, especially
    DNS.

    All internal clients must point STRICTLY at the internal DNS
    servers which can resolve all internal addresses they need
    (and those DNS SERVERS must do any external resolution they
    need too.)

    All DCs are "internal DNS clients" too.

    Try DCDiag on all DCs -- NetDiag on all non-DCs.

    DNS for AD
    1) Dynamic for the zone supporting AD
    2) All internal DNS clients NIC\IP properties must specify SOLELY
    that internal, dynamic DNS server (set.)
    3) DCs and even DNS servers are DNS clients too -- see #2
    4) If you have more than one Domain, every DNS server must
    be able to resolve ALL domains (either directly or indirectly)

    netdiag /fix

    ....or maybe:

    dcdiag /fix

    (Win2003 can do this from Support tools):
    nltest /dsregdns /server:DC-ServerNameGoesHere
    http://support.microsoft.com/kb/q260371/

    Ensure that DNS zones/domains are fully replicated to all DNS
    servers for that (internal) zone/domain.

    Also useful may be running DCDiag on each DC, sending the
    output to a text file, and searching for FAIL, ERROR, WARN.

    Single Label domain zone names are a problem Google:
    [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


    --
    Herb Martin, MCSE, MVP
    Accelerated MCSE
    http://www.LearnQuick.Com
    [phone number on web site]
     
    Herb Martin, Aug 3, 2005
    #7
  8. Hello Simon,

    Good to know the upgrade succeeds!

    As for the winXP slow logons, I suspect that this issue is mainly related
    to DNS. What Herb suggests is really worth trying. We have to make sure
    that each winXP DNS client points to the internal DNS servers correctly.

    On the client side, you may try the following commands in the command
    prompt to check the DNS part.
    Nslookup yourcomputername
    Nslookup yourDNSservername

    Since you upgrade from an NT domain, I would like to confirm that you are
    not using the Single Label domain name. It is not recommended and may lead
    to many issues. Please refer to the following KB article:

    300684 Information About Configuring Windows 2000 for Domains With
    Single-Label
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;300684

    Hope this helps. Further concerns, please get in touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Aug 3, 2005
    #8
  9. Simon P

    Simon P Guest

    Hi Herb and Frances

    Thankyou for your help, the DNS works fine now on the clients.
    Thanx for everything.

    cheers
    Simon
     
    Simon P, Aug 8, 2005
    #9
  10. Simon P

    Herb Martin Guest

    So it was a DNS issue?

    (It's nice to know how you fix such things as that helps us to help
    others with similar problems...)
    You're welcome.
     
    Herb Martin, Aug 8, 2005
    #10
  11. Hello Simon,

    Good to hear the news. You are welcome.

    As Herb said, it would be best if you could detail the resolution to share
    the experience. :)

    In the future, if you have any other concerns, please feel free to let us
    know.

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Aug 9, 2005
    #11
  12. Simon P

    Simon P Guest

    Hi Both of you

    The problem felt so easy when I saw it in the "Advance, property of
    networkconnection" I'm feeling stupid not to seeing it before.

    The DNS on the clients was pointing to the ISP:s DNS not
    to our servers so I changed it to our to DC:s and the clients worked fine
    after that.

    Thanx again.

    Simon
     
    Simon P, Aug 10, 2005
    #12
  13. Simon P

    Herb Martin Guest

    Hi Both of you
    Nothing to feel stupid about.

    How do you think WE learned this was a bad idea? <grin>

    In my case by doing it wrong, and for both Frances and I by
    helping thousands of people (literally) to solve such problems.

    If I immediately know how to fix your problem, chances are
    that I have seen it before ... <ahem, cough, cough>
     
    Herb Martin, Aug 10, 2005
    #13
  14. Hello Simon,

    Thanks for sharing you experience.

    What Herb said is true. Although it is a simple setting, it helps when we
    meet similar issues in the future. Maybe the next time when a customer
    complains about the slow logons, we will first check this setting. :)

    If you have other concerns, please feel free to contact us!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Aug 11, 2005
    #14
    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.