Windows Forum

Ask something
Discussion Locked

Event 677-Service ticket request failed

0 helpful
6 replies

by johnnyextreme 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

PLEASE, MAKE IT STOP!
My Win2K Pro machines are filling up my security log on the Win2K domain controller with this event -
Service Ticket Request Failed:
User Name: Garratt
User Domain: DELCO.COM
Service Name: HOST/FILESVR
Ticket Options: 0x40810010
Failure Code: 7
Client Address: 10.0.1.53
One of these for each server they have a mapped drive for (like FILESVR above) except the Win2K server, and one for their user name as well as one for their computer name. I have a logon batch file which maps network drives for all users. Often, but not always, the mapped drives appear with a red x in My Computer, even though they are accessible. Any suggestions? I'm going to try taking the batch file out of a users profile andsee what difference that makes.

6 replies

by johnnyextreme

With no mapped drives the events do not appear. This is a mixed NT/Win2K network and only Win2K clients cause these messages, and only when they are mapping directories on NT machines.

by izz

I can tell you that if supposedly in your NT Domain Controller, u have specified a home folder for each user. Then by default w2k Pro will map it as a network drive, with no need for a login script. I have an NT4.0 domain and I am upgrading the clients first to W2k PRo, so I have noticed that by default for those tha I have created a home folder it appears in "My computer" as a mapped drive, with no need for login scripts.

And for this X, well lately I read an article that summed up as:" Aslong as when u click on the mapped drive u will reach it so why are u thinking about it." Meaning no explanation for that so far.

Hope this helps.

by johnnyextreme

The login script is for drives other than the home folder that each user needs to have mapped. I'm concerned about these unnecessary audit events.

by magetower

The problem is related to your domain setup. This is the assumption:
You are running a W2K Server as the PDC in a mixed-mode setup using Active Directory. You have other servers running NT4 as BDCs or member servers.

The W2K clients by default will recognize the existance of the Acitive Directory DC and will establish Kerberos encryption service tickets with the DC. Because of the mixed-mode environment the clients will first try to use their Kerberose tickets to authenticate with the NT servers. This will fail (thus the log entries). They will then revert to authenticating with NTLM and will succeed with the NT4 servers (thus being able to access shares despite the errors).

When the login script is run it tries to establish the connection to the NT4 server and failes the initial authentication. The client will continue to login but any mapped drives will show a red X indicating initial failed connectivity but clicking on the mapped drive causes the authentication process to go through the motions (probably causing more log entries) and the NTLM authetication eventually kicks in granting access.

Being not totally familiar with the Kerberos stuff I'm not sure how you can disable (either selectively or globally) to eliminate the error logging but hopefully this will point you in the right direction.

Good Luck

by johnnyextreme

Very good answer. It would be nice to have a Win2K network in Native mode, but until then I'll use the information you gave me to redirect my search for answers.

This discussion is closed to new replies.