Win 98 Client issues... Slow logins and shares not showing up

I tried connecting to a Win 2K3 server from a windows 98
workstation. I too cannot get the home folder (we use Z
to map or show up on Win 98 . It does map on Win XP.

I mapped another drive in the login script to the home
folder. THen I set the permissions so that even though
every user can see all home folders, they can only enter
their own.

Not the best solution admittedly but it works until a
better one comes along.


>-----Original Message-----
>I have a windows 98 client machine running under a W2k3
server with
>AD. When I login on the client, everything works
properly, except I
>can not find the home directory, (It's mapped
automatically on a XP
>client as the G:\ drive), nor view anything on the
network (which I
>can see a mapped directory normally on a XP client). I
have installed
>the DSClient (AD client extensions) for Windows 98 from
a Windows 2000
>Server CD . On the server the share is named File$...
so it looks
>like this:
>\\bluffton-1\File$\username
>
>the share is published in AD as: File$
>
>The Windows 98 client also takes about a minute to
finally make a
>connection, while in XP it only takes a few seconds.
Why is there
>such a difference between login times?
>
>Does anyone have a workaround, or possible ideas to my
problem???
>Would WINS be a possible solution??? Or something
else???
>
>Basically, what I am asking, can I map a drive to a
subfolder in a
>share in a Windows 98 Client, or even (the worst
possible scenario)
>map the share and allow a user to only see a subfolder
they have
>access (and rights) to, and not some other user's folder
in the share?
> Any help would be greatly appreciated.
>
>- James Haynes
>- (E-Mail Removed)
>.
>

Windows 9x clients can not do nested mapping to shares. You can not
map to
\\servername\share\folder

You can only map using

\\servername\share

For our 98 clients I have had to share every users home folder
seperately until I have them all on Windows 2000/XP.