administrative shares

  • Thread starter Thread starter CSC
  • Start date Start date
C

CSC

Windows 2000 Professional Workgroup
Administrative shares (admin$, ipc$...)are not enabled,
Workgroup computers unable to access the W2K machine. Net
share command loads the shares, but only briefly. No
evidence of a virus or worm. W2K OS recently reinstalled on
the machine. Is there a solution?
 
CSC said:
Windows 2000 Professional Workgroup
Administrative shares (admin$, ipc$...)are not enabled,
Workgroup computers unable to access the W2K machine. Net
share command loads the shares, but only briefly. No
evidence of a virus or worm. W2K OS recently reinstalled on
the machine. Is there a solution?
Click to expand...

Please supply full details of your problem:

- How do you know that the administrative shares are not
enabled?
- Have you tried them by their proper names (C$, D$ etc)?
- What is the exact "net share" command you use?
- What exactly do you mean by "loads the shares, but only briefly"?
 
-----Original Message-----



Please supply full details of your problem:

- How do you know that the administrative shares are not
enabled?
- Have you tried them by their proper names (C$, D$ etc)?
- What is the exact "net share" command you use?
- What exactly do you mean by "loads the shares, but only briefly"?


.
Response to your questions:
Click to expand...
Start/Run/fsmgmt.msc produces a list of shared folders.
None of the administrative shares are present.

At the command prompt, entering "net share ipc$," for
example, enables the ipc$ share ("ipc$ was shared
successfully" is the computer response). If you run
fsmgmt.msc at this point, the ipc$ share appears in the
shared folders list. Workgroup file sharing works normally
as well. However, the ipc$ sharing does not persist and
disappears from the shared folders list after a minute or
two and file sharing no longer works afterwards.

This is a frustrating problem. I have seen other postings
which seem to indicate a worm of some sort may be the
cause, but that appears unlikely in this case.
 
CSC said:
Start/Run/fsmgmt.msc produces a list of shared folders.
None of the administrative shares are present.

At the command prompt, entering "net share ipc$," for
example, enables the ipc$ share ("ipc$ was shared
successfully" is the computer response). If you run
fsmgmt.msc at this point, the ipc$ share appears in the
shared folders list. Workgroup file sharing works normally
as well. However, the ipc$ sharing does not persist and
disappears from the shared folders list after a minute or
two and file sharing no longer works afterwards.

This is a frustrating problem. I have seen other postings
which seem to indicate a worm of some sort may be the
cause, but that appears unlikely in this case.
Click to expand...

As I suggested in my first reply: to connect to administrative
shares, you use this command:

net use x: \\SomePC\c$
 
-----Original Message-----



As I suggested in my first reply: to connect to administrative
shares, you use this command:

net use x: \\SomePC\c$


.
Please explain this command as I am getting system errors.
Click to expand...
What does "x" refer to? I assume "somepc" is the w2k
computer name. After using this command, would the
administrative shares appear in the shared folders list
permanently? Thanks.
 
CSC said:
What does "x" refer to? I assume "somepc" is the w2k
computer name. After using this command, would the
administrative shares appear in the shared folders list
permanently? Thanks.
Click to expand...

X: is a random drive letter I used. I could have used almost any
other letter of the alphabet.

C$ is the name of the administrative share, equivalent to drive C:.

Why don't you try the command for yourself and report the
result here?
 
-----Original Message-----



X: is a random drive letter I used. I could have used almost any
other letter of the alphabet.

C$ is the name of the administrative share, equivalent to drive C:.

Why don't you try the command for yourself and report the
result here?


Thanks for your patience.
Click to expand...
I entered the following:
net use x: \\computername\c$

The response was: System error 67 has occurred. The network
name cannot be found.

Looking at http://support.microsoft.com/?kbid=265861, it
seems that this command may not work with W2K.

Regards.
 
CSC said:
I entered the following:
net use x: \\computername\c$

The response was: System error 67 has occurred. The network
name cannot be found.

Looking at http://support.microsoft.com/?kbid=265861, it
seems that this command may not work with W2K.

Regards.
Click to expand...

I must admit that I do not understand the essence of KB article 265861.
On the other hand I use the "net use" command extensively on all
versions of Windows, from Win98 right through to Win2003 Server,
and it has never failed for me. In your case I would do this:

1. Create the share \\YourServer\Test.
2. Turn off all internal firewalls, especially those that are integrated
with your virus scanner.
3. Start a Command Prompt on your server.
4. Type these two commands on the server:
net use x: \\YourServer\Test
net use y: \\YourServer\c$
5. Start a Command Prompt on your workstation.
6. Type these commands on the workstation:
ping YourServer
net use x: \\YourServer\Test
net use y: \\YourServer\c$
7. Report the result of each of the above commands.
8. Report the value of these registry keys:
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters:
- AutoShareServer
- AutoShareWks
 
-----Original Message-----



I must admit that I do not understand the essence of KB article 265861.
On the other hand I use the "net use" command extensively on all
versions of Windows, from Win98 right through to Win2003 Server,
and it has never failed for me. In your case I would do this:

1. Create the share \\YourServer\Test.
2. Turn off all internal firewalls, especially those that are integrated
with your virus scanner.
3. Start a Command Prompt on your server.
4. Type these two commands on the server:
net use x: \\YourServer\Test
net use y: \\YourServer\c$
5. Start a Command Prompt on your workstation.
6. Type these commands on the workstation:
ping YourServer
net use x: \\YourServer\Test
net use y: \\YourServer\c$
7. Report the result of each of the above commands.
8. Report the value of these registry keys:
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters:
- AutoShareServer
- AutoShareWks


.
I solved this problem by reinstalling W2K. Thanks for your
Click to expand...
input.
 
Back
Top