Mapped Drives Win XP in NT4 Domain

[hceonetman]

I've read numerous threads of XP users unable to connect to an NT4.0 domain, but have not seen my particular problem. Our domain is a single server domain on the same subnet. We use static IP addressing. When first setting up the XP-Pro box I join the computer to the domain and create a user with admin rights in that domain. The user and password match an existing user on the domain. Everything seems to work and I can login just fine. I then set up drive mappings in 'Network Places' and make them reconnect at login. Again no problem. The odd thing is that every time I login I get the message 'Could Not Reconnect All Network Drives'. When I go to either Network Places or Explorer the drives show up with the red 'Not Connected' icon. However, when I click on them I am connected. All files are available and I am not prompted for another password.
In short, on bootup XP tells me I can't reconnect when in fact I am fully connected. I would like to not have to explain this to my users each time I add a new XP box.
I tried disabling the 'Digitally encrypt or sign secure channel data-always' setting but it made no difference.
Anyone else seen this problem?

Thanks
HCEONETMAN

 

[wolluf]

I have seen other posts with this issue (so worth a search). Good chance that Linney will have a good link, if he reads this.

PS. Have you tried using login script & net use as method of mapping?

 

[hceonetman]

Wolluf
Thanks for the suggestion. XP is still the newcomer in the domain, most users are W98SE. Also, not all of my XPs have this problem. I have experimented with login scripts before and didn't find them beneficial. I can't remember all the reasons, but I wasn't happy with them.
Though there are advantages with XP, I find their network configuration functionality a step backwards from 98 or 2000. Unless they're aimed at some future network operating system that we don't yet (and never may) understand.

HCEONETMAN
When superior marketing competes with superior technology, put your money on the ad-men.

 

[conceptumator]

A lot of the problems you see listed are from users who bought XP Home. The home version will not connect to a domain, while the XP Pro version will. That's why the difference in $$.

Suggestion for those having the problem:

We have several notebooks in our office which give problems if they are trying to authenticate to a domain when you aren't in the office (obviously). I set these machines up on a workgroup -- works perfectly.

I am using a mix of Win XP Pro, Win98SE and Win2K machines in two separate networks without a hitch. One server is Win2K Server, the other is WinNT Server 4.0 SP6

 

[hceonetman]

Thanks again, but that's still not the problem. I am using XP-Professional pre-loaded on Dell Optiplex systems. Also, everything works as it should - the error message is the only symptom of anything wrong.

But, #1, I don't like error messages, even if bogus; #2 Users don't like the extra click to clear the message and I have nothing to offer them; #3 This is the only symptom I see, but is there something wrong that is not evident?

I'd love to solve it, but in the meantime I'm not losing any sleep over it. Just thought someone else may have had the same thing.
HCEONETMAN

 

[GDGarth]

Did you ever figure this one out? I've got the exact same problem, and I'm getting tired of having to click on each of my mapped drives to get them to reconnect.

Is there any way to use a script or batch file to reconnect the network drives?

 

[bcastner]

I am sorry I missed this thread. The issue at its core lies with the default of Win2k and XP clients to make any mapping persistant.

You need to adjust your logon scripts for NT4 servers to remove existing mappings on logon and recreate them anew. See this site under the subhead "Mapping" for further details:

http://www25.brinkster.com/ChicagoTech/

 

[GDGarth]

I put a "Net Use" statement to map each of my network drives into my autoexec.bat file, and it seems to have solved the problem.

 

[hceonetman]

I've tried to avoid login scripts altogether. We are small enough that 2 of us can manage all the PCs and set their persistent mapping on the individual machine. I've gradually gotten the PCs to stop displaying the error message by making sure the WINS settings are correct and I've also installed the 'Network Monitor Driver' in network properties.
Thanks for the ideas though.

HCEONETMAN