intermittent dfs drive mapping issues

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

You may want to upgrade to Server 2003 SP2 some time soon. See if any
of the info in these KBs helps:

http://support.microsoft.com/kb/938666
http://support.microsoft.com/kb/944505
http://support.microsoft.com/kb/931685

Thanks for your input. I've been through those kb's you supplied and none
seem relevant unfortunately. In the interim I've excluded the following
directories from being scanned by Trend Officescan:

d:\dfs
s:\shareddirectory (this is the dir where all the shares are)

You mention upgrading to SP2, I've been through the list of fixes SP2 is
supposed to resolve and kb898900 is the only fix related to dfs there is.
Does not seem to be related.

Also did I mention, this problem is intermittent.

Hi Jay man,

I am wondering if you ever found a solution to this problem. I am now having precisely the same issue with DFS-mapped drives. And I have also been through the KB articles referenced, but they do not address this specific problem.

My problems started about 6 weeks ago, and I thought that it might be due to a Windows Update. But I now see that your original post is far earlier...

Regards

Hi,

Unfortunately, I'm experiencing exactly the same problem since 2 weeks!

Did you ever the solution?

Quote:

---

Originally Posted by lacuzon93e

Hi,

Unfortunately, I'm experiencing exactly the same problem since 2 weeks!

Did you ever the solution?

---

This may seem like a strange suggestion, but change the location of this particular NET USE line in your logon script... I have seen this behavior when using my KIX scripts (but not Citrix)... This is just a guess, but is the \\domain.com\namespace\citrixprofiles target on a different server than your other network shares?

Hi,

Thanks for your reply EINSTEIN_007.

Fortunately, I solved that problem late yesterday.

I had to remove a server from the domain name server list and then readding it in that list.

The server about which I'm speaking had been reinstalled ex nihilo 2 weeks ago with the same name and @IP, following a crash.

I suppose that the name that was in the domain name server list was still refering to the old server.

Everything seems to go right since.