*windev* generates error 12 trying to open printer

[Michael Greer]

We have a user who as a printer defined on the server as link file P20, which contains "*windev*;SEA-P20".  This has been working for years.  Suddenly today, this printer can be accessed when connected to the server (windows 2012) directly, but when connecting through windx, even *from* the server, *windev* cannot be opened, nor an the printer P20.  Throws an error 12.  Any ideas what might have changed.

[Michael Greer]

Going to cancel this.  Reboot solved problems so typical windows issue.

[Michael Greer]

So this is back as in issue. It appears that if I edit a device (change a driver for example), then access to *windev* fails *only for those who are accessing through WindX.  If I am on the server and directly into Pxplus I can access *windev*. If I am on the server, but use a client, it is a no go.

[Devon Austen]

The likely culprit is some thing networking/security related. Maybe an OS update or security software update reset a permission or closed a port.

I have seen updated switch the network from private to public before which disables a whole host of things from being open.