I support my church's 13 PC's in a peer network. A Win2KPro machine functions as a file server. One workstation is Win2KPro and all the rest are Win98.Slow performance opening files on workstations from the 'server' has been a problem. It can take 30 second, a minute, or more to open a small Word document. This is a problem some times and not others.
Just today I got the idea from another discussion thread on this site that a poorly-performing home-made cable from the 'server' to the hub could be the cause. I replaced it with a professionaly-made cable and the small amount of testing I have done looks very promising.
Now I read your comments here about the registry change and will be trying that. Your impressions, please, about whether the performance problem I describe could be helped by your suggestions, or are you really touching on something totally different?
Thanks.
>Slow network browsing on 98/ME is
>due to Win2K. Delete this
>registry key on your Win2K
>machine:
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr
>entVersion\Explorer\RemoteComputer\NameSpace\{D627
>7990-4C6A-11CF-8D87-00AA0060F5BF}
>
>By deafualt, Win2K is always searching
>for scheduled tasks on any
>machine you network to. Deleting
>this key stops Win2K from
>doing that. It solved my
>problem of taking nearly a
>full minute to connect to
>my WinME machines.
>
>For file copying, I use IPX/SPX
>exclusively for file sharing (TCP/IP
>is only used for internet)
>and those long copies went
>away. Perhaps someone can shed
>some light on why TCP/IP
>takes forever to copy between
>9X and 2K machines.
