Network Geeks

   / Network Geeks #31  
<font color=blue>set both share and NTFS permissions to Everyone/Full Control. </font color=blue>

This is what I suggested earlier (or at least I thought I did)/w3tcompact/icons/smile.gif
 
   / Network Geeks #32  
Do you think he needs to make the 98 machine join a workgroup? My thinking is he doesn't have a domain so he has to join a workgroup and you're suggestion is right along those lines. If you don't log in, there are no security credentials. However, he can access some shares on the 2000 machine from the 98 machine. He just can't access the Program Files share. Is this because it is a protected or special system share? If that is the case, he shouldn't be able to access the C$ share, the system folder, etc... I'm still stumped.
 
   / Network Geeks #33  
I've gotten this to work by defining the same userid, with the same password on each PC, the logging in to each PC and mapping the drives in either direction.
 
   / Network Geeks #34  
So, if he doesn't log in, that means he skipped the password the first time he ever logged in. On the 98 machine he should go to start/logoff and he should get a log on prompt, then enter the same userid and password as he logs in with his 2000 machine. That will work as long as the original 98 login was not the same as his 2000 machine. If the original 98 login was the same as his 2000 machine, he will have to hit the ESC key at the login prompt, find the .PWL file for that user, blow away the .PWL file, then log off and back on as the 2000 userid with the correct 2000 password.... long sentence. Does that sound right?
 
   / Network Geeks #35  
Yep.
 
   / Network Geeks #36  
<font color=blue>He just can't access the Program Files share. Is this because it is a protected or special system share? If that is the case, he shouldn't be able to access the C$ share, the system folder, etc.</font color=blue>

The default W2K NTFS permission set for c$ is Everyone/Full Control, which is why he could access the c-drive share even without credentials, I believe. Even the \WINNT folder includes Everyone in its permission set.

The default NTFS set for the Program Files folder is more restrictive, and does not include "Everyone", but only Administrators, Power Users, and Users. All of these groups require some sort of credentials to permit access.

I think the simplest way to fix it (per pbenven) would be to grant "Everyone" Full Control on the Program Files folder. This is a potential security hole if connected full time to the Internet, but a personal firewall should take care of that.
 
   / Network Geeks
  • Thread Starter
#37  
Sorry to leave you guys hanging. I've been kinda busy. I sent MikePa an email with some images of the problem. The images file is too large to post here. If anyone else wants to see them let me know and I will email them to you also. I might have time later to try some more of the suggestions.

Jerry
 
   / Network Geeks #38  
Have you tried to map a drive to this share by using the \\computername\progra~1 nomenclature? Many times just by using the shortened file names, you can get this to work. Another trick is to put the whole name in quotes such as "\\computername\program files". The problem might just be in the way that the network subsytem interprets the space in the name of the share. If this does not fix the problem, feel free to e-mail me with any more specifics and I will do my best to help you out.
 

Tractor & Equipment Auctions

2010 Ford Edge SE SUV (A51694)
2010 Ford Edge SE...
1990 GREAT DANE 28' REFER (A52472)
1990 GREAT DANE...
Duetz Power Unit (A50120)
Duetz Power Unit...
New Long Forks (A53002)
New Long Forks...
2012 Ford Fusion SE Sedan (A51694)
2012 Ford Fusion...
2024 Bintelli ActivEV Pulse Electric Golf Cart (A51694)
2024 Bintelli...
 
Top