System error 53 when mapping a DFS link over a VPN connection

[Sto Rage©]

Thanks.
Where do I get the Windows 2000 version of dfsutil ?
The only one I could see on Microsoft's site is for the W2K3 servers. I
tried using it, but gives the error "The procedure entry point TraceMessage
could not be located in the dynamic link library ADVAPI32.dll."
-G

Have the client connect using VPN and try to connect to the DFS Root.

When

it fails have him run "dfsutil /pktinfo > pktinfo.txt" and see if he is
getting referrals.
If he is getting referrals and they are NetBIOS names make sure the VPN
client can resolve the NetBIOS Names. If they fail to resolve try the
Make WINS available for VPN clients
or
Add Hosts file with both IP to host name and IP to FQDN
or
Add DNS suffix search order for the domain in the VPN IP settings
--
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no

rights.

Hi DFS Gurus,
One of my customer reports a problem while his login script tries to

map

to a DFS share when he connects via VPN. He has a Windows 2000

Workstation.

The script works OK while he is in the office.
Is there any know issues with VPN and DFS?
Here's the error from the login script: (Message sanitized for obvious
reasons) You will notice that a direct server mapping works fine (T:\

Drive)

whereas all the DFS links fail. (BTW, the DFS links to drives H:\ & J:\
actually references the same Server that maps to the T:\ drive)
--- Processing Drive Mappings ---
--- Mapping H: to \\Domain_Name\DFS_Root\Share_Name\home\UserName ---
System error 53 has occurred.
The network path was not found.
--- Mapping J: to \\Domain_Name\DFS_Root\Share_Name\publish\UserName---
System error 53 has occurred.
The network path was not found.
--- Mapping T: to \\Server_Name\home ---
--- Mapping Q: to \\Domain_Name\DFS_Root ---
System error 53 has occurred.
The network path was not found.
Press any key to continue . . .
-G

[David Everett [MSFT]]

This tool is in the Support Tools on the setup CD
--
David Everett
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Sto Rage©
Thanks.
Where do I get the Windows 2000 version of dfsutil ?
The only one I could see on Microsoft's site is for the W2K3 servers. I
tried using it, but gives the error "The procedure entry point

TraceMessage

Post by Sto Rage©
could not be located in the dynamic link library ADVAPI32.dll."
-G

Have the client connect using VPN and try to connect to the DFS Root.

When

it fails have him run "dfsutil /pktinfo > pktinfo.txt" and see if he is
getting referrals.
If he is getting referrals and they are NetBIOS names make sure the VPN
client can resolve the NetBIOS Names. If they fail to resolve try the
Make WINS available for VPN clients
or
Add Hosts file with both IP to host name and IP to FQDN
or
Add DNS suffix search order for the domain in the VPN IP settings
--
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no

rights.

Hi DFS Gurus,
One of my customer reports a problem while his login script tries to

map

to a DFS share when he connects via VPN. He has a Windows 2000

Workstation.

The script works OK while he is in the office.
Is there any know issues with VPN and DFS?
Here's the error from the login script: (Message sanitized for obvious
reasons) You will notice that a direct server mapping works fine (T:\

Drive)

whereas all the DFS links fail. (BTW, the DFS links to drives H:\ & J:\
actually references the same Server that maps to the T:\ drive)
--- Processing Drive Mappings ---
--- Mapping H: to \\Domain_Name\DFS_Root\Share_Name\home\UserName ---
System error 53 has occurred.
The network path was not found.
--- Mapping J: to

\\Domain_Name\DFS_Root\Share_Name\publish\UserName---

Post by Sto Rage©

System error 53 has occurred.
The network path was not found.
--- Mapping T: to \\Server_Name\home ---
--- Mapping Q: to \\Domain_Name\DFS_Root ---
System error 53 has occurred.
The network path was not found.
Press any key to continue . . .
-G