Windows 10: PNRP P2P stops working on Windows 10 1803 and 1809

Hello,


I am having trouble starting a PNRP P2P connection since updates 1803 and 1809. The setup is as following:


- PC A (Windows 10, 1803)

- PC B (Windows 10, 1809)

- PC C (Windows 10, 1607)


All PNRP- and SSDP Services (and UPnP) are running on each machine and set to "Auto" or "Auto (delayed start)". All firewalls have ports 3540 and 1900 open (or are shut down completely for some tests).

All PCs are in the same network and can ping each other on ipv6 and ipv4. This is about a "LinkLocal.." cloud.


PC C (1607) can connect to PC A and PC B and communicate with both. But PC A CANNOT connect to PC B! I tried every fix there is for PNRP (switching on/off all services, setting rights on folder "MachineKeys", deleting "idstore" etc.) but any PC newer then update 1803 can only connect to PCs prior to 1803 with PNRP.


With WireShark I can see that the M-Search packages (with "urn:Microsoft Windows Peer...") arrive and are answered correctly on port 1900, so SSDP seems to work correctly. But with PCs newer then 1803 trying to resolve each other, the "PNRP LOOKUP" Message is never sent.


When I have all three PCs connected and all PCs can resolve PC C (with 1607) and I am trying "netsh p2p pnrp peer traceroute " on the active cloud from PC A to PC B, it resolves the correct ipv6 address but says "not reachable" and "not found" (even though that PC B is connected to PC C).


The connections are established with netsh (add registration, resolve etc.), but it was also tested with System.net.PeerToPeer applications with same results. Also Windows 7 PCs could connect to all others without trouble, and switching from 1803 to only 1809 Updates had no effect as well. I tested one PC having update 17... (could connect) then updated that PC to 1803 (stopped connecting).


I really think PNRP is a great way of communication between Windows PCs, especially in times of rising demand for the IoT. I am a bit surprised that the PNRP issues seem to be kind of neglected by Microsoft - at least it is really hard to find any support for it.

Help on that issue would be greatly appreciated.

:)

 

Win 10 1803 to 1809 update

Good day one and all.

My Desktop computer running Win 10 updated from version 1803 to 1809 a while back, but my laptop/notebook running Win 10 version 1803 (As of a Check for updates today 15 Nov 2018 6:30 AM) still hasn't updated to 1809.

I'm assuming the update 1803 to 1809 has now resumed after the earlier problems caused a suspension?

Updates in general on the laptop are coming through as available, for example, yesterday (14th Nov 2018) the "Cumulative Update for Windows 10 version 1803 for x64 based Systems (KB4467702)" arrived and was installed okay.

Any thoughts, suggestions?

Thanks

Arturo

 

Unlocked Realtek HD Audio Drivers Windows 7 & 8 (With Dolby Digital Live and DTS Interactive)

DTS supported natively by Windows 8/8.1 and it should work on windows 10 too just DDL require to unlock your driver .

 

Windows 10 Update 1809 not working on tablet

I have an Acer tablet that is running Windows 10, 32-bit, update 1803. I have tried to update it to 1809 through ever method I could find, ISO file, update from the site, etc. Each time, the process goes through all of the normal steps, then restarts several
times, but when everything has completed it is back to Update 1803 with new updates to be downloaded. This sounds like this model tablet cannot be updated to 1809, but I receive no messages stating that is the case.

The tablet is working properly under the 1803 update. Why is it not able to update to 1809?