Terminal services problem

[TeddyTed]

I just rebuilt (clean install) my Win2K server machine, did all my updates -including Sp3- and then installed terminal servies.
For some reason TS won't start.
When i go into Terminal Services magement console I find the following: "youcould not be authenticated on this server".

This machine is used to share files.
There is no DC on the network.

I have uninstalled and reinstalled TS but the result is the same every time.
Is anyone farmillar with this situation?


Thanks,
TB

[objohn]

Have you installed in in remote admin mode or application mode?

What account is the service running under - change it to the system account if it's not running under that.

Win2K Sp4 is is the latest SP for Win2k, not Sp3 - install that, then run windows update on it.

OJ

[caribconsult]

I don't agree about SP4. I've seen several units, both workstations and servers, that functioned nicely under SP3 and went off the rails on SP4, so my suggestion is avoid SP4

[TeddyTed]

I'm running it in Remote admin mode.
I've installed sp4 and did my updates.

What account is the service running under - change it to the system account if it's not running under that.

OJ, I'm not quite sure what you're talking about here. Please elaborate...


Thanks,

TB

[objohn]

If you open up services.msc, slect Terminal Services and then go to properties. Under Logon, it will show it it's running under a user account or the system account.

check www.microsoft.com/technet.


OJ

[TeddyTed]

OJ, Thanks for your help.
I finally got it running. I uninstalled and reinstalled the service packs.
That did the trick.


Thanks

TB

[YeOldeStonecat]

No issues with SP4 on any of my clients servers, just did a big research center full last night even, 8x servers. They'd not been attended to by any IT in a long time, most were waaaay back at SP2 still.

I'm a strong believer in keeping all Critical Updates updated. If the machine had issues after applying a critical update or service pack...then there most likely was some existing issue with the machine.

Out of the quite literally hundreds of servers I've worked on, the only time I've seen a service pack blow up with when NT 4.0 6.0 first came out....it was very buggy, 3 days later 6.0a was out. And I didn't install it, just fixed it, but it was pretty official that the original SP6 was buggy.

[TeddyTed]

I hear you YOSC....
Actually, the problem wasn't the service pack. After refreshing my memory I recalled that I didn't restart the machine after installing SP2, I just went ahead and installed SP3. That is what caused the problem.


Thanks!
TB