File Takes an Unexpectedly Long Time to Open Through SMB Protocol

[Heber Soto]

I am expericing trouble with new machines running XP
proffesional when they open a file from the server the
first time it takes a long time doing so, after they work
fine. I found in the MS Knowledge Base an article that
metion this (Microsoft Knowledge Base Article - 812513)
in this article it mentions that there is a fix for this
but it dosent tells me where the file is located.
Anybody knows what fix this is?

[Matt DuBois [MSFT]]

The fix for the issue described in article 812513 is included in Sp1. My
guess as to the cause of your problem is that the XP machines are having a
hard time resolving the name of the server. Once it does that the first
time, it caches the mapping so it doesn't take as long for subsequent
accesses. An XP client should be configured with ONLY the DNS server for
your domain, and not any other DNS servers. Your domain DNS server should
be configured with a DNS forwarder so that client machines can resolve
internet names as well as intranet names. For instructions on how to
configure a DNS forwarder, see the "How to Configure Forwarders" heading in
the following article:

[url]http://support.microsoft.com/?id=323380[/url]


As a side note: If you are ever in doubt as to whether a given update is
already on your computer, look at the section of the article that describes
the files that changed. If all of the files on your computer are the same
date, or newer, than the files in the article, then you should already have
that fix installed.

--
This posting is provided AS IS with no warranties, and confers no rights.


"Heber Soto" <heber_soto@yahoo.com> wrote in message
news:03d601c34bd7$88607320$a301280a@phx.gbl...

> I am expericing trouble with new machines running XP
> proffesional when they open a file from the server the
> first time it takes a long time doing so, after they work
> fine. I found in the MS Knowledge Base an article that
> metion this (Microsoft Knowledge Base Article - 812513)
> in this article it mentions that there is a fix for this
> but it dosent tells me where the file is located.
> Anybody knows what fix this is?
>
>
>