Windows Forum

Ask something
Discussion Locked

Problem login script NT Cluster Server

0 helpful
2 replies

by nxk

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are in the process of archiving some of the data to NODE1 (PDC). This has a spare 3.74GB of free space. I shared out a folder called 'Archiving Data' and changed the login script file so that this folder was mapped to Drive K. I then resyncronised the
domain.
I tested out some users and at first sight it seemed to be working correctly. However, I have noticed that when a user logs on and it uses NODE1 for the DHCP server the user can see and connect to Drive K:\ and can see all the archived folders. However, if NODE2 is used when the login script runs and it gets to K:\ - it shows an error message which
says 'System Error 3126' Logon failure or incorrect username and password.
The script runs okay but the user cannot see DriveK:\.
The permissions on NODE1\Archiving is Everyone - Full Control. Is it because you have to use the Administrator login in order to see drives on NODE1 from NODE2 but not the other way round?
I dont think we need to add it as a resource on the cluster do we as it there is a failover from NODE2 to NODE1 it will already be there.
Any help would be greatly appreciated.
Thank you

2 replies

by dlongan

In the script are you using the cluster alias or specifically node1?

Is this folder on the shared drive subsystem?

What role(s) are you using node2 as, for example you mention node1 as a PDC and DHCP server?

by nxk

The script specifically refers to node1
No the folder is not on the shared drive subsystem
The role for node2 is BDC

This discussion is closed to new replies.