Re: Win2K & Win98 Networking Problem

From: SaltPeter (SaltPeter_at_Jupiter.sys)
Date: 04/21/04 

Date: Wed, 21 Apr 2004 02:09:54 -0400

"rtrammel" <anonymous@discussions.microsoft.com> wrote in message
news:441BDBEB-DBC5-4797-BF96-907AD6BB5CF5@microsoft.com...
> 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.

Relevant Pages

  • Re: ADMT/Sidhistory not working
    ... Not unless you are using the account from the old domain. ... you need to grant your "new" groups in the new domain the permissions on the ... permissions to resources in the OLD domain. ... sid history, you are using the old user account, and thus the old sid. ...
    (microsoft.public.windows.server.active_directory)
  • Re: All permissions, access... DENIED???
    ... I recently discovered that the change account details one gets via control ... I am running Windows XP Home Edition Service Pack 2. ... I have all permissions, ...
    (microsoft.public.windowsxp.general)
  • Re: DNS
    ... The access rights are the most prescriptive of the share permissions and the ... Make sure that you're trying to access the resources ... Also check that the account ...
    (microsoft.public.win2000.active_directory)
  • Re: Disconnecting network drive
    ... Whatever account you run the service under, ... configured with the correct permissions to access resources. ... 'Local System ...
    (microsoft.public.vc.mfc)
  • Re: Incoming E-Mail - cant create contact in OU
    ... account out of local administrator to attempt to find any denied access. ... I then added full permissions to my user account on both of these keys, ... local admin rights to the server hosting incoming email. ... what permission I need to give the app pool locally to avoid this issue. ...
    (microsoft.public.sharepoint.windowsservices)