SP1 can browse C$. SP2 cannot. Help!

[David Ellis]

Two computers are connected by a crossover cable. The Service Pack 1
computer can browse C$ on Service Pack 2, but the SP2 computer cannot
browse C$ on SP1. SP2 can browse SP1's shared folders. Both logged in
as administrators with same name and password. Both NTFS with simple
file sharing disabled.

On the SP2 computer, in Map Network Drive, a folder path is entered
and Finish is pressed. A "Map Network Drive" pop-up announces
"Attempting to connect to \\y4fg0\C$..."

A "Connect to y4fg0" dialog box pops up with the expected user name
ghosted and a blank password field.

Enter password and click OK.

Another "Connect to y4fg0" dialog box pops up with ghosted user name
"YF4G0\Guest" and the password filled in.

Click OK, the dialog box blinks and remains on screen with
"YF4G0\Guest" displayed and the password filled in.

If I assign a share name on SP1 (i.e., C-drive), SP2 has no trouble
browsing it.

Using SP1's share name C$, how do I get the SP2 computer to browse the
root folder?

--David

 

[Lanwench [MVP - Exchange]]

Two computers are connected by a crossover cable. The Service Pack 1
computer can browse C$ on Service Pack 2, but the SP2 computer cannot
browse C$ on SP1. SP2 can browse SP1's shared folders. Both logged in
as administrators with same name and password. Both NTFS with simple
file sharing disabled.

Minor teminology correction: "browsing" means, you're clicking on network
places/computers near me, etc., in Explorer, and seeing the computers &
shares there. When you directly connect to any share on a remote computer
(such as \\computer\share), you aren't browsing.

On the SP2 computer, in Map Network Drive, a folder path is entered
and Finish is pressed. A "Map Network Drive" pop-up announces
"Attempting to connect to \\y4fg0\C$..."

A "Connect to y4fg0" dialog box pops up with the expected user name
ghosted and a blank password field.

Enter password and click OK.

Another "Connect to y4fg0" dialog box pops up with ghosted user name
"YF4G0\Guest" and the password filled in.

Click OK, the dialog box blinks and remains on screen with
"YF4G0\Guest" displayed and the password filled in.

If I assign a share name on SP1 (i.e., C-drive), SP2 has no trouble
browsing it.

Using SP1's share name C$, how do I get the SP2 computer to browse the
root folder?

I've seen this/heard of it, but I don't remember the reason this happens -
are you 100% sure the credentials are correct/identical?

If you need to connect to a remote computer, it's usually best connect to
the specific subfolder shares you need. But still, if your manually set
"C-drive" share works for the root of your system volume as you say it does,
is there some specific reason you need to use c$ ?

 

[David Ellis]

Minor teminology correction: "browsing" means, you're clicking on network
places/computers near me, etc., in Explorer, and seeing the computers &
shares there. When you directly connect to any share on a remote computer
(such as \\computer\share), you aren't browsing.

The button in Map Network Drive is titled Browse. 'Guess I'm learning
bad habits from reading the dialog boxes. :=) Thanks for the tip.

I've seen this/heard of it, but I don't remember the reason this happens -
are you 100% sure the credentials are correct/identical?

If you need to connect to a remote computer, it's usually best connect to
the specific subfolder shares you need. But still, if your manually set
"C-drive" share works for the root of your system volume as you say it does,
is there some specific reason you need to use c$ ?

Three reasons. I'd like to not have to bother keying in a share of the
root folder, then wait for the drive to be scanned when C$ should
work. And I'd like to know if I'm doing something wrong so I don't
keep on doing it. I'd also like to know why SP1 has no such problem
and SP2 has it.

 

[Lanwench [MVP - Exchange]]

The button in Map Network Drive is titled Browse. 'Guess I'm learning
bad habits from reading the dialog boxes. :=) Thanks for the tip.

OK - well, that button does browse, I think - I just never use it. When I
know a machine name, I type it in (\\computer) manually - or use a command
line. So I think we're both right.

Three reasons. I'd like to not have to bother keying in a share of the
root folder, then wait for the drive to be scanned when C$ should
work. And I'd like to know if I'm doing something wrong so I don't
keep on doing it. I'd also like to know why SP1 has no such problem
and SP2 has it.

I'm honestly not sure either....sorry, perhaps someone else will post. Jus
remember, c$ is a share every bit as much as c-drive is - and performance
shouldn't be any different.