Protocol problems with Win 2000 Server

[Chupaweed]

I have Windows 2000 Server and I have 15 other comps with Windows 95 and they all can see each other and the Server, but the Server can't see anythithing but himself tried every protocol and the only protocol that works it NetBeui

[Lowland]

Don't get too hung up on Protocols - it's probably not your problem!
The fact that NetBuie works should tell you something about how the machines are interpreting their assigned names.

So, you should look at how your network is configured by machine. Remember you have three core parts, Protocal, Service and Client, so check that all are common. For example, File and Print sharing, Client for Microsoft Networks.

Then you need to consider how you machines are looking for addresses. The "preferred" way is for you server to run DHCP (Dynamic Host Configuration Protocol) and get your clients to accept assigned IP addresses. You can anyway try pinging the static addresses from the Server if you don't have DHCP enabled, see what happens. But go DHCP if you can. Then you can set the clients to use DHCP for DNS resolution.
Then shut down the browser capability on the Win95 machines. That's in Network. You want your server to be the master browser, and only use a BDC (back-up domain controller) as back-up.
Make sure your Win 95's have "I want others to share my files and printers" checked.
Then try your server again. W2K server is actually in my opinion, very good. We run win3.1, 95, 98, W2K (NT5) through a NT4Server PDC. This all works fine, even network printing without using a print server, but I can't wait to get around to all W2K and W2K server!

Let us know if more help needed

[Chupaweed]

The thing is that all worked fine before with TCP/IP and IPX then out of the blue that happend, all the comp's can see each other but the server can't see nothing but himself. then I tried every protocol and the only protocol that the server can see all the rest of the computers is with NetBeui

[Lowland]

I would uninstall netbeui and try and ping the other machines from the server, but not seeing the network usually means either some network component is missing or wrongly configured.

If you couldn't see with any protocal, I would suggest that your NIC was Kaput

[kannibul]

check you subnet mask on the server.
make sure it matches your dhcp settings for the clients.
Also make sure you don't have a defualt gateway, unless you are using a router for internet access.

[Chupaweed]

Thanx for the info