Link to home
Start Free TrialLog in
Avatar of netmon
netmon

asked on

Simple access permissions

this is probably going to seem like real 101 stuff to you guys but I'm really stumped.
I'm trying to get the computers at my workplace hooked up.
I've gotten to the point where they can all "see" eachother in the "network neighborhood" or "Computers Near Me" but I get asked for unknown log-on and password upon attempting to access one from the other.
Both are fully updated WIN2k systems.
BOTH have had "sharing" activated on the c-drive and at least a couple folders.
I have full administrator privilidges and access to all the pc's but for the life of me I can't see where to designate a "sharing" password. and frankly I don't WANT one. I've created a workgroup and I'd like to simply designate specific computer names as having unrestricted acsess within that workgroup. Shouldn't I be able to do that?
help?  
ASKER CERTIFIED SOLUTION
Avatar of stevenlewis
stevenlewis

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of stevenlewis
stevenlewis

you may have to add the guest account to the permissions for the shares
Avatar of netmon

ASKER

I was just about to run back to say "never mind I got it"!
but your answer sounds like a winner too so...
here's what I did since posting.
First off turned out one of the PC's I was working on was NOT "fully updated" and was sans the WIN2k SP2 update. did that.
The other machine had nothing set up to share. In order to share the C:drive (make the "hand" appear) I had to ADD a new shareing and name it simply "C" the default with "C$" had some kind of administrative restrictions on it.
lastly I took note of the network user log-ins that appeared upon boot-up, in each case they had been setup initially with no password. then attempted access again this time using those user names, left the password blank, and wah-lah! I'm definitely going to print-out your answer though as it sounds very good and it's something else I didn't know or find in my own research tonight. 10 hours ago my boss asked me on the phone how much I knew about "networking" The answer now is "a HELL OF A LOT MORE THAN I KNEW 10 FRIGGIN' HOURS AGO!!!"  
thanks all!
Avatar of netmon

ASKER

I was just about to run back to say "never mind I got it"!
but your answer sounds like a winner too so...
here's what I did since posting.
First off turned out one of the PC's I was working on was NOT "fully updated" and was sans the WIN2k SP2 update. did that.
The other machine had nothing set up to share. In order to share the C:drive (make the "hand" appear) I had to ADD a new shareing and name it simply "C" the default with "C$" had some kind of administrative restrictions on it.
lastly I took note of the network user log-ins that appeared upon boot-up, in each case they had been setup initially with no password. then attempted access again this time using those user names, left the password blank, and wah-lah! I'm definitely going to print-out your answer though as it sounds very good and it's something else I didn't know or find in my own research tonight. 10 hours ago my boss asked me on the phone how much I knew about "networking" The answer now is "a HELL OF A LOT MORE THAN I KNEW 10 FRIGGIN' HOURS AGO!!!"  
thanks all!
Avatar of netmon

ASKER

I was just about to run back to say "never mind I got it"!
but your answer sounds like a winner too so...
here's what I did since posting.
First off turned out one of the PC's I was working on was NOT "fully updated" and was sans the WIN2k SP2 update. did that.
The other machine had nothing set up to share. In order to share the C:drive (make the "hand" appear) I had to ADD a new shareing and name it simply "C" the default with "C$" had some kind of administrative restrictions on it.
lastly I took note of the network user log-ins that appeared upon boot-up, in each case they had been setup initially with no password. then attempted access again this time using those user names, left the password blank, and wah-lah! I'm definitely going to print-out your answer though as it sounds very good and it's something else I didn't know or find in my own research tonight. 10 hours ago my boss asked me on the phone how much I knew about "networking" The answer now is "a HELL OF A LOT MORE THAN I KNEW 10 FRIGGIN' HOURS AGO!!!"  
thanks all!
Avatar of netmon

ASKER

I was just about to run back to say "never mind I got it"!
but your answer sounds like a winner too so...
here's what I did since posting.
First off turned out one of the PC's I was working on was NOT "fully updated" and was sans the WIN2k SP2 update. did that.
The other machine had nothing set up to share. In order to share the C:drive (make the "hand" appear) I had to ADD a new shareing and name it simply "C" the default with "C$" had some kind of administrative restrictions on it.
lastly I took note of the network user log-ins that appeared upon boot-up, in each case they had been setup initially with no password. then attempted access again this time using those user names, left the password blank, and wah-lah! I'm definitely going to print-out your answer though as it sounds very good and it's something else I didn't know or find in my own research tonight. 10 hours ago my boss asked me on the phone how much I knew about "networking" The answer now is "a HELL OF A LOT MORE THAN I KNEW 10 FRIGGIN' HOURS AGO!!!"  
thanks all!
Avatar of netmon

ASKER

please excuse the multiple posts. I have no idea.
All I know is I was trying to post another DIFFERENT comment and I just kept getting "internal server error" over and over, refreshed the page a few times and finally gave up. now today I see.... one for the webmaster...