Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

xp pro join win NT workgroup how to

Status
Not open for further replies.

x2000koh

MIS
Sep 14, 2003
2
SG
Hi all
I am new to window xp and new to this forum.
I have an existing small network using window NT 4 Server and
window 98 client workstations. Now I have installed window xp pro as client. During installation, I did not create any users. When I turn on the window xp machine, wait for a while
it bring me to desktop environment.

I have done a drive mapping, I assigned letter "P" as this public drive. It work fine after I enter the user name and password, check on "reconnet on logon". When I restart the computer, the drive mapping does not work, when I click on my computer, I can see all the drives, but the p:public drive appeared "X" in red indicated that it is not connected. I have to manually click on the p drive, then enter the username and password on the login window.

Question :
How can I restart the computer so that the drive is connected automatically ? Is it because I did not create or turn on the user. So it has no login to connect the p" drive ? My internet connection is working fine. Network printer also working fine. The only thing don't work is the "p" drive did not connected automatically ?

Appreciate any one can help.

Regards,
Francis

 
First, remove the persistant map:

Start, Run, net use P: /delete

Second, Make the entry using either the logon script, or add a .CMD file to the Startup folder for All users. It would have this form:

createp.cmd

net use p: //share_server/sharename /Persistant:no


 
It sounds like the XP machine is not passing logon credentials to the NT 4 server. This will cause you to have to provide the logon credentials manually when attempting to connect to a share on the NT server. Depending on the permissions set on the share (Default: Everyone Full Control) it may not be allowing you to access the drive until proper credentials are provided.

I did not see you mention anything about joining your XP machine to either a workgroup or a domain during installation. Click on the Start then right-click on My Computer then Properties and look at the Computer Name tab. If you are not logging onto a Workgroup/Domain, I cannot guess what is being passed to the NT server for access permission credentials. From the Computer Name tab (if this account has administrator priveledges) you should be able to join the machine to the Workgroup/Domain which should allow you to automatically (Persistently) map your share drive.
 
The problem arises not from a credential issue but from the default behavior of XP to asynchronously process the logon.

For both Win2k and NT Domains this asynchronous processing can in part explain loooong logon times and the failures of persistantly mapped drives among other issues.

The first step is to disable this default behavior. Start, Run, gpedit.msc to load the group policy editor. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.

(This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.)

The second step to ensure the maps do not show the red "X" is to make the maps non-peristant and accomplish the maps through the logon script or a batch file as I described in my original note above. For details on the issue, see the discussion under "Troubleshooting -- Mapping" on Robert Lin, MS-MVP's site:
 
I just commented on XP-to-NT Domain issues in an earlier thread today. It contains some notes I have made for a possible FAQ entry on improving XP client behavior in an NT Domain. While a work in process, I hope it gives you some interesting and valuable approaches:

thread779-651793
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top