never seen this myself before. Weird drive mapping problem

  • Thread starter Thread starter MM
  • Start date Start date
M

MM

Hi, Can anyone help with this problem: I have not seen this before.

I have decommissioned a NT 4 file/print server called F-01 and moved the
date to a new Server F-02. I have a dedicated Terminal Server called T-05
for remote users to access F-02. The kix script on T-05 is executed via
usrlogon.cmd upon logon onto the T-05 and maps drives/assigns printers etc.

The problem is now that the data is moved, once I shutdown F-01 the script
maps drives to the new server F-02 on T-05 but after about 30 seconds these
drives simply disappear. The mapped drives are correct and so are the
printers. They are all on F-02. The old server has had all the printers
deleted. The E: volume data folders have been unshared and renamed old after
the data was moved.

If I turn on the old F-01 then there is no problem. In other words T-05 is
having a problem once F-01 is turned off.

Has any expert out there got any ideas? Please e-mail them to me via
(e-mail address removed)

I will thank you with a reply of gratitude if the suggestion works for me.

Thanks and regards
 
This old NT 4.0 server was not a BDC, was it?
Did you have any applications installed on it that use a shared
server installation as well as a client installation on the TS,
like Office? If that's the case, you will have to uninstall and
reinstall.
A last resort might be to search the registry on the T-05 for the
string F-01. I've had a similar problem, and we had to manually
change some obscure registry keys to fix the problem.

You could also download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator on T-05,
and start a TS session as a normal user.

FileMon and RegMon will show you all files and registry keys that
are being accessed, including all "access denied" and "path not
found" errors that occur.
 
Vera,

Thank you VERY much. FileMon helped me find out what was happening.

We use a kix script here and it was originally located in
c:\winnt\system32\grouppolicy\user\logon\scripts\ folder. Our policy then
changed and we were told to re-located the logon scripts to
c:\winnt\system32\kix folder with usrlogon.cmd to be used to execute the
script (why - I don't know). The script files were copied and not moved to
the new location for this one particular server only. Therefore, both
scripts were executing one after the other. A new W2K server replaced the
NT4 server and the kix folder script was changed - therefore the second
script would overwrite the first script with the old server details. It's so
fast you don't see what's happened.

Very embarrassing!!!
 
Back
Top