Truly bizarre access denied issue
This is a discussion about Truly bizarre access denied issue in the Everything New Technology category; Here's the scoop. 2 nt 4 machines, pdc and bdc. A windows 2000 member file server. \\2k\data\SMITH The data folder has share permission of everyone full control, and ntfs permission of the SMITH directory has full control for SMITH and domain admins.
Here's the scoop. 2 nt 4 machines, pdc and bdc. A windows 2000 member file server. \\2k\data\SMITH
The data folder has share permission of everyone full control, and ntfs permission of the SMITH directory has full control for SMITH and domain admins. All machines have netbeui and TCP/IP with netbios enabled.
I log on a win98 workstation as SMITH from a win98 machine. I browse into \\2k\data, but get ACCESS denied when I try to go into the SMITH directory itself.
I log on to a different win98 machine, and I can browse right into the SMITH directory without issues and all is well. The machines that work for access work every time, the machines that deny when logged onto them deny every time.
I don't understand how I can get in from some 98 machines and not others when they are all logging onto the domain.
Isues of note the PDC used to be a windows 2000 server, but died and was replaced with an NT 4 server (promoted the bdc, reinstalled the new nt server and promoted to pdc after replicating the SAm database and what not. To make sure there were no issues, I had the windows 2000 server leave the domain, and rejoin the nt 4 domain fresh. I've been searching the web for solutions and have not found anything yet.
The data folder has share permission of everyone full control, and ntfs permission of the SMITH directory has full control for SMITH and domain admins. All machines have netbeui and TCP/IP with netbios enabled.
I log on a win98 workstation as SMITH from a win98 machine. I browse into \\2k\data, but get ACCESS denied when I try to go into the SMITH directory itself.
I log on to a different win98 machine, and I can browse right into the SMITH directory without issues and all is well. The machines that work for access work every time, the machines that deny when logged onto them deny every time.
I don't understand how I can get in from some 98 machines and not others when they are all logging onto the domain.
Isues of note the PDC used to be a windows 2000 server, but died and was replaced with an NT 4 server (promoted the bdc, reinstalled the new nt server and promoted to pdc after replicating the SAm database and what not. To make sure there were no issues, I had the windows 2000 server leave the domain, and rejoin the nt 4 domain fresh. I've been searching the web for solutions and have not found anything yet.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Sep 16
Sep 18
0
3 minutes
Responses to this topic
OP
For all those interested, I gotit worked out. It was a combination of errors which I still cannot explain. Long story short I upgraded thePDC to Windows 2000 Server again. The Windows 2000 File server I had to leave the domain (and delete the account from active directory) and rejoin the domain fresh. It took a good hour tomake this work. (When the 2000 member server would try tojoin the domain, it would prompt for password and username to add to the domain, but then after that it would say there was no domain. After many attempts it joined. All was still not well though.
3 remaining 98 workstations still gave the access denied message fgr user SMITH but SMITH could get into his directory from all the rest. Turns out the networking on those 3 98 workstations were all whack. The network settings all looked good, but I arbitrarily removed all networking and reinstalled the nic driver fresh.
After this, badaBOOM all was fixed.
3 remaining 98 workstations still gave the access denied message fgr user SMITH but SMITH could get into his directory from all the rest. Turns out the networking on those 3 98 workstations were all whack. The network settings all looked good, but I arbitrarily removed all networking and reinstalled the nic driver fresh.
After this, badaBOOM all was fixed.
