'No Entire Network' bug?!?
From: Peter Stam (PeterStam_at_discussions.microsoft.com)
Date: 06/06/05
- Next message: mocity: "Update 828028 and SP1"
- Previous message: paulcerv: "win2003 ca and domain controller certificates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 6 Jun 2005 10:52:01 -0700
Hello everybody,
We have a terminal server that is locked down to the bone (i tried that
is). There is a policy under 'User configuration --> Administrative
templates --> windows components --> windows explorer --> 'No Entire
Network'. I enabled this policy so that you can't browse the entire
network from the terminal server. Here's the thing:
When I connect with RDP (local drives connected) and start Microsoft
Office in the terminal session, I open a document from my local drive
in the RDP session and 'save as' it once again. The standard dialog
comes with the path \\desktop\my network places\entire
network\\tsclient\d (the local drive). So as you might see I can then
select 'Entire Network' and browse through the 'entire network'?!?. I
know that the policy only removes the icon from the 'My network places'
but how am I suppose to block this problem then? Any ideas because I
realy like to close the 'Entire Network' option due to security issues.
I know that the server can be hidden by 'net config server /hidden:yes'
but connected sessions keep rembering this so I can't remove the
servers once they browsed the network once.
Best Regards,
Peter
- Next message: mocity: "Update 828028 and SP1"
- Previous message: paulcerv: "win2003 ca and domain controller certificates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
