Tracy,

With your experience in security, I should have expected a detailed response. *grin*

Personally, I don't really care what machines show up in Network Neighborhood, and the fewer machines that have sharing enabled on the network, the better.

>I understand what you are saying here, but I believe the reason for the problem is due to the differences in native protocols in the OS. Win98 uses NetBios names for network communications and Windows 2000 uses DNS over IP. It is due to security reasons that Windows 2000 does not communicate over NETBIOS by default. In order for all his Win98 to communicate with all network resources, he could install the Windows Name Service (WINS) on the Windows 2000 server in the Windows 2000 network (make it also a WINS server). Then Windows 2000 would build a list of registered NetBios names to enable users to locate computers via browsing the neighborhood because the netbios name would be resolved to an IP adress. This is not typically recommended in a W2k network for security reasons, but it is just as secure as his existing Win98 network in a sense.
>
>Tracy
>
>>Tracy,
>>
>>I don't think it is really security; it is for organizational purposes when browsing the "Network Neighborhood."
>>
>>Machines from different workgroups can connect to shared resources, you just need to know the name of the computer you want to connect to.
>>
>>Ounis, to see what I mean, from the Win98 machine you can go to Start|Run and type \\servername (use your server's name, of course), and you will should the server, regardless of the workgroup you have given to the Windows 98 machine.
>>
>>>It is designed to be this way. It is security. However, with Win98 clients, it is a hetereogenous network.
>>>