Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / December 2004

Tip: Looking for answers? Try searching our database.

W2K - broken file sharing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
cew - 23 Dec 2004 21:08 GMT
I have 2 computers, D and L, on a 100BT LAN. When both were running
W98SE, file sharing worked right. I installed W2K on D, and I think I
set up peer-to-peer networking right. Now D can access shared files on L
fine, as before. D shows up in the joint workgroup on L, but double
clicking D to access D's shared files produces a password dialog box as
follows:
Entire Network Password
    You must supply a password to make this connection.
    Resource:  \\D\IPC$
    Password:

I've check all the passwords I can find, but none work.

Appreciate anyone telling me what I've done wrong, or what I'm missing.
Thanks.
Dave Patrick - 23 Dec 2004 22:13 GMT
You'll want to create an account (in Users and Passwords) on the Win2k
machine(s) with the username and password that you use to logon to the win9x
machine(s) with. Then you'll need to share out the resource(s) with
permissions for those users. Also make sure they're all part of the same
workgroup. Then you'll no longer be prompted for the IPC$ password
Inter-process communication)

In a peer level workgroup, when you try to access resources on a Windows
NT/2000/XP/2003 machine, Windows NT/2000/XP/2003 needs to authenticate the
user. If the user account doesn't exist in it's local account database, then
access will be denied.

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

|I have 2 computers, D and L, on a 100BT LAN. When both were running
| W98SE, file sharing worked right. I installed W2K on D, and I think I
[quoted text clipped - 11 lines]
| Appreciate anyone telling me what I've done wrong, or what I'm missing.
| Thanks.
cew - 23 Dec 2004 23:03 GMT
> You'll want to create an account (in Users and Passwords) on the Win2k
> machine(s) with the username and password that you use to logon to the win9x
[quoted text clipped - 7 lines]
> user. If the user account doesn't exist in it's local account database, then
> access will be denied.

Thanks, makes sense. Except that I don't logon to the W98se machine. Do
I have to setup a logon on the W98se machine, then duplicate it on the
W2k machine?
The files I want available to the W98se machine are shared to 'Everyone'
with full control.
Dave Patrick - 23 Dec 2004 23:25 GMT
Either that or enable the guest account (on Windows 2000) and apply the
guest account permissions to the share.

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| Thanks, makes sense. Except that I don't logon to the W98se machine. Do
| I have to setup a logon on the W98se machine, then duplicate it on the
| W2k machine?
| The files I want available to the W98se machine are shared to 'Everyone'
| with full control.
John John - 24 Dec 2004 13:11 GMT
Use authenticated logon on the W98 machine.  That is force it to use
logon name and password at logon.

John

>> You'll want to create an account (in Users and Passwords) on the Win2k
>> machine(s) with the username and password that you use to logon to the
[quoted text clipped - 13 lines]
> The files I want available to the W98se machine are shared to 'Everyone'
> with full control.
cew - 24 Dec 2004 17:13 GMT
> You'll want to create an account (in Users and Passwords) on the Win2k
> machine(s) with the username and password that you use to logon to the win9x
[quoted text clipped - 7 lines]
> user. If the user account doesn't exist in it's local account database, then
> access will be denied.

Thanks to all. It works fine to log in on W98 with an account identical
to an account on W2K.
But I stll have a question --- what is the password for \\D\IPC$ ?!?!?!?
It's NOT the administrator password or any other password that I know of
on D.
Under Administrative Tools > Computer Management > Shared Folders >
Shares, I find IPC$ -- which along with ADMIN$, C$, and E$ (C & E being
hard disks) -- is "shared for administrative purposes, and cannot be
changed".
Obviously there is more here than I need to know about, but just curious.
Dave Patrick - 24 Dec 2004 17:23 GMT
These may help you.

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/prodd
ocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/pro
ddocs/en-us/file_srv_special.asp


http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipc/base/interp
rocess_communications.asp


Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| Thanks to all. It works fine to log in on W98 with an account identical
| to an account on W2K.
[quoted text clipped - 6 lines]
| changed".
| Obviously there is more here than I need to know about, but just curious.
cew - 24 Dec 2004 23:36 GMT
> These may help you.
>
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/prodd
ocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/pro
ddocs/en-us/file_srv_special.asp

>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipc/base/interp
rocess_communications.asp

Thanks for the links. I sort of understand IPCs. But I still don't know
what the requested password is. Or is there really no password, and the
password request is a artifact of no W98 ligin?
Dave Patrick - 24 Dec 2004 23:54 GMT
As long as restrict anonymous access is enabled a valid local account user
name and password is required.

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| Thanks for the links. I sort of understand IPCs. But I still don't know
| what the requested password is. Or is there really no password, and the
| password request is a artifact of no W98 ligin?
Jiri Tuma - 30 Dec 2004 09:10 GMT
IPC$ is serviced by build-in Guest account on NT based operating systems. So
password you are looking for is password of GUEST account. However, this
account is build-in - ie. it is existing on every machine - and has no
password by default, which is serious security issue even this account has
only minimal rights. Due this reason GUEST account is disabled by default on
current installations and if you really want to use anonymous access to your
computer, you need to enable it first.

> > These may help you.

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/file_srv_special.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipc/base/in
terprocess_communications.asp

> Thanks for the links. I sort of understand IPCs. But I still don't know
> what the requested password is. Or is there really no password, and the
> password request is a artifact of no W98 ligin?
John John - 24 Dec 2004 17:37 GMT
Try starting the Net Logon service on the W2K box.

John

>> You'll want to create an account (in Users and Passwords) on the Win2k
>> machine(s) with the username and password that you use to logon to the
[quoted text clipped - 18 lines]
> changed".
> Obviously there is more here than I need to know about, but just curious.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.