mapping network drive fails between NT and 2003 server

Discussion in 'Server Migration' started by PaulW, Jul 27, 2004.

  1. PaulW

    PaulW Guest

    I am halfway through an NT to 2003 migration and I
    thought mall waqs well. NOT SO FAST!! I upgraded an NT
    PDC to WS2K3 as recommended, all went well. Now I find
    that new users created after the migration can not map
    network drives from their client computers to the files
    on the NT server. They fail authentication and It
    prompts you for a valid userid/password. If you enter
    these from the old migraqted users it works. If you
    enter a newly created user it fails. If I delete an old
    users accouint and add it back, it stops working.

    Any leads would be appreciated


    P.S. By mapping network drives I mean typing:
    NET USE Z: \\servername\sharename
    PaulW, Jul 27, 2004
    1. Advertisements

  2. Hi Paul,

    Thanks for your posting here.

    I would like to confirm the following information with you.

    1. What is the operation system running on the client and file server?
    2. Are the client and file server in the same domain?
    3. What is the detailed error massage?
    4. Is there any related error in the event logs on client and file server?
    5. Does the problem occur on all the clients just some certain clients?
    6. Does the problem occur if you try to map a share on Windows 2003 DC?

    Bob Qin
    Product Support Services
    Microsoft Corporation

    Get Secure! -

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Bob Qin [MSFT], Jul 28, 2004
    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.