sbs 2003 network slow why?
|
From: john on 3 Apr 2010 19:10 On 4/2/2010 2:51 PM, john wrote: > hello, I have a client they have a sbs 2003 server fully updated, and i > just copied over 20 gigs of data to the one bosses profile, now its been > a week and the clients and boss are complaining their network is slow, > they have gigabit speed. > > I checked the server there are no errors in the event log, have checked > random computers and no errors in the event logs. > > I have noticed that the bosses profile when it is loaded explorer.exe is > sitting at 5% usage while just on the desktop. > > I ping the desktops from the server and all the pings are <1ms so there > is no lag. > > what else can it be? > > I have tcp offload on the server because it has never given me problems > should i disable it? well there's nothing really wrong, I know there is an error for scanning for updates, but that due to sp3 not downloading in wsus properly I have to purge it. Ignore the shares missing were removed from the posting to save space. > Security assessment: Incomplete Scan > Computer name: MED\PDC1 > IP address: 192.168.2.100 > Security report name: MED - PDC1 (4-3-2010 4-04 PM) > Scan date: 4/3/2010 4:04 PM > Scanned with MBSA version: 2.1.2112.0 > Catalog synchronization date: > Security update catalog: Windows Server Update Services > > Security Updates Scan Results > > Issue: Security Updates > Score: Unable to scan > Result: An error occurred while scanning for security updates. (0x80072ee2) > > > Operating System Scan Results > > Administrative Vulnerabilities > > Issue: Local Account Password Test > Score: Check not performed > Result: Password checks are not performed on a domain controller. > > Issue: File System > Score: Check passed > Result: All hard drives (6) are using the NTFS file system. > Detail: > | Drive Letter | File System | > | C: | NTFS | > | D: | NTFS | > | F: | NTFS | > | G: | NTFS | > | H: | NTFS | > | I: | NTFS | > > Issue: Password Expiration > Score: Check failed (non-critical) > Result: Some user accounts (3 of 34) have non-expiring passwords. > Detail: > | User | > | Administrator | > | Guest | > | QBDataServiceUser18 | > | IUSR_PDC1 | > | IWAM_PDC1 | > | SUPPORT_388945a0 | > > Issue: Guest Account > Score: Check passed > Result: The Guest account is disabled on this computer. > > Issue: Autologon > Score: Check passed > Result: Autologon is not configured on this computer. > > Issue: Restrict Anonymous > Score: Check passed > Result: Computer is properly restricting anonymous access. > > Issue: Administrators > Score: Check failed (non-critical) > Result: More than 2 Administrators were found on this computer. > Detail: > | User | > | MED\Administrator | > | MED\Americas | > | MED\Enterprise Admins | > > Issue: Windows Firewall > Score: Best practice > Result: Windows Firewall is not installed or configured properly, or is not available on this version of Windows. > > Issue: Automatic Updates > Score: Best practice > Result: Automatic Updates are managed through Group Policy on this computer. > > Issue: Incomplete Updates > Score: Best practice > Result: No incomplete software update installations were found. > > Additional System Information > > Issue: Windows Version > Score: Best practice > Result: Computer is running Microsoft Windows Server 2003. > > Issue: Auditing > Score: Best practice > Result: Logon Success and Logon Failure auditing are both enabled. > > > Issue: Services > Score: Best practice > Result: Some potentially unnecessary services are installed. > Detail: > | Service | State | > | Simple Mail Transfer Protocol (SMTP) | Running | > | Telnet | Stopped | > | World Wide Web Publishing Service | Running | > > > Internet Information Services (IIS) Scan Results > > Administrative Vulnerabilities > > Issue: Sample Applications > Score: Check passed > Result: IIS sample applications are not installed. > > Issue: IISAdmin Virtual Directory > Score: Check passed > Result: IISADMPWD virtual directory is not present. > > Issue: Parent Paths > Score: Check passed > Result: Parent paths are not enabled. > > Issue: MSADC and Scripts Virtual Directories > Score: Check passed > Result: The MSADC and Scripts virtual directories are not present. > > Issue: IIS Lockdown Tool > Score: Check passed > Result: The IIS Lockdown tool was developed for IIS 4.0, 5.0, and 5.1, and is not needed for new Windows Server 2003 installations running IIS 6.0. > > Additional System Information > > Issue: IIS Logging Enabled > Score: Best practice > Result: All web and FTP sites are using the recommended logging options. > > > SQL Server Scan Results > > Instance MICROSOFT##SSEE > > Administrative Vulnerabilities > > Issue: SQL Server/MSDE Security Mode > Score: Check passed > Result: SQL Server and/or MSDE authentication mode is set to Windows Only. > > Issue: CmdExec role > Score: Check passed > Result: CmdExec is restricted to sysadmin only. > > Issue: Registry Permissions > Score: Check passed > Result: The Everyone group does not have more than Read access to the SQL Server and/or MSDE registry keys. > > Issue: Folder Permissions > Score: Check failed (critical) > Result: Permissions on the SQL Server and/or MSDE installation folders are not set properly. > Detail: > | Instance | Folder | User | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn | BUILTIN\Performance Log Users | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn | BUILTIN\Performance Monitor Users | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn | MED\SQLServer2005MSSQLUser$PDC1$MICROSOFT##SSEE | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn | \CREATOR OWNER | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data | MED\SQLServer2005MSSQLUser$PDC1$MICROSOFT##SSEE | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data | MED\SQLServer2005MSSQLUser$PDC1$MICROSOFT##SSEE | > | MICROSOFT##SSEE | C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data | \CREATOR OWNER | > > Issue: Sysadmin role members > Score: Best practice > Result: BUILTIN\Administrators group should not be part of sysadmin role. > > Issue: Guest Account > Score: Check passed > Result: The Guest account is not enabled in any of the databases. > > Issue: Sysadmins > Score: Check failed (non-critical) > Result: More than 2 members of sysadmin role are present. > > Issue: Service Accounts > Score: Unable to scan > Result: SQL Server, SQL Server Agent, MSDE and/or MSDE Agent service accounts should not be members of the local Administrators group or run as LocalSystem. > Detail: > | Instance | Service | Account | Issue | > | MICROSOFT##SSEE | MSSQL$MICROSOFT##SSEE | NT AUTHORITY\NetworkService | This is a Domain Account. Baseline Security Analyzer cannot determine whether it belongs to the Domain Admins group due to the following error: 1212 The format of the specified domain name is invalid. > . | > > Issue: Password Policy > Score: Check failed (critical) > Result: Enable password expiration for the SQL server accounts. > > Issue: SSIS Roles > Score: Check passed > Result: The BUILTIN Admin does not belong to the SSIS roles. > > Issue: Sysdtslog > Score: Best practice > Result: Do not create sysdtslogs90 in the Master or MSDB database.It is recommended to create a seperate logging database. > > > Instance SBSMONITORING > > Administrative Vulnerabilities > > Issue: SQL Server/MSDE Security Mode > Score: Check passed > Result: SQL Server and/or MSDE authentication mode is set to Windows Only. > > Issue: Exposed SQL Server/MSDE Password > Score: Check passed > Result: The 'sa' password and SQL service account password are not exposed in text files. > > Issue: CmdExec role > Score: Check passed > Result: CmdExec is restricted to sysadmin only. > > Issue: Registry Permissions > Score: Check passed > Result: The Everyone group does not have more than Read access to the SQL Server and/or MSDE registry keys. > > Issue: Folder Permissions > Score: Check passed > Result: Permissions on the SQL Server and/or MSDE installation folders are set properly. > > Issue: Sysadmin role members > Score: Best practice > Result: BUILTIN\Administrators group should not be part of sysadmin role. > > Issue: Guest Account > Score: Check passed > Result: The Guest account is not enabled in any of the databases. > > Issue: Sysadmins > Score: Check passed > Result: No more than 2 members of sysadmin role are present. > > Issue: SQL Server/MSDE Account Password Test > Score: Check not performed > Result: The check was skipped because SQL Server and/or MSDE is operating in Windows Only authentication mode. > > Issue: Service Accounts > Score: Best practice > Result: SQL Server, SQL Server Agent, MSDE and/or MSDE Agent service accounts should not be members of the local Administrators group or run as LocalSystem. > Detail: > | Instance | Service | Account | Issue | > | SBSMONITORING | MSSQL$SBSMONITORING | SYSTEM | LocalSystem account. | > | SBSMONITORING | SQLAgent$SBSMONITORING | SYSTEM | LocalSystem account. | > > > Instance SHAREPOINT > > Administrative Vulnerabilities > > Issue: SQL Server/MSDE Security Mode > Score: Check passed > Result: SQL Server and/or MSDE authentication mode is set to Windows Only. > > Issue: Exposed SQL Server/MSDE Password > Score: Check passed > Result: The 'sa' password and SQL service account password are not exposed in text files. > > Issue: CmdExec role > Score: Check passed > Result: CmdExec is restricted to sysadmin only. > > Issue: Registry Permissions > Score: Check passed > Result: The Everyone group does not have more than Read access to the SQL Server and/or MSDE registry keys. > > Issue: Folder Permissions > Score: Check passed > Result: Permissions on the SQL Server and/or MSDE installation folders are set properly. > > Issue: Sysadmin role members > Score: Best practice > Result: BUILTIN\Administrators group should not be part of sysadmin role. > > Issue: Guest Account > Score: Check passed > Result: The Guest account is not enabled in any of the databases. > > Issue: Sysadmins > Score: Check passed > Result: No more than 2 members of sysadmin role are present. > > Issue: SQL Server/MSDE Account Password Test > Score: Check not performed > Result: The check was skipped because SQL Server and/or MSDE is operating in Windows Only authentication mode. > > Issue: Service Accounts > Score: Best practice > Result: SQL Server, SQL Server Agent, MSDE and/or MSDE Agent service accounts should not be members of the local Administrators group or run as LocalSystem. > Detail: > | Instance | Service | Account | Issue | > | SHAREPOINT | MSSQL$SHAREPOINT | SYSTEM | LocalSystem account. | > | SHAREPOINT | SQLAgent$SHAREPOINT | SYSTEM | LocalSystem account. | > > > Desktop Application Scan Results > > Administrative Vulnerabilities > > Issue: IE Zones > Score: Check failed (critical) > Result: Internet Explorer zones do not have secure settings for some users. > Detail: > | User | Zone | Level | Recommended Level | > | MED\SBS Backup User | Internet | High | High | > Sub-Detail: > | Setting | Current | Recommended | > | Run components not signed with Authenticode | Enable | Disable | > | Run components signed with Authenticode | Enable | Disable | > | MED\QBDataServiceUser18 | Internet | High | High | > Sub-Detail: > | Setting | Current | Recommended | > | Run components not signed with Authenticode | Enable | Disable | > | Run components signed with Authenticode | Enable | Disable | > | MED\Administrator | Internet | Custom | High | > Sub-Detail: > | Setting | Current | Recommended | > | Run components not signed with Authenticode | Enable | Disable | > | Run components signed with Authenticode | Enable | Disable | > | Submit nonencrypted form data | Enable | Prompt | > > Issue: Macro Security > Score: Check not performed > Result: No supported Microsoft Office products are installed. > |