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?
erkytAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fatal_ExceptionSystems EngineerCommented:
Regarding the reboot in your 2k workstations.  Are they bluescreening?  Have you cked your error logs?  http://support.microsoft.com/?kbid=192463

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
0
erkytAuthor Commented:
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?
0
Fatal_ExceptionSystems EngineerCommented:
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:%remotecomputername%

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!
0
GhostModCommented:
PAQed, with points refunded (125)

GhostMod
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.