networking questions

  • Thread starter Thread starter Vic
  • Start date Start date
V

Vic

In the home setup here, the network runs rather smoothly and quickly
with one exception. Before explaining the exception let me preface with
the following. When on the tower PC I can enter, RUN \\laptop and
virtually instantly the shared drives pop up, and visa versa.

The exception occurs when accessing the NETWORK in Explorer. When the
workgroup is clicked it seems explorer grinds for a while (27 sec.)
before networked computers show up. Does any body know why this s-l-o-w
retrieval? Does anybody know how to speed it up? Seems odd explorer
would be so slow when drives pop up almost instantly from a command
prompt!

Thanks
 
Vic wrote:
> In the home setup here, the network runs rather smoothly and quickly
> with one exception. Before explaining the exception let me preface
> with the following. When on the tower PC I can enter, RUN \\laptop
> and virtually instantly the shared drives pop up, and visa versa.
>
> The exception occurs when accessing the NETWORK in Explorer. When
> the workgroup is clicked it seems explorer grinds for a while (27
> sec.) before networked computers show up. Does any body know why
> this s-l-o-w retrieval? Does anybody know how to speed it up? Seems odd
> explorer would be so slow when drives pop up almost
> instantly from a command prompt!

Seems like normal to me. When you map a drive share from the command
prompt:

net use x: \\server\sharename

It merely does what you tell it - which is one thing.

When y9ou open up the GUI, it has all those background actions it is also
taking. Looking for more shares, looking for file types and how to display
them, looking for file attributes, etc.

Just create some batch script to map the shares you wish to from now on and
run it and then open my computer/windows explorer to get to what you want.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
 
Vic,

What if you do theis?

\\laptopname\

Do you see the shares immediately?

--
Newbie Coder
(It's just a name)


"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:u6B0YciOIHA.5988@TK2MSFTNGP02.phx.gbl...
> Vic wrote:
> > In the home setup here, the network runs rather smoothly and quickly
> > with one exception. Before explaining the exception let me preface
> > with the following. When on the tower PC I can enter, RUN \\laptop
> > and virtually instantly the shared drives pop up, and visa versa.
> >
> > The exception occurs when accessing the NETWORK in Explorer. When
> > the workgroup is clicked it seems explorer grinds for a while (27
> > sec.) before networked computers show up. Does any body know why
> > this s-l-o-w retrieval? Does anybody know how to speed it up? Seems odd
> > explorer would be so slow when drives pop up almost
> > instantly from a command prompt!
>
> Seems like normal to me. When you map a drive share from the command
> prompt:
>
> net use x: \\server\sharename
>
> It merely does what you tell it - which is one thing.
>
> When y9ou open up the GUI, it has all those background actions it is also
> taking. Looking for more shares, looking for file types and how to display
> them, looking for file attributes, etc.
>
> Just create some batch script to map the shares you wish to from now on and
> run it and then open my computer/windows explorer to get to what you want.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
 
Under Tools | Folder Options.. | View tab | is the Automatically Check for
Network Files and Folders box checked? (Top box under Advanced Settings:,
Files and Folders)

"Vic" wrote:

> In the home setup here, the network runs rather smoothly and quickly
> with one exception. Before explaining the exception let me preface with
> the following. When on the tower PC I can enter, RUN \\laptop and
> virtually instantly the shared drives pop up, and visa versa.
>
> The exception occurs when accessing the NETWORK in Explorer. When the
> workgroup is clicked it seems explorer grinds for a while (27 sec.)
> before networked computers show up. Does any body know why this s-l-o-w
> retrieval? Does anybody know how to speed it up? Seems odd explorer
> would be so slow when drives pop up almost instantly from a command
> prompt!
>
> Thanks
>
>
>
 
Yes, that what I tried saying in the first post. ALL share popup
immediately when I enter
\\laptop but the shares take almost half-a-minute to showup in Explorers
NETWORK branch.

BTW: I've researched this and removed the namespace entries for printers
and tasks. That was many moons ago ... made a nice improvement to
network speed. Now I'm trying to improve Explorers displaying of
networked computers.

Lastly, files transfer speeds are good.
___
"Newbie Coder" <newbiecoder@spammeplease.com> wrote in message
news:uUIZKLnOIHA.3816@TK2MSFTNGP04.phx.gbl...
> Vic,
>
> What if you do theis?
>
> \\laptopname\
>
> Do you see the shares immediately?
>
> --
> Newbie Coder
> (It's just a name)
>
>
> "Shenan Stanley" <newshelper@gmail.com> wrote in message
> news:u6B0YciOIHA.5988@TK2MSFTNGP02.phx.gbl...
>> Vic wrote:
>> > In the home setup here, the network runs rather smoothly and
>> > quickly
>> > with one exception. Before explaining the exception let me preface
>> > with the following. When on the tower PC I can enter, RUN \\laptop
>> > and virtually instantly the shared drives pop up, and visa versa.
>> >
>> > The exception occurs when accessing the NETWORK in Explorer. When
>> > the workgroup is clicked it seems explorer grinds for a while (27
>> > sec.) before networked computers show up. Does any body know why
>> > this s-l-o-w retrieval? Does anybody know how to speed it up? Seems
>> > odd
>> > explorer would be so slow when drives pop up almost
>> > instantly from a command prompt!
>>
>> Seems like normal to me. When you map a drive share from the command
>> prompt:
>>
>> net use x: \\server\sharename
>>
>> It merely does what you tell it - which is one thing.
>>
>> When y9ou open up the GUI, it has all those background actions it is
>> also
>> taking. Looking for more shares, looking for file types and how to
>> display
>> them, looking for file attributes, etc.
>>
>> Just create some batch script to map the shares you wish to from now
>> on and
>> run it and then open my computer/windows explorer to get to what you
>> want.
>>
>> --
>> Shenan Stanley
>> MS-MVP
>> --
>> How To Ask Questions The Smart Way
>> http://www.catb.org/~esr/faqs/smart-questions.html
>>
>>
>
 
No, just checked and that box is not checked. Would checking it improve
things?
__
"Script" <Script@discussions.microsoft.com> wrote in message
news:805999D6-9A86-4538-A58D-CE09F47AB074@microsoft.com...
> Under Tools | Folder Options.. | View tab | is the Automatically Check
> for
> Network Files and Folders box checked? (Top box under Advanced
> Settings:,
> Files and Folders)
>
> "Vic" wrote:
>
>> In the home setup here, the network runs rather smoothly and quickly
>> with one exception. Before explaining the exception let me preface
>> with
>> the following. When on the tower PC I can enter, RUN \\laptop and
>> virtually instantly the shared drives pop up, and visa versa.
>>
>> The exception occurs when accessing the NETWORK in Explorer. When the
>> workgroup is clicked it seems explorer grinds for a while (27 sec.)
>> before networked computers show up. Does any body know why this
>> s-l-o-w
>> retrieval? Does anybody know how to speed it up? Seems odd explorer
>> would be so slow when drives pop up almost instantly from a command
>> prompt!
>>
>> Thanks
>>
>>
>>
 
Back
Top