slow network browsing

F

FPS, Romney

Hi all,
Problem 1:
I just added a Windows 2000 Pro SP4 machine to our LAN. It can access the
internet. It has a shared folder which can be accessed from other computers.
It has a mapped network drive which accesses files on the mapped drive
quickly. However, it takes approximately 30 seconds to see shared files on
other computers when I use My Network Places or Windows Explorer. All
computers, including this one, are part of the same workgroup. This
particular computer can quickly navigate to our workgroup and display icons
for each computer on the network, but when I double-click a particular
computer icon, it takes 30 seconds or so for the shared files to appear.
(the nifty little flashlight appears).

Like all the other computers, this Win 2000 machine has "Obtain an IP
address automatically" checked, as well as "Obtain DNS server address
automatically" -- under TCP/IP properties. The advanced TCM/IP setttings are
also the same.

Problem 2:
While I'm at it, a similar, but even more confusing problem occurs on a
Windows XP Pro machine: it quickly displays shared files on computers A, B,
C, but takes about 30 seconds to display shared files on Computer D (a
Windows XP Home Edition). Other computers, however, on the network (XP Pros
and Win 98 quickly display the shared files on Computer D.

Thanks for any help,
Mark
 
C

crazyal12

Hi all,
Problem 1:
I just added a Windows 2000 Pro SP4 machine to our LAN. It can access the
internet. It has a shared folder which can be accessed from other computers.
It has a mapped network drive which accesses files on the mapped drive
quickly. However, it takes approximately 30 seconds to see shared files on
other computers when I use My Network Places or Windows Explorer. All
computers, including this one, are part of the same workgroup. This
particular computer can quickly navigate to our workgroup and display icons
for each computer on the network, but when I double-click a particular
computer icon, it takes 30 seconds or so for the shared files to appear.
(the nifty little flashlight appears).

Like all the other computers, this Win 2000 machine has "Obtain an IP
address automatically" checked, as well as "Obtain DNS server address
automatically" -- under TCP/IP properties. The advanced TCM/IP setttings are
also the same.

Problem 2:
While I'm at it, a similar, but even more confusing problem occurs on a
Windows XP Pro machine: it quickly displays shared files on computers A, B,
C, but takes about 30 seconds to display shared files on Computer D (a
Windows XP Home Edition). Other computers, however, on the network (XP Pros
and Win 98 quickly display the shared files on Computer D.

Thanks for any help,
Mark
 
C

crazyal12

(e-mail address removed) wrote: have you got any persanel firewalls that
might be blocking it or slowing it down
 
K

Kurt

Are the files shared to user accounts or are you using the guest account? My
first guess is that you are trying to authenticate using your logon
credentials, and when that fails, falling back to the "guest" access.

....kurt
 
F

FPS, Romney

Beats me, Kurt. You're probably on the right track, but I don't know enough
to understand your question completely. The Windows 98 machine simply has
the folder shared with full privileges. The 2000 machine takes as long to
read this folder as it does any of the XP machines. The 2000 machine logs on
with Administrators, Guests, and Users privileges. (I had added all three to
see if that made a difference -- which it didn't).

I think I've screwed things up somewhere along the way when I initially
tried to set up this machine for the network. I had erroneously listed the
Workgroup name as "Workgroup". I later went through the Wizard again and
changed it to the correct Workgroup name. For awhile, however, when I logged
onto the website for our modem/router, the 2000 computer was still listed as
part of "Workgroup", instead of the correct name. I've rebooted the
modem/router, and then restarted the 2000 computer, and now the 2000
computer's "domain" name on the website is listed as "Unkown". The other
computers listed on the website have the correct Workgroup name listed for
"domain" name. [We don't actually have "domains", we're just part of the
same Workgroup].

I think that even though I changed the Workgroup name to the correct one,
this did not completely eliminate the initial incorrect Workgroup name. When
I check My Computer/Properties/ Network Identification, it lists the correct
Workgroup name. The Properties button of Network Identification has
Workgroup checked and not Domain.

Further suggestions would surely be appreciated.
Thanks,
Mark
 
F

FPS, Romney

Thanks for the response.
Does Windows 2000 Pro *have* a firewall? ... I can't find it. I know the
other computers on the network don't have a firewall turned on, including
the Widows 98 machine.
 
F

FPS, Romney

Kurt,
I log on to this computer with the same account name and password that other
users use on their computers. When other users log on to their computers
with this same username/password, they have no difficulty immediately
viewing the contents of shared folders across the network, including the
shared folder on this Win2000 computer.

On this Win2000 computer, however, it takes 30 seconds to view the contents
of shared folders on the network. Once the folder is in view, I can copy,
delete, etc.

Would sure appreciate some additional help.
Thanks,
Mark
 
M

Mark

Many thanks, Airman Thunderbird. I'll give that a try tomorrow at work.
Mark

Airman Thunderbird said:
The problem (with no solution) is mentioned here

http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP

On my Win2k machine deleting this registry key fixed it for me with no
noticable side effects.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Remot
eComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"


Kurt,
I log on to this computer with the same account name and password that other
users use on their computers. When other users log on to their computers
with this same username/password, they have no difficulty immediately
viewing the contents of shared folders across the network, including the
shared folder on this Win2000 computer.

On this Win2000 computer, however, it takes 30 seconds to view the contents
of shared folders on the network. Once the folder is in view, I can copy,
delete, etc.

Would sure appreciate some additional help.
Thanks,
Mark
 
M

Mark

Just wondering ...
There must have been a time when there were a lot of Win2000 machines being
added to peer-to-peer networks. Why was this not a *major* problem? What is
unique about our two machines? And, why was this not fixed by SP4?
.... any thoughts?
Mark

Airman Thunderbird said:
The problem (with no solution) is mentioned here

http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP

On my Win2k machine deleting this registry key fixed it for me with no
noticable side effects.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Remot
eComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"


Kurt,
I log on to this computer with the same account name and password that other
users use on their computers. When other users log on to their computers
with this same username/password, they have no difficulty immediately
viewing the contents of shared folders across the network, including the
shared folder on this Win2000 computer.

On this Win2000 computer, however, it takes 30 seconds to view the contents
of shared folders on the network. Once the folder is in view, I can copy,
delete, etc.

Would sure appreciate some additional help.
Thanks,
Mark
 
M

Mark

Airman Thunderbird,
I'm also wondering if it could be the particular network adapter/driver that
contributes to, or creates this problem. This particular Dell came with a
CNET Pro200WL card.
Mark

Airman Thunderbird said:
The problem (with no solution) is mentioned here

http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP

On my Win2k machine deleting this registry key fixed it for me with no
noticable side effects.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Remot
eComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"


Kurt,
I log on to this computer with the same account name and password that other
users use on their computers. When other users log on to their computers
with this same username/password, they have no difficulty immediately
viewing the contents of shared folders across the network, including the
shared folder on this Win2000 computer.

On this Win2000 computer, however, it takes 30 seconds to view the contents
of shared folders on the network. Once the folder is in view, I can copy,
delete, etc.

Would sure appreciate some additional help.
Thanks,
Mark
 
A

Airman Thunderbird

The registry change worked with several sets of hardware at the time I
implemented it.
Airman Thunderbird,
I'm also wondering if it could be the particular network adapter/driver that
contributes to, or creates this problem. This particular Dell came with a
CNET Pro200WL card.
Mark

Airman Thunderbird said:
The problem (with no solution) is mentioned here

http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP

On my Win2k machine deleting this registry key fixed it for me with no
noticable side effects.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Remot
eComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"
 
A

Airman Thunderbird

When 2k was first launched, it was a major problem, the newsgroups were
full of it.
 
M

Mark

Airman Thunderbird, you're probably the person who might know the answer to
this other problem on the Win2000 machine. I don't know if it could be
related to the same issue, but our web-based router utility program fails to
list the correct workgroup name of this computer -- listing it's workgroup
name as "unknown". It also identifies this as a Windows 98 OS, and when I
first hooked it up to the network, listed it as a Linux OS. All the other
computers are listed correctly on this web-based program.

The computer itself lists the correct workgroup name (My
Computer/Properties/Network Identification), and when viewed from other
computers it shows up in the correct workgroup. Obviously, some missing or
bad data is being sent to the router.

Thanks for any insight into this second problem. It's not as crucial (I
guess) as the first problem, which you provided a solution for. Thanks
again.
Mark
 
F

FPS, Romney

Airman Thunderbird,
I deleted the Registry key and now it only takes 15 seconds to display the
shared folders after I click on the computer icon within the workgroup. When
I click on the actual shared folder, it immediately displays the results. If
I then click on the computer icon again, the flashlight comes on and it
takes another 15 seconds before the flashlight goes off.

I guess this is about as good as it gets for this combination of Win2000,
and CNET Pro200WL adapter.

I've just noticed, however, that it makes a big difference how I try to
access the contents of the shared folder.

1) If I take the long way via: My Network Places/Entire Network/Microsoft
Windows Network/WorkgroupName/ComputerName/SharedFolder, then it takes 15
seconds (now after the Registry change) each time I click on ComputerName
before I can access the contents of the shared folder.

2) If the SharedFolder is present in the window immediately after I click on
My Network Places, then there is no delay in viewing the contents of the
SharedFolder. I simply click on the folder and there are the contents.

Only two of the five computers/shared folders were present when I first
click on My Network Places. Once I manually added the other computers/shared
folders using "Add to Network Places", the folders and contents were
immediately viewable after clicking My Network Places.

I don't know why only a couple of the computers/shared folders were added
automatically on the Win2000 machine, and why I had to added the others
manually. This is the first time I've ever used "Add to Network Places".

I admit, I've been spoiled by the Win98 machine which I normally work at. On
that machine, there's no delay regardless of which route I take in viewing
shared folders across the network. Anyhow, if I take the time to manually
add all the shared resources via "Add to Network Places", then I shouldn't
experience any future delays when I need to browse for shared folders.

Hope this note makes sense.
Thanks for your help,
Mark

Airman Thunderbird said:
The problem (with no solution) is mentioned here

http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP

On my Win2k machine deleting this registry key fixed it for me with no
noticable side effects.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Remot
eComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"


Kurt,
I log on to this computer with the same account name and password that other
users use on their computers. When other users log on to their computers
with this same username/password, they have no difficulty immediately
viewing the contents of shared folders across the network, including the
shared folder on this Win2000 computer.

On this Win2000 computer, however, it takes 30 seconds to view the contents
of shared folders on the network. Once the folder is in view, I can copy,
delete, etc.

Would sure appreciate some additional help.
Thanks,
Mark
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top