server not accessable

I've got a server that had to be wiped and reinstalled. This servers only
purpose is to house data, and it's got a share on it that all the machines
acquire their data on.

When the server was reinstalled and put back online all 2000 and XP machines
could get to the share. Unfortunately the windows 98 machines can't.

I can log into the network on these windows 98 machines, see and access
shares on the network, but I can't access a share on this particular server
it says that the machine is not accessable.

It's very odd because I can ping it by the server name and it responds back,
I can see the server in windows explorer, but still get the same error "Not
accessable".

From a command prompt I type \\servername\sharedfolder and I get error 53.

I installed the DSClient on these machines, but that didn't change anything.


What am I missing here?

Maybe your freshly installed Win2K is a memeber of an AD in native mode
or maybe you selected not to support legacy clients when installing?

See what I'm getting at? Win9x can't do kerberos authentication even
with dsclient installed.

BoB

Penny wrote:
> I've got a server that had to be wiped and reinstalled. This servers only
> purpose is to house data, and it's got a share on it that all the machines
> acquire their data on.
>
> When the server was reinstalled and put back online all 2000 and XP machines
> could get to the share. Unfortunately the windows 98 machines can't.
>
> I can log into the network on these windows 98 machines, see and access
> shares on the network, but I can't access a share on this particular server
> it says that the machine is not accessable.
>
> It's very odd because I can ping it by the server name and it responds back,
> I can see the server in windows explorer, but still get the same error "Not
> accessable".
>
> From a command prompt I type \\servername\sharedfolder and I get error 53.
>
> I installed the DSClient on these machines, but that didn't change anything.
>
>
> What am I missing here?

I didn't do the actual install myself. How can I turn the legacy support on
if the person who did the install unknowingly selected not to support legacy
clients?

"Bengt Bergholm" wrote:

> Maybe your freshly installed Win2K is a memeber of an AD in native mode
> or maybe you selected not to support legacy clients when installing?
>
> See what I'm getting at? Win9x can't do kerberos authentication even
> with dsclient installed.
>
> BoB
>
> Penny wrote:
> > I've got a server that had to be wiped and reinstalled. This servers only
> > purpose is to house data, and it's got a share on it that all the machines
> > acquire their data on.
> >
> > When the server was reinstalled and put back online all 2000 and XP machines
> > could get to the share. Unfortunately the windows 98 machines can't.
> >
> > I can log into the network on these windows 98 machines, see and access
> > shares on the network, but I can't access a share on this particular server
> > it says that the machine is not accessable.
> >
> > It's very odd because I can ping it by the server name and it responds back,
> > I can see the server in windows explorer, but still get the same error "Not
> > accessable".
> >
> > From a command prompt I type \\servername\sharedfolder and I get error 53.
> >
> > I installed the DSClient on these machines, but that didn't change anything.
> >
> >
> > What am I missing here?
>