0 pts.
 Net.exe process hangs around and stops all office files being opened, sound weird – you bet it is.
I have a network thats running a mix of XP SP1 and 2 - on a win 2k ADv as a DC and the file server aswell. The problem is that after a .cmd logon script has run that the client computers still have the cmd.exe and net.exe process running ... and these processes are stopping any network or local office files from being opened the computer locks up when clicking on the files and then we get a not responding error. Anyone have ideas? As soon as i kill the net.exe and cmd.exe the files are available no worries. What is going on? Help please

Software/Hardware used:
ASKED: May 1, 2005  10:20 PM
UPDATED: May 25, 2005  8:20 PM

Answer Wiki:
NET.exe & CMD.exe - Logon script. Hangs. U betcha! Have you tried running the script in a 'command prompt window'? Unless you have watched the script in a window you don't know where the process stops. (Usually waiting on a response from the keyboard.) Items that cause hangs in logon script - #1 - mapping a non existing drive. Also gets you if you left 'Windows Explorer' at the default of checking 'network shares and drives' upon start. #2 - printer redirects, changes to network printers that are not on. #3 - secondary logins (this is a biggie) If you try to set access to a 2nd domain before the first one initializes, the process locks up waiting for a flag that cannot arrive. #4 - Bad script commands. There are small changes in scripting in XP and SP2. These changes are in the allowed options (xxx.exe /1 /C /E etc.) An invalid option will generate an error that you can only see in the command prompt window. This should get you started. Good Luck.
Last Wiki Answer Submitted:  May 2, 2005  10:42 am  by  Howard2nd   30 pts.
All Answer Wiki Contributors:  Howard2nd   30 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Net.exe is a virus.

You should run a scan on your machine.

 0 pts.

 

You betcha – it wasnt a virus.

It was exsactly what the first guy said well done good sir.

Peach out

 0 pts.