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?  
LVL 3
netmonAsked:
Who is Participating?
 
stevenlewisConnect With a Mentor Commented:
Click on Start/Programs/Administrative Tools/Computer Management. Look for Local Users and Groups under

System Tools (on the left side), and expand it to show the two folders, Users and Groups. Highlight

the Users folder, and then you'll see the Administrator and Guest account. Highlight the Guest account,

and click on Action. Go down to properties, and on the General Tab for Guest Properties, you'll see

the box checked for Account is Disabled. Uncheck it, and you should be good to go
0
 
stevenlewisCommented:
you may have to add the guest account to the permissions for the shares
0
 
netmonAuthor Commented:
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!
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
netmonAuthor Commented:
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!
0
 
netmonAuthor Commented:
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!
0
 
netmonAuthor Commented:
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!
0
 
netmonAuthor Commented:
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...
0
All Courses

From novice to tech pro — start learning today.