Win2k workstation starts to boot after the user starts browsing shared directories on NT4 server.
We have an old NT 4 server environment (working good) and we got a few new machines with Win2k. The problem is as described above. Next problem (connected?) is that loggin into the domain gives every user the same desktop. No matter who loggs in. The only protocol installed is TCP/IP. Are there any possibilities of the two OS:s to work together or do we have to start thinking of getting win2k server?
ASKER
The problem became solved by - by accident! If we installed Win2k over NT4, everything works just fine. Only the "clean" installation caused the bluescreening obove. It must have something to do with the profiles in NT4 and documents and settings in W2k?
Not really sure...?? But you got her fixed and that is what counts...
Here is a tip when dealing with W2K Pro clients in a NT4 domain though... You may be able to use it to advantage. (I have used it in the past to my satisfaction) You can use this to remotely admin the LGP of the clients:
Local Group Policy Remote Administration:
At the command prompt type:
gpedit.msc/gpcomputer:%rem
This will bring up the Local Group Policy interface for the remote computer. Edit the policy and then use the Windows Shutdown.exe utility to reboot the PC and your changes are in effect!
Here is a tip when dealing with W2K Pro clients in a NT4 domain though... You may be able to use it to advantage. (I have used it in the past to my satisfaction) You can use this to remotely admin the LGP of the clients:
Local Group Policy Remote Administration:
At the command prompt type:
gpedit.msc/gpcomputer:%rem
This will bring up the Local Group Policy interface for the remote computer. Edit the policy and then use the Windows Shutdown.exe utility to reboot the PC and your changes are in effect!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I cannot see any reason that connecting to shared resources would cause this to happen, but perhaps another expert could assist and recommend a good reason.
Upgrading to W2K server products is definitely something to consider, for a variety of reasons. Primarily, you can no longer get support from MS for this product. But, the best reason is the nice features that 2K brings to the table. Those include Active Directory, Group Policy, trust relationships with other domains, etc. I think it is well worth the small investment in going forth with the upgrade. Time is the only limiting factor here. Depending on your environment (# users connecting) planning your AD structure is a must, and therefore some time. There have been numerous articles (white papers) written on this and I would be happy to recommend them to you if you desire.
Hope some of this helped. Am sure you will get more responses and additionaly viewpoints.
Happy Holidays.
FE