mikeymikec
Lifer
So there's PC1 and PC2 on a network, both running Win7 HP 64 with all updates.
PC1 shares a printer that User1 and User2 on PC2 would like to access, and some documents that just User1 should be allowed to access.
I've set up PC1 to not require logins to access the PC via Windows filesharing services, and I've secured the documents share simply by leaving its filesystem permissions so that the only user of PC1's credentials are required to access those files.
Here's where things get weird:
If I set up the PC1 shared printer on User 1 & 2's profiles, do a test print from both User1 and User2's profiles, it works fine. However, as soon as I set up a mapped network drive on User1's profile to access PC1's documents folder with saved credentials, User2 can no longer print to that printer. File access and printing via PC1 continues to work fine for User1.
In case anyone asks, all three users have different usernames.
As far as I'm aware, a mapped network drive should be user-specific, as should network login credentials. However it seems to me that there's some kind of creep going on between userland and 'all users' land. I suppose the bug could be intentional in order to encourage users to set up a Windows domain, but given that there's three PCs in total this would seem like overkill and a very expensive solution just so that selective printing/filesharing works. For now User2 has to put up with not being able to print to PC1's printer which is annoying but not the end of the world (multiple printers on network).
Another workaround I could look into is sticking a network switch between PC1's network connection and the network, and have PC1's printer actually on the network rather than being shared, but as the printer choices were not made by me, it's easily possible that the printer in question is USB only. I could look up the cost of one of those JetDirect boxes, I've never actually bought one before 🙂
PC1 shares a printer that User1 and User2 on PC2 would like to access, and some documents that just User1 should be allowed to access.
I've set up PC1 to not require logins to access the PC via Windows filesharing services, and I've secured the documents share simply by leaving its filesystem permissions so that the only user of PC1's credentials are required to access those files.
Here's where things get weird:
If I set up the PC1 shared printer on User 1 & 2's profiles, do a test print from both User1 and User2's profiles, it works fine. However, as soon as I set up a mapped network drive on User1's profile to access PC1's documents folder with saved credentials, User2 can no longer print to that printer. File access and printing via PC1 continues to work fine for User1.
In case anyone asks, all three users have different usernames.
As far as I'm aware, a mapped network drive should be user-specific, as should network login credentials. However it seems to me that there's some kind of creep going on between userland and 'all users' land. I suppose the bug could be intentional in order to encourage users to set up a Windows domain, but given that there's three PCs in total this would seem like overkill and a very expensive solution just so that selective printing/filesharing works. For now User2 has to put up with not being able to print to PC1's printer which is annoying but not the end of the world (multiple printers on network).
Another workaround I could look into is sticking a network switch between PC1's network connection and the network, and have PC1's printer actually on the network rather than being shared, but as the printer choices were not made by me, it's easily possible that the printer in question is USB only. I could look up the cost of one of those JetDirect boxes, I've never actually bought one before 🙂
