@Winuser
hmmm...maybe it was as simple as a IPv4/IPv6 conflict or error...?
Since you changed connection type of the printer...something changed in the IP or Routing that made your IP recognize or find the printer again?
Did you ever try to reset your network on the IP computer? Either way this was an interesting problem.
Glad you got it working.
That is quite true, for now. A word of caution though, if you decide SKIP is not what you want, go back as soon as possible. Don't put it off too long. An excerpt from the "Skip" announcement and the Hub link:
Since this fork just occurred, the builds from the RS_PRERELEASE and RS3_RELEASE branches will be virtually identical. But at some point in the future, build numbers in the RS_PRERELEASE branch will jump ahead, engineering teams will start checking in new code, and things diverge. When this happens – you will not be able to leave Skip Ahead and go back to builds from the RS3_RELEASE branch without reinstalling Windows.
The full announcement with some good explanations is here on the Feedback Hub:
Insider Hub - Windows Insider
Last edited by f14tomcat; 29 Jul 2017 at 18:58.
I did a clean install of build 16241 the other day and Windows setup my printer for me. The printer was still working after upgrading to build 16251.rs_prerelease. What ever changed happened today. I could ping it and the scanner still worked . It was just that Windows couldn't find it as a printer.
Screenshot from my Windows Server 2016 Desktop. It shows 4 VMs in the process of updating from 16241 to 16251.
The VMware VM is Windows Professional and the 3 Virtualbox (latest build v. 5.1.26) VMs, Professional, Enterpriseand Education.
I tested this with MS Word on Android. Continued on my Laptop in browser, in Word Online. :)
To send current Groove to PC, it has to channel through a 'mediaredirect'! Kinda lame!
Quote
