I have 2 computers: Windows 2000 Prof & Windows 2000 Server. Initially, I linked both the computers using TCP/IP and NETBIOS with a common network id and has given each a IP address. I, then, shared a folder on the server and the client PC was able to view the documents in it. This works fine. Lately, I promoted the stand-alone Windows 2000 Server to a domain controller. I succeeded in linking the client PC to the domain controller and both was on the same domain. I, then, went on to do some further testing. My aim is to prevent the client PC from connecting to the domain controller, once I have changed it back to a WORKGROUP. My problem is this: I changed the client PC back to a WORKGROUP called DUMMY, while the Server is left to be a domain controller with the domain name called TEST. Both have different network id (server: 255.0.0.0, client: 255.255.255.0) and ip address. Since both are on separate network and the client is not "linked" to the domain controller (as it is now in a WORKGROUP). Why am I then, still able to view the shared folder on the server from the client PC ??? Likewise, when I share a folder on the client PC, I can map to the folder from the server ??? Please help.

Just because you have a different subnet mask doesn't necessarily mean the two machine wont be able to communicate. It depends what IP you gave it. For example if PC1 has a mask of 255.0.0.0 with an IP of 192.168.0.1 and PC2 has a mask of 255.255.255.0 and an IP of 192.168.0.2, those two computers will probably still communicate just fine. If you want to really test it, give the other machine and IP of 10.10.10.10 and see what happens.

It shouldn't really matter if it can view it or not. If you use the correct permissions on the server they can't access anything. And I'm not even sure what you are trying to accomplish..... You should either use a domain, or use workgroups (server can be installed and use like a workstation and not be a DC).....