A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Networking
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

server not accessable



 
 
Thread Tools Display Modes
  #1  
Old October 20th 05, 08:13 PM
Penny
external usenet poster
 
Posts: n/a
Default 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?
  #2  
Old October 22nd 05, 06:14 PM
Bengt Bergholm
external usenet poster
 
Posts: n/a
Default server not accessable

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?

  #3  
Old October 22nd 05, 06:14 PM posted to microsoft.public.win98.networking
Bengt Bergholm
external usenet poster
 
Posts: 2
Default server not accessable

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?

  #4  
Old October 24th 05, 05:59 PM
Penny
external usenet poster
 
Posts: n/a
Default server not accessable

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?


  #5  
Old October 24th 05, 05:59 PM posted to microsoft.public.win98.networking
Penny
External Usenet User
 
Posts: 30
Default server not accessable

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?


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Configure windows me to connect to folder or file shared by windows 2000 server kamal General 3 December 17th 04 05:56 AM
Configure windows me to connect to folder or file shared by windows 2000 server kamal General 4 December 17th 04 02:59 AM
Regarding Proxy server & firewall Rakesh Roy Networking 0 September 7th 04 03:04 PM
Win 98 client/ NT server issues Andy Networking 0 July 14th 04 04:40 PM
Windows 98 and Windows 2003 Server Lars Wurm Software & Applications 0 July 13th 04 01:27 PM


All times are GMT +1. The time now is 01:00 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.