Why does W2K (pro) client do more than it is asked to do?

Desperate to find out why connecting to a samba share (on an AIX
server) from W2K is so slow, I tried connecting to the same share from
a Linux box, using smbclient:

smbclient \\\\aixserver\\sharedir$ -U lynn

The results were amazing. The connection was so MUCH FASTER then
connecting from a W2K (pro) workstation:

\\aixserver\sharedir$ (in the Start|Run edit box)


When I examined the samba log files on the server, I could see why.

The log file for the Linux client contained a single entry:

[2004/02/23 11:55:35, 1] smbd/service.c:make_connection(636)
linuxbox (192.168.0.4) connect to service sharedir$ as user lynn
(uid=21776, gid=1) (pid 125438)

So clean, so elegant, so beautiful!

OTOH, the log file for the W2K client contained an entry similar to
the above, but was immediately followed by about 30 messages of the
form:

[2004/02/23 11:59:03, 0] smbd/password.c:user_ok(683)
rejected user nobody:3004-302 Your account has expired; please see
the system administrator.

Now... my question: Why? What does the W2K client do that triggers
this barrage of rejected authentications of a user 'nobody' (that is
clearly not allowed to enter)?

More importantly, is there a way to configure the W2K client to *not*
waste time on these unrequested/unallowed accesses?

Thanks in advance,
Lynn

On 25 Feb 2004 06:11:21 -0800, linuxlover992000@yahoo.com (Linux
Lover) wrote:

>Desperate to find out why connecting to a samba share (on an AIX
>server) from W2K is so slow, I tried connecting to the same share from
>a Linux box, using smbclient:
>
>smbclient \\\\aixserver\\sharedir$ -U lynn
>
>The results were amazing. The connection was so MUCH FASTER then
>connecting from a W2K (pro) workstation:
>
>\\aixserver\sharedir$ (in the Start|Run edit box)
>
>
>When I examined the samba log files on the server, I could see why.
>
>The log file for the Linux client contained a single entry:
>
>[2004/02/23 11:55:35, 1] smbd/service.c:make_connection(636)
> linuxbox (192.168.0.4) connect to service sharedir$ as user lynn
>(uid=21776, gid=1) (pid 125438)
>
>So clean, so elegant, so beautiful!
>
>OTOH, the log file for the W2K client contained an entry similar to
>the above, but was immediately followed by about 30 messages of the
>form:
>
>[2004/02/23 11:59:03, 0] smbd/password.c:user_ok(683)
> rejected user nobody:3004-302 Your account has expired; please see
>the system administrator.
>
>Now... my question: Why? What does the W2K client do that triggers
>this barrage of rejected authentications of a user 'nobody' (that is
>clearly not allowed to enter)?
>
>More importantly, is there a way to configure the W2K client to *not*
>waste time on these unrequested/unallowed accesses?

Have you asked in a Samba support area? Have you configured the
security accounts correctly?

Jeff

jcochran.nospam@naplesgov.com (Jeff Cochran) wrote in message news:<404db5f0.1188755960@msnews.microsoft.com>...
> On 25 Feb 2004 06:11:21 -0800, linuxlover992000@yahoo.com (Linux
> Lover) wrote:
>
> >Desperate to find out why connecting to a samba share (on an AIX
> >server) from W2K is so slow, I tried connecting to the same share from
> >a Linux box, using smbclient:
> >
> >smbclient \\\\aixserver\\sharedir$ -U lynn
> >
> >The results were amazing. The connection was so MUCH FASTER then
> >connecting from a W2K (pro) workstation:
> >
> >\\aixserver\sharedir$ (in the Start|Run edit box)
> >
> >
> >When I examined the samba log files on the server, I could see why.
> >
> >The log file for the Linux client contained a single entry:
> >
> >[2004/02/23 11:55:35, 1] smbd/service.c:make_connection(636)
> > linuxbox (192.168.0.4) connect to service sharedir$ as user lynn
> >(uid=21776, gid=1) (pid 125438)
> >
> >So clean, so elegant, so beautiful!
> >
> >OTOH, the log file for the W2K client contained an entry similar to
> >the above, but was immediately followed by about 30 messages of the
> >form:
> >
> >[2004/02/23 11:59:03, 0] smbd/password.c:user_ok(683)
> > rejected user nobody:3004-302 Your account has expired; please see
> >the system administrator.
> >
> >Now... my question: Why? What does the W2K client do that triggers
> >this barrage of rejected authentications of a user 'nobody' (that is
> >clearly not allowed to enter)?
> >
> >More importantly, is there a way to configure the W2K client to *not*
> >waste time on these unrequested/unallowed accesses?
>
> Have you asked in a Samba support area? Have you configured the
> security accounts correctly?
>

Jeff, thanks for your answer. Yes, I asked in comp.protocols.smb. The
folks there are very knowledgeable about Samba, but seem to be
clueless about the W2K *client* side.

I have no reason to believe that I misconfigured the security
accounts, since the problem I described is specific to the W2K client,
and not shared by all connections to the server. Also, the connection
eventually succeeds but it is painfully slow (only from a W2K client).

So, if I re-phrase my question differently: What does a W2K client do
**in addition to connecting to a share**, when asked to connect like
this:

\\aixserver\sharedir$ (in the Start|Run edit box)

In other words, does it also attempt browsing? enumerating all
printers? Connect to a domain controller?

There must be something else that it attempts to do (that is very
specific to W2K and not other SMB clients), but I don't know what it
is.

Thanks,
Lynn