XP workstations slow to connect, causing Failure Audits on file se

I have a Windows Server 2003 file server that is a domain member. Whenever a
non-domain Windows XP workstation attempts to connect to the server (via
Run-'\\address'), the client sits for about 90 seconds before a logon screen
appears. Examining the server's security log, I see multiple Failure Audits
(events 529 and 680). Apparently what the client is trying to do is connect
to the server using its local logon user name and password. It tries this
for a minute and a half, then finally prompts for a new user name/password.

When a Windows Vista client tries to conenct, again multiple events 529 and
680 appear in the server's security log, however it does this very quickly
and immediately pops up a user name/password prompt. No waiting 90 seconds
on Vista clients.

So my question is, why is XP doing this? I understand why it would try the
workstation's logon credentials first when logging into a file server, but
trying for 90 seconds seems excessive. Is there some default setting that
can be changed to improve the situation?

Thanks.

Mike D wrote:
I have a Windows Server 2003 file server that is a domain member.
Whenever a non-domain Windows XP workstation attempts to connect to
the server (via Run-'\\address'), the client sits for about 90
seconds before a logon screen appears. Examining the server's
security log, I see multiple Failure Audits (events 529 and 680).
Apparently what the client is trying to do is connect to the server
using its local logon user name and password. It tries this for a
minute and a half, then finally prompts for a new user name/password.

When a Windows Vista client tries to conenct, again multiple events
529 and 680 appear in the server's security log, however it does this
very quickly and immediately pops up a user name/password prompt. No
waiting 90 seconds on Vista clients.

So my question is, why is XP doing this? I understand why it would
try the workstation's logon credentials first when logging into a
file server, but trying for 90 seconds seems excessive. Is there
some default setting that can be changed to improve the situation?

Thanks.

Post an unedited ipconfig /all from the server, and from one of the problem
XP boxes. I can't answer to Vista, as I don't use it.

Also....have to ask, do you have a *lot* of non-domain-member workstations
on this network, such that this is a regular occurrence? It's a situation
best avoided.

This is normal behaviour,and is designed to make it easier where username
and password already match those on the server. I would suggest using a
batchfile containing:

net use x: \\servername\sharename /user:username

as this will cause it to ask for the password straightaway.

Alternatively, http://mylogon.net may offer a more elegant solution.


"Mike D" wrote:

I have a Windows Server 2003 file server that is a domain member. Whenever a
non-domain Windows XP workstation attempts to connect to the server (via
Run-'\\address'), the client sits for about 90 seconds before a logon screen
appears. Examining the server's security log, I see multiple Failure Audits
(events 529 and 680). Apparently what the client is trying to do is connect
to the server using its local logon user name and password. It tries this
for a minute and a half, then finally prompts for a new user name/password.

When a Windows Vista client tries to conenct, again multiple events 529 and
680 appear in the server's security log, however it does this very quickly
and immediately pops up a user name/password prompt. No waiting 90 seconds
on Vista clients.

So my question is, why is XP doing this? I understand why it would try the
workstation's logon credentials first when logging into a file server, but
trying for 90 seconds seems excessive. Is there some default setting that
can be changed to improve the situation?

Thanks.