>>An indication of why it will not be possible to 'sit' on a version of a Window OS -- support eventually dries up, and apps are written to expect features found only on the most recent WinXX release. That's why we are moving toward a platform independent toolset: Oracle accessed by webpages writting with platform neutral HTML coding. Then it won't matter. We can set on NOVELL and NT4 without being forced to upgrade to W2K, XP or what ever is next. Does that mean we are leaving VFP? Yes, eventually, when we get our Fox apps converted. The network guys tell me that W2K isn't very friendly with Novell, and even with other W2K machines on the net. That I can attest to. My W2K generates frequent allerts telling me that either some other W2K is trying to promote my PC to Master Browser, or my PC is trying to become Master Browser. The network boss says it's happening with all the W2K, and they can't stop it. The Knowledge base describes the problem beautifully, but offers no
>>solution, they say. Anyway, we're taking our 20-30 servers (Novell, NT, W2K) and moving their contents onto two huge boxes running the latest Novell network. It will be interesting to see how bandwidth suffers, if it does...
>
>Hi Jerry,
>
>Can you cite the KB article that describes this problem or the search criteria to locate it? I would be very interested in reading this material since we use Win2K boxes on a Novell network here.
>
>Bill

I've got two kinds of errors in my error logs. The first is one which says that my brower is being forced to become a master brower, but the attempt fails.
The second is my browser trying to gain Master Browser status, but fails.
There are about 175 Master Browser related issues. I'm at home and don't recall the exact messages that are in the error log, but here is one related to the problem I had.

http://support.microsoft.com/support/kb/articles/q227/4/19.asp?id=Q227419&sd=GN&fr=0&ln=EN-US