Cannot write temp file on SMS_DP$ Win32 Error = 64

Question

Hi we have two distribution points connected to our prem by a site to site vpn. The first DP is DP02, the second is DP03.

DP02 has been in place for a while and is running Windows Server 2016, it has worked fine since the day it went in then all of a sudden we started seeing errors when trying to distribute content. We battled with this but got nowhere, we figured we would try a new DP at that location. hence DP03.

DP03 is Windows Server 2019 and has the same issue, at this point we started scratching out heads. Then out of nowhere DP02 started to work again and touch wood it has been working since and continues to do so. The problem seems to now exist on DP03 and I am interested in getting to the bottom of it.

Both of these DPs are on the same LAN connected via the same VPN so if it was a network related issue I think it would also be affecting DP02 which it hasn't now for a few days and the fact DP02 is working at the time when DP03 is not suggests the network is not the issue but I am open to listening to any suggestions!

I don't have any access to the configuration of the LAN on the other side of the VPN where the DPs sit as it is maintained by another organisation. These two DPs are hosted in that organisations hyper-v environment, they are both contactable by ping and rdp and browsing their shares using their netbios names.

PkgXferMgr.log

Ignoring drive D:\. Unable to get volume information (HRESULT 21).
Skip realtekservice.cat since its been already added to the content on the remote DP
Skip RealtekService.inf since its been already added to the content on the remote DP
Sending file '\\DP03.mydomain.com\SMS_DP$\BFA308F4B160D486933E80ABADFD95A2443BE945B120E902EDD49CB21F1FEBB1-332B86AA-7240-46CA-999C-1200D9C2240F.BB10033B.temp'
No (more) send requests found to process.
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes
Cannot write to \\DP03.mydomain.com\SMS_DP$\BFA308F4B160D486933E80ABADFD95A2443BE945B120E902EDD49CB21F1FEBB1-332B86AA-7240-46CA-999C-1200D9C2240F.BB10033B.temp, Win32 error = 64

So as you can see the error we receive seems to be Win32 error = 64. Now we have no windows firewall turned on, we have exceptions for \DP03\SMS_DP$ and D:\SMS_DP$ in our AV (microsoft AV) and we can browse the share from the server acting as our content source (our primary site server). We have made sure that the primary site server is an administrator on the target DP. We have disabled NetBIOS via TCP/IP, flushed DNS cache yet it persists.

One thing that we do encounter is whenever we use

net view dp03 /all

We get a list of shares including SMS_DP$ however when we use

net view dp03.mydomain.com /all we receive error 53

Is my answer staring me in the face there and am i just not joining up the dots?

Can anyone offer any help or suggestions?

Answer 1

There's definitely a network layer issue going on here outside of the scope of control or visibility of ConfigMgr. There's an open-ended list of possibilities most of which are specific to your environment so it's not possible to really hazard a guess here even. I've added a Windows Server tag to add visibility (because as noted, this isn't specific to ConfigMgr in any way).

Anti-virus/anti-malware products are always a prime culprit as are network layer gateways or security tools (the later often get implemented in environments without anyone outside of the security team knowing). Don't rule out malware here either.

I would start by using tools like procmon, sysmon, and Process Explorer on the site server as well as the DPs to track the activity.

Tak to the networking folks as well as it could be as simple as failing network equipment.

Answer 2

Hi,

Please run the following command:

• nslookup dp03
• nslookup dp03.mydomain.com

Here is my lab screenshot:

C:\Windows\system32>nslookup cm16
Server:  UnKnown
Address:  10.1.1.10

Name:    cm16.sc.com
Address:  10.1.1.20


C:\Windows\system32>nslookup cm16.sc.com
Server:  UnKnown
Address:  10.1.1.10

Name:    cm16.sc.com
Address:  10.1.1.20