I have recently started my first IT job, graduating school this december with aa in networking - schooled on 2kserver(boo)
My first service call i have been assigned was a brand new network that was having problems logging in, and connecting to the network drive.
Onsite in the PDC server i have rearranged the users into domain security groups, assigned logon properties by DL security groups. DNS is running on another server, and its a static network. Each workstation (15 total) has a mapped drive to the server where they use a shared software app/database.
I was called out for login problems, (prior to my AD security changes) User would be in the shared app,claimed loss netowrk connectivity(via windows baloon on taskbar), shared app would freeze, user would have to reboot, and then could not connect to drive when logged back in and access the application.
I changed security settings for DL user group, went to workstations, logged in and out fine and drives connected each time. The next day, called me for problems logging in locally. Reviewed security settings in both Domain Security Policy and DC security policy (logon locally for DL user groups) I could not figure it out, ended up changing all the workstations (XP) from power users to admins and the problemd went away.
Called back today (2 days later), program is frezing and can not connect drives, I unplugged the network cable, checked the switch for connection, plugged it back in restarted and got a sbctlwnd running /end now prompt, restarted the workstation and everything worked fine.
I believe it has somthing to do with domain trust. The PDC server is running win server 2k3 and i have very limited expierence with that, but decent expierence with server2k. If i remember correctly, 2k3 comes completely locked down, ad server 2k comes wide open (correct me if i am wrong)
Any thoughts ?
My first service call i have been assigned was a brand new network that was having problems logging in, and connecting to the network drive.
Onsite in the PDC server i have rearranged the users into domain security groups, assigned logon properties by DL security groups. DNS is running on another server, and its a static network. Each workstation (15 total) has a mapped drive to the server where they use a shared software app/database.
I was called out for login problems, (prior to my AD security changes) User would be in the shared app,claimed loss netowrk connectivity(via windows baloon on taskbar), shared app would freeze, user would have to reboot, and then could not connect to drive when logged back in and access the application.
I changed security settings for DL user group, went to workstations, logged in and out fine and drives connected each time. The next day, called me for problems logging in locally. Reviewed security settings in both Domain Security Policy and DC security policy (logon locally for DL user groups) I could not figure it out, ended up changing all the workstations (XP) from power users to admins and the problemd went away.
Called back today (2 days later), program is frezing and can not connect drives, I unplugged the network cable, checked the switch for connection, plugged it back in restarted and got a sbctlwnd running /end now prompt, restarted the workstation and everything worked fine.
I believe it has somthing to do with domain trust. The PDC server is running win server 2k3 and i have very limited expierence with that, but decent expierence with server2k. If i remember correctly, 2k3 comes completely locked down, ad server 2k comes wide open (correct me if i am wrong)
Any thoughts ?