J
Jay man
Guest
We have intermittent issues with users mapping a drive to a dfs share. Drive
mappings happen through a login script. Drive mappings to other servers work
fine.
Symptoms:
1.A "system error 3 has occurred" error appears when running the login
script or trying to map the drive manually through DOS using net use n:
\\domain\share\folder
2.When trying to map through explorer, a system error occurs.
3.Yet when you browse to the share from run you can view the contents and
only then are you able to map the drive to \\domain\share\folder
The above happens irrespective of whether just the domain name is used or
the FQDN is used.
Client workstations having the problem are Windows Xp pc's. DC's are Windows
2003 Sp1, along with file servers hosting the data.
Anyone had or have the same issue with a solution?
Cheers
mappings happen through a login script. Drive mappings to other servers work
fine.
Symptoms:
1.A "system error 3 has occurred" error appears when running the login
script or trying to map the drive manually through DOS using net use n:
\\domain\share\folder
2.When trying to map through explorer, a system error occurs.
3.Yet when you browse to the share from run you can view the contents and
only then are you able to map the drive to \\domain\share\folder
The above happens irrespective of whether just the domain name is used or
the FQDN is used.
Client workstations having the problem are Windows Xp pc's. DC's are Windows
2003 Sp1, along with file servers hosting the data.
Anyone had or have the same issue with a solution?
Cheers