Issue to map network drive on untrusted domain
Hi to all,
We are using Windows 7 Professional 32 Bit, connected to domain named DomainA.
To the client is applied the policy:
Always wait for the network at computer startup and logon
Enabled
The clients map, with a logon script, network drives in DomainA with no problem, it are ever connected and accessible.
Also, in the clients are mapped network drives to an untrusted domain DomainB, created with windows explorer:
Map network driveDrive ZFolder \\....Reconnect at logonEntered DomainB\user and passwordRemember my credential,
NOT checked.
The mapped drive, after creation, open and is accessible, all fine.
After reboot of the client, the mapped drive to DomainB are not connected, a red X appear on the drive. When we try
to open it, the following error is displayed:
I suppose that the multiple connections, are related to DomainA credential connection.
After some minutes (too much), if we try again to open the network drive, a windows popup ask for password of the DomainB\user
credential and all are fine.
Its possible to minimize the timeout time of the domainA credential connection to domainB?
A solution is to save the DomainB credential (user and password) in the credential manager (Windows credential),
in this case, when the users logon on, all the drive are mapped and functional, but for security policy would be preferable not to save the password.
In windows
xp the "delay" problem does not occur.
Any suggestions are greatly appreciated.
Thanks in advance.
March 14th, 2013 7:36am