Win2K & Win98 Networking Problem

[Guest]

This should be a simple problem to correct.
We have a simple peer-to-peer network.
Three computers are running Windows 98, and we just added another computer running Windows 2000.
Each computer has a folder that is shared with full permissions and NO password
Each Win98 computer is set to login with NO password. The Win2K computer logs in to an account with NO password

From the Win2K computer I can access any of the other computers.
From any of the other computers I can see the Win2K computer, but if I attempt to access the resources (shared folder) of the Win2K computer from the Win98 computers I am prompted for a password. And, the share that is defaulted is IPC$. How do I set the default share to the shared folder I want [ C:\Shared ] and it not request a password

Any help would be greatly appreciated

Thanks.

 

[SaltPeter]

This should be a simple problem to correct.
We have a simple peer-to-peer network.
Three computers are running Windows 98, and we just added another computer running Windows 2000.
Each computer has a folder that is shared with full permissions and NO password.
Each Win98 computer is set to login with NO password. The Win2K computer

logs in to an account with NO password.

Thats a misconception, while your Win9x systems operate happily with any or
no account, the W2K operating system requires an account to login, whether
the login is automatic or not. Also, who is logged in at the station is
irrelevent. The system is either up or not.

From the Win2K computer I can access any of the other computers.
From any of the other computers I can see the Win2K computer, but if I

attempt to access the resources (shared folder) of the Win2K computer from
the Win98 computers I am prompted for a password. And, the share that is
defaulted is IPC$. How do I set the default share to the shared folder I
want [ C:\Shared ] and it not request a password?

Any help would be greatly appreciated.

Thanks.

Win9x PCs are share-level operating systems, NT4, W2K and XP are user-level
operating systems. This means that W2K relies on a security provider to
manage access to the resources within. The InterProcess Communication ($IPC)
is a remote procedure call which is prompting for credentials which must
already exist on that system.

In other words, "Bob" can't connect to W2K unless "Bob" has an account
available at the target W2K system (password or no password). Note the
disabled Guest account in W2K (anonymous logons are disabled by default). So
create an account with appropriate rights on W2K to use when you connect to
it.

Then there is the issue of permissions, which may involve the share
permissions to resource and the ntfs permissions depending on what file
system is installed.

 

[Guest]

It never occured to me to setup accounts for the other computers. Thanks for the suggestion. Problem solved.

 

[SaltPeter]

It never occured to me to setup accounts for the other computers. Thanks

for the suggestion. Problem solved.

Wellcome, now you understand why domains have their advantages, since the
security provider in a domain environment encompasses all partcipating
NT-based clients, a single account can be defined to connect to a resouce
anywhere in the domain. Not so with a workgroup.