win2k and win98

korguul

Junior Member
Jun 25, 2001
7
0
0
this is along the lines of the "can win2k talk to winme" discussion posted below. here's my question. i've got win 2k professional on a computer with 2 partitions--one ntfs, one fat32. i can connect to it through the hub with a win98 machine using tcp/ip, but the win 98 machine can only see shares from the fat32 partition on the win2k machine. it can't see the ntfs shares. i know the win98 can't see ntfs partitions locally (in a dual boot situation), but for some reason i thought that the win2k pro machine would allow the win98 machine to see ntfs shares over a network. am i wrong about this?
thanks.
 

nd

Golden Member
Oct 9, 1999
1,690
0
0
You're not wrong about that. The Win98 machine doesn't care what filesystem a share is hosted on. Everything is transparent over the SMB protocol. I'm not sure what the problem is, but it's not directly related to it being a NTFS partition (could be an indirect problem related to it being NTFS though).

Hmm.. my guess would be that it's a security/permission issue. NTFS stores more security related attributes than FAT32, so there's a possible source of the issue.
 

korguul

Junior Member
Jun 25, 2001
7
0
0
ok--more info. i dont think security is the issue, since the ntfs shares are set up with full control for everyone in both the share permissions and the ntfs permissions. also, the win98 machine can see shares if i type the full unc path to the shares in the "run" line.
i installed a trial version of win2k server on another partition and it seems that the win98 machine can see all of those shares regardless of file system. im wondering if smb needs to be installed on the pro partition, or if some settings need to be made to allow the pro machine to "serve up" files on ntfs to win 98 machines. any replies are helpful.
thanks.
 

randal

Golden Member
Jun 3, 2001
1,890
0
76
The "Full Control" thing only applies to local users, IIRC. Find out the username of the win98 machine and make a user on the win2k machine w/ the same user id & password.

Although the run \\unc convention works almost flawlessly, browsing on ms networks is painful. give it at least 1/2 hour of both computers being on before attempting to browse shares.

$.02
randal