peer to peer (W2K)

[freqdoc]

Just installed Win2k and am new to it. I have a home network of win2k, win me, win 98, and linux. All computers can see and share to each other except for the win2k computer which no one can find. However, all computers can ping the win2k computer, and the win2k computer can ping all others. When I click on 'Entire Network' in my network places I get 'network not present or not started' Can someone please help me and forgive my newbieness? BTW, the win 2k computer accesses the Internet through my router just fine as well.

Thanx

Ric

[Phaedrus]

Sounds to me like file system incompatibility. Is it possible that you have installed Win2K on an NTFS drive, while the other systems are running on FAT32? If so, the FAT32's won't see the NTFS files, although Win2K running on NTFS will see the FAT32's.

P

<P ID="edit"><FONT class="small">Edited by Phaedrus on 07/21/02 22:36.</FONT></P>

[BertImmenschuh]

The file system/hard drive formatting only matters to the computer the drive is in. You can have a FAT16 and a FAT32 and an NTFS and even a Macintosh computer communicating with the server with no problem, except the Macintosh may need a file convertor/translator to work in a program. There's countless Win95/98/ME computers that can't use NTFS working on WinNT/2000 networks. And WinNT can't use FAT32.

[freqdoc]

Yes, win2k is nfts and winme is fat32, but I can't even get that far. Win2k reports 'network not present or not started', when I click on the 'entire network' icon. I never even see the other computers period. This is supposed to be a peer to peer network with no dedicated server. Thanks for the reply though!

Ric

[Phaedrus]

Maybe WinNT can't, but Win2K can, and does.

You have a good point in that the other nodes should be visible, irrespective of file format but I don't think I've been able to read files on an NTFS-formatted drive in Win98 or ME without installing an additional driver specifically made for the purpose.

I wonder whether his network protocols and/or bindings might be the problem. The fact that the Win2K machine can't see the network might be the biggest clue to solving the problem. Get it to see the rest of the network, and I suspect everything else will fall into place (assuming correct protocols and bindings). I would suggest trying NetBEUI as a common protocol, and binding everything (services and adaptors) to everything else through it and then start finding what does and doesn't see whatever else. Of course, this would be a test configuration only, and would need to be changed to go on-line.

P