Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
It takes about 30 seconds for Windows 2000 to display the computers connected to my network in explorer. My network consists of a 2000 computer and a laptop running 98SE. I can access all my files on the 2000 computer quickly from the 98SE computer but not the other way around. Also, I should note that my 2000 computer is assigned a static ip address by Microsoft 2000's internet connection sharing feature and the 98SE is using DHCP to obtain its IP. It seems to me that I can access my 98SE computer much more quickly when the 2000 computer is not connected to the internet than when it is connected. Anyone have any suggestions or insights?
W2KP is trying to use DNS first. When the DNS request fails then it will look for WINS. Are you running NetBEUI on both? One workaround is to assign a static IP to the W98SE and use 192.168.0.1 as the gateway IP. If this doesn't speed things up, install a LMHOSTS file on the W2KP.
0 
If I assign a static IP to my W98SE, will I still be able to share internet connection on my W2KP machine?
0
my win2K -> win9x networking blows as well. i can get the network neightborhood list up quick enough, but when i click on a computer, it takes *FOREVER* to get a list of shared resources on that computer, even if i just had it open a few seconds prior. opening a shared resource is quick enough (not as fast as win9x though) and shortcuts to shared resources are good as well. file transfers seem to happen at full speed.
i have tried many different protocol combinations and orders with no luck.
i am the only win2k box on the network so i don't know about win2K -> win2K speed.
i was *REALLY* hoping SP1 would fix this but it made no difference at all.
i'm using a 3Com 905b
0
I'm so frustrated with this problem. I think it is a flaw in WinNT and Win2K and nobody wants to admit it. I have checked numerous sites on this issues over a period of months, I have also tried everything possible - none of it worked!
0
Boy I'm glad I came to this forum! I have been digging around for days trying to figure this out. I'm running a windows 2k server, with 2 windows 98se clients. The 98SE machines can surf shared resources like they're local drives, however the windows 2k machine is very slow when surfing shared resources.
At first it took roughly 30 seconds for the shared resources to pop up... I've got it down to about 5 or 6 seconds (still much slower, but tolerable) by adding all of the machines to my firewall's local zone. (I've tried removing the firewall altogether, and this hasn't helped or harmed at all).
If anyone has any info, please post!
-Brian
0
Any solutions yet? I'm having exactly the same problem. We have a network in our student flat. I'm running W2K and the other four computers are running Win95/98. They can access everything really quickly, even on my computer but when I try to browse the network with W2K it is VERY VERY slow. What the f$^k?
A little more info: we're using new NIC's but using BNC cabling etc. I'm off to the MS site to trawl through more info to see if i can find a solution.
0
I found the problem. Using the top of this message I did a search at Microsoft.com and found this:
http://support.microsoft.com/support/kb/articles/Q245/8/00.ASP
Unfortunately there is no fix... blargh...
0
I FOUND A FIX!!! I FOUND A FIX!!!
I did some searching on Dejanews and found the fix. Use Regedit and delete the following key from your registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="Scheduled Tasks"I did it and have NO MORE WAITING! Woohoo!
0
WoOoOOoo HoOOooOo!! It works IT WORKS!! I am very impressd at the speed now. Although I don't know of any future complications though :)
THANK YOU!!
0
I was having the very same problem. I removed Netbeui and enabled Netbios over TCP/IP on My Windows 2K box. No more waiting and I still have full IP functionality!
0
I have a slightly different problem that i cannot figure out. While browsing the network through windows 2000 explorer, accessing our file server can take from 5 to 20 seconds to open its contents. Then the same amount of time opening up each folder. This only happens on some computers, not all. Some computers are quite fast while using windows explorer. I have not seen any explainations on this. I tried the fix of deleting a registry key in the remotecomputer/namespace subkey. I am lost now. Any suggestions would help.
0
The Fix works !
But you have to delete the whole folder {D6277990-4C6A-11CF-8D87-00AA0060F5BF}
0
Hey guys,
I've got windows 2000 professional installed. Every time I open up inet explorer, it freezes up for about 20 seconds. I also have the problem where browsing other cpu's on the network is slow. I've tried deleting {D6277990-4C6A-11CF-8D87-00AA0060F5BF}
But that didn't do too much, although I do appreciate all the help everyone gives.
Can anyone help me out?? I've been trying to fix this for almost a year!! And I'm not about to re-install everything.. dammit! hehe
Thanks in advance
-Ryan
0
I exported the key mentioned above to no avail :-( Anyone else have any other suggestions? We've got quite a few 2000 machines around our office and they all have the same problem browsing the network. I might add that we also have Novell running as well and I seem to be able to browse the Novell servers just fine. Odd!
0
One simple fix worked here on our network.
We've been having trouble with the initial opening of a file in Word or Excel - after you click the down arrow to browse to another drive there is a long wait. I've tried various "fixes" and finally found one that sorta works...
Go into the Display Properties and then to the Effects tab. Uncheck all the boxes.
This seems to have resolved the issue of slow browsing here. Go Figure.
Please let me know if anyone else finds this to be of help. I'm curious if this is an actually solution or if the problem will crop up again.
Thanks!
0
I have had an issue with Win2K from the outset, each time thinking the next SP will fix slow/er file access than NT4. Having read the above solutions with interest I am interested to see if there is any more feedback. My grumbles are that Explorer seems slower accessing drives on a Novell NW5 server, Searches in Explorer take longer. If you make the mistake of highlighting files that are found in your searh and select properties.... You wait a long time with sometimes no results!
NT4 no problem. No one seems to want to admit to this problem!!Mark
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
