bondbill2k2 Posted January 9, 2012 Posted January 9, 2012 (edited) We are having some really strange problems with our mapped drivers on your windows 7 admin computers. We have a drive mapped to a folder on the admin server which is running DNS and DHCP server for the admin computers. When users click on my computer then click on the mapped drive the machine slooooooowly loads the folder content, when I say slow I mean slow several minutes however If you use run to the location via the mapped drive name its near instant, yet you are still using that mapped drive letter to get there not a direct path of that location........................... Oh forgot to mention our servers are all 2003 r2 Confused! Edited January 9, 2012 by bondbill2k2
Abe Posted January 9, 2012 Posted January 9, 2012 I assume you have SP2 applied, in which case this may well be the cause of performance problems seen especially with Vista/7 clients: An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers
bondbill2k2 Posted January 9, 2012 Author Posted January 9, 2012 (edited) Hmm will disabling RSS have much noticable affect on the network and s erver performance? Pretty shocking that such a feature is related with so many problems! Either way ive made the changed and will get a reboot sorted asap but most our admin staff tend to work later then I do and don't see the need for reboots during their work hours! Edited January 9, 2012 by bondbill2k2
Michael Posted January 9, 2012 Posted January 9, 2012 I think Abe means 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1. I'd also recommend you use the FQDN when mapping network drives as 2008 R2 and 7 do work better.
Abe Posted January 9, 2012 Posted January 9, 2012 I think Abe means 2008 R2 with Service Pack 1 and Windows 7 with Service Pack 1. No the performance problems we saw were specifically 2003 R2 SP2 servers with mapped drives on Windows 7 clients.
bondbill2k2 Posted January 9, 2012 Author Posted January 9, 2012 I'd also recommend you use the FQDN when mapping network drives as 2008 R2 and 7 do work better. Does this disqualify using shared folders in the path then? Ill have to check if we use a FQDN or folder share
Michael Posted January 9, 2012 Posted January 9, 2012 The FQDN would include the domain in full and the share, such as: \\SERVERNAME.domain.domain\sharename Right clicking Computer and selecting Properties will display your FQDN.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now