Discussion Locked

win 98 clients can't see shared folder

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently installed and set up an NT server NT 4 with sp 6. Everything seemed fine except win 98 clients cant see a shared folder. Win 2000 clients CAN the shared folder without any probs. It's nothing to do with rights, I'm sure of that.
What iswrong?

13 replies

by addison99

Can the Win 98 PC's see the server.

But I am presuming that if you can it wont let you access the drive.

If this is the case I will be down to access rights.

by drew_lgca

If you go to the command line and enter the path (\\server\folder\)will it open the folders ? Are the PCs part of a domain or workgroup? What protcols are you using ?

by markring40

Is is just one folder that can't be seen or is it the entire NT Drive that 98 users can't access? With NT and 98 clients you are using different file systems. Win98 can't read NTFS, while you can "go either way" with 2000. You can set up a Win 98hard drive on the NT machine and share that to be backward compatible with your 95 and 98 clients.

by lawrence

No sorry. Win 98 can read NTFS since the same win98 clients can read other ntfs's on another NT server.
Thanks

by markring40

What type of data is in the shared folder? Does that folder possibly contain corrupted data? And you've double-checked the Read Only, Full permissions etc and they are fine. There has to be corrupted data there. Good Luck. Don't spend your Memorial Day weekend loosing sleep over this one. :-)

by uellem

Can you ping the server from the win98 clients? That is, is the server's IP address resolved?

If not, try using lmhosts.

by philando

You said win98 clients cant see a shared folder, which lead me to assume that the client can access other data on the server. If this is true, I'll bet my ga-zoo its a permission problem. Good luck.

by lawrence

Thanks for everyone's help. The answer was so simple. The name of the share folder was too long. When I made it smaller...problem solved...ooops

This discussion is closed to new replies.