SBS 2008 Slow Network Performance with Windows XP Clients
|
From: OneginNH on 5 Feb 2010 09:21 To ask an obvious question, could my issue be as simple as not having IP6 on the XP workstations? Could that be why Windows 7 has no problems and XP does? "OneginNH" wrote: > Hi Al and thank you for your response. To answer your questions: > > 1) In regard to "advanced networking stuff" I'm not sure where/how to find > that kind of thing. I guess I can poke around. In calling Intel about this > I woudl have thought they could/woudl point me in this direction (if needed) > since both the server NIC and the workstation NICs are Intel (actually that's > not strictly true, one of the worst performers under Windows XP has a Realtek > NIC). But, yes, what you are suggesting has been on my mind ever since I ran > across that KB 968991 article that I mention elsewhere in this (rather long) > posting - problem with that 968991 article is that it doesn't strictly apply > to my circumstances. But it talks about Intel Advanced I/O stuff which is > what you are pointing me to. Why Intel wouldn't have known about such an > issue is a mystery to me and for these various reasons I have therefore held > off on applying the 968991 hotfix - do you think I shoudl do it? > > 2) In regard to the SBS BPA I'm a bit embarrassed to say that I had not run > it. Why? Because with the BPA for the Exchange piece built right in to the > O/S, I guess I assumed that the BPA tool for SBS would be built right into > the SBS console alongside all the other error checking that tool constantly > does. Anyway once I saw your note I immediately downloaded the SBS 2008 BPA. > Right off the bat I did show the only critical error (expected), which was > that the DNS A resource record was pointing to both NIC's on the server. As > mentioned elsehwere in this mammoth post, the second serve NIC got turned on > recently only as an experiemnt and it did not change things at all. Anyway > this mornign I shut off that second NIC again and ran BPA again and the > critical error is gone for DNS. There are no critical errors. The remaining > non-critical issues are, of course, of concern but I have no idea where to > focus/get started -- I need to solve the slow network problem before I do any > of the more refined fine-tuning stuff - as I'm sure you can appreciate. But > perhaps the key to my performance issus is in these issues, and I have posted > them below (below my next and last answer to your questions) -- if there is > any feedback you can provide I would most appreciate it. > > 3) You ask about logs on the server and the workstations. Yes I have > checked and not seen anything obvious but I agree, I need to do some careful > analysis there, which I will proceed to do. If you have any suggestions as > to what to focus on in the logs that would be appreciated. > > Thank you and here are the issues shown by BPA at this time: > > > All Issues > > > Exchange Server 2007 with Service Pack 1 : > The server RIVERSERV is running Exchange Server 2007 with Service Pack 1; > however, Service Pack 2 for Exchange Server 2007 is available. For more > information, see "You cannot install Exchange Server 2007 Service Pack 2 on a > Windows Small Business Server 2008-based computer" in the Microsoft Knowledge > Base at http://go.microsoft.com/fwlink/?LinkId=163940. > > > Add-On Congestion Control Provider : > Add-On Congestion Control Provider is set to ctcp. To disable Add-On > Congestion Control Provider, click Start, and in the Search box type > "command." in the results, right-click Command Prompt, and then click Run as > administrator. At the command prompt, run the following command: netsh int > tcp set global congestion=none > > > Firewall is disabled : > The Firewall has been disabled and by default is enabled on Windows Small > Business Server > > > IE Enhanced Security disabled : > IE Enhanced Security is currently disabled for Administrators. To enable IE > Enhanced Security go to Start/Server Manager and click on the Configure IE > ESC link on the right. > > > Local activation permission to the IIS WAMREG Admin Service required : > The Network Service is missing local activation permissions to the IIS > WAMREG admin Service in accordance with the event ID 10016 in the system > event log. For more information, see KB "Event ID error messages 10016 and > 10017 are logged in the System log after you install Windows SharePoint > Services 3.0" at http://go.microsoft.com/fwlink/?LinkId=128063. Note: This > warning will continue to appear until at least 24 hours have passed since the > most recent occurrence of event 10016. > > > Receive Window Auto-Tuning Level : > Receive Window Auto-Tuning Level is set to normal. To disable Receive > Window Auto-Tuning Level, click Start, and in the Search box type "command." > in the results, right-click Command Prompt, and then click Run as > administrator. At the command prompt, run the following command: netsh int > tcp set global autotuning=disabled > > > Receive-Side Scaling State : > Receive-Side Scaling State is set to enabled. To disable Receive-Side > Scaling, click Start, and in the Search box type "command." in the results, > right-click Command Prompt, and then click Run as administrator. At the > command prompt, run the following command: netsh int tcp set global > rss=disabled > > > remote.riverwebnh.com does not exist in the BackConnectionHostNames registry > key : > The BackConnectionHostNames key should include the value > remote.riverwebnh.com. To resolve this issue, open Registry Editor, and then > locate and click > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > Right-click BackConnectionHostNames, and then click Modify. In the Value data > box, type remote.riverwebnh.com, and then click OK. > > > Service Pack 2 for Windows Server 2008 is not installed : > Service Pack 2 for Windows Server 2008 is not installed on this server. > > > Task Offload : > Task Offload is set to enabled. To disable Task Offload, click Start, and > in the Search box type "command." in the results, right-click Command Prompt, > and then click Run as administrator. At the command prompt, run the the > following command: netsh int ip set global taskoffload=disabled > > > The BackConnectionHostNames registry key does not exist : > The registry key > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames > does not exist. To resolve this issue, open Registry Editor, and then locate > and click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. > Right-click MSV1_0, point to New, and then click Multi-String Value. Type > BackConnectionHostNames, and then press ENTER. > > > The Companyweb value does not exist in the BackConnectionHostNames registry > key : > The Companyweb value does not exist in the BackConnectionHostNames registry > key. To resolve this issue, open Registry Editor, and then locate and click > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > Right-click BackConnectionHostNames, and then click Modify, In the Value data > box, type Companyweb, and then click OK. > > > The log file for the Windows SharePoint Services configuration database is > getting large : > The log file for the Windows SharePoint Services configuration database is > larger than 1 GB in size. For information about how to reduce the size of the > log file, see the Knowledge Base at > http://go.microsoft.com/fwlink/?LinkId=159745. > > > User account does not show in the Windows SBS Console : > The user account Deb Hardy does not have the attributes that are necessary > for it to display in the Windows SBS Console. > > > User account does not show in the Windows SBS Console : > The user account Remote AOD does not have the attributes that are necessary > for it to display in the Windows SBS Console. > > > Windows SharePoint Services 3.0 : > Windows SharePoint Services 3.0 is installed with Service Pack 1. Service > Pack 2 is available. > > > "Al Williams" wrote: > > > I'd verify that none of advanced networking stuff (TCP Chimney Offload, > > etc.) is enabled on the server first, it tends to cause issues with older > > PC's. Have you run the SBS BPA? Anything in the logs of the server or > > clients? > > > > http://support.microsoft.com/kb/951037 > > > > -- > > Allan Williams > > > > > > > > > > OneginNH wrote: > > > Two months ago I completed an uneventful install of SBS 2008 for a > > > company of about 25 users on brand-new hardware. The only > > > significance issues since the install have been performance-related, > > > specifically that browsing shared folders on the server is very slow > > > (displaying the contents of folders, for example). Opening large > > > documents and media files is also very slow, and at least one > > > server-based Visual Foxpro program which ran very fast under the old > > > Server 2003 server slows to a crawl with the new server. However, > > > all these woes disappear if the client is Windows 7 - the speed > > > difference is night and day! Is there something that can be done to > > > tweak Windows XP to perform better with SBS 2008? The client does > > > not have the budget to undertake a migration to Windows 7 at this > > > time. > > > > > > . > >
From: Al Williams on 5 Feb 2010 12:13 The BPA pointed to several "advanced" networking settings that were enabled and should be disabled: Add-On Congestion Control Provider Receive Window Auto-Tuning Level Receive-Side Scaling State Task Offload Fix those first using the instructions given and see if it helps. Also look into the other settings (Firewall is disabled?). -- Allan Williams OneginNH wrote: > Hi Al and thank you for your response. To answer your questions: > > 1) In regard to "advanced networking stuff" I'm not sure where/how > to find that kind of thing. I guess I can poke around. In calling > Intel about this I woudl have thought they could/woudl point me in > this direction (if needed) since both the server NIC and the > workstation NICs are Intel (actually that's not strictly true, one of > the worst performers under Windows XP has a Realtek NIC). But, yes, > what you are suggesting has been on my mind ever since I ran across > that KB 968991 article that I mention elsewhere in this (rather long) > posting - problem with that 968991 article is that it doesn't > strictly apply to my circumstances. But it talks about Intel > Advanced I/O stuff which is what you are pointing me to. Why Intel > wouldn't have known about such an issue is a mystery to me and for > these various reasons I have therefore held off on applying the > 968991 hotfix - do you think I shoudl do it? > > 2) In regard to the SBS BPA I'm a bit embarrassed to say that I had > not run it. Why? Because with the BPA for the Exchange piece built > right in to the O/S, I guess I assumed that the BPA tool for SBS > would be built right into the SBS console alongside all the other > error checking that tool constantly does. Anyway once I saw your > note I immediately downloaded the SBS 2008 BPA. Right off the bat I > did show the only critical error (expected), which was that the DNS A > resource record was pointing to both NIC's on the server. As > mentioned elsehwere in this mammoth post, the second serve NIC got > turned on recently only as an experiemnt and it did not change things > at all. Anyway this mornign I shut off that second NIC again and ran > BPA again and the critical error is gone for DNS. There are no > critical errors. The remaining non-critical issues are, of course, > of concern but I have no idea where to focus/get started -- I need to > solve the slow network problem before I do any of the more refined > fine-tuning stuff - as I'm sure you can appreciate. But perhaps the > key to my performance issus is in these issues, and I have posted > them below (below my next and last answer to your questions) -- if > there is any feedback you can provide I would most appreciate it. > > 3) You ask about logs on the server and the workstations. Yes I have > checked and not seen anything obvious but I agree, I need to do some > careful analysis there, which I will proceed to do. If you have any > suggestions as to what to focus on in the logs that would be > appreciated. > > Thank you and here are the issues shown by BPA at this time: > > > All Issues > > > Exchange Server 2007 with Service Pack 1 : > The server RIVERSERV is running Exchange Server 2007 with Service > Pack 1; however, Service Pack 2 for Exchange Server 2007 is > available. For more information, see "You cannot install Exchange > Server 2007 Service Pack 2 on a Windows Small Business Server > 2008-based computer" in the Microsoft Knowledge Base at > http://go.microsoft.com/fwlink/?LinkId=163940. > > > Add-On Congestion Control Provider : > Add-On Congestion Control Provider is set to ctcp. To disable Add-On > Congestion Control Provider, click Start, and in the Search box type > "command." in the results, right-click Command Prompt, and then click > Run as administrator. At the command prompt, run the following > command: netsh int tcp set global congestion=none > > > Firewall is disabled : > The Firewall has been disabled and by default is enabled on Windows > Small Business Server > > > IE Enhanced Security disabled : > IE Enhanced Security is currently disabled for Administrators. To > enable IE Enhanced Security go to Start/Server Manager and click on > the Configure IE ESC link on the right. > > > Local activation permission to the IIS WAMREG Admin Service required : > The Network Service is missing local activation permissions to the IIS > WAMREG admin Service in accordance with the event ID 10016 in the > system event log. For more information, see KB "Event ID error > messages 10016 and 10017 are logged in the System log after you > install Windows SharePoint Services 3.0" at > http://go.microsoft.com/fwlink/?LinkId=128063. Note: This warning > will continue to appear until at least 24 hours have passed since the > most recent occurrence of event 10016. > > > Receive Window Auto-Tuning Level : > Receive Window Auto-Tuning Level is set to normal. To disable Receive > Window Auto-Tuning Level, click Start, and in the Search box type > "command." in the results, right-click Command Prompt, and then click > Run as administrator. At the command prompt, run the following > command: netsh int tcp set global autotuning=disabled > > > Receive-Side Scaling State : > Receive-Side Scaling State is set to enabled. To disable Receive-Side > Scaling, click Start, and in the Search box type "command." in the > results, right-click Command Prompt, and then click Run as > administrator. At the command prompt, run the following command: > netsh int tcp set global rss=disabled > > > remote.riverwebnh.com does not exist in the BackConnectionHostNames > registry key : > The BackConnectionHostNames key should include the value > remote.riverwebnh.com. To resolve this issue, open Registry Editor, > and then locate and click > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > Right-click BackConnectionHostNames, and then click Modify. In the > Value data box, type remote.riverwebnh.com, and then click OK. > > > Service Pack 2 for Windows Server 2008 is not installed : > Service Pack 2 for Windows Server 2008 is not installed on this > server. > > > Task Offload : > Task Offload is set to enabled. To disable Task Offload, click Start, > and > in the Search box type "command." in the results, right-click Command > Prompt, and then click Run as administrator. At the command prompt, > run the the following command: netsh int ip set global > taskoffload=disabled > > > The BackConnectionHostNames registry key does not exist : > The registry key > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames > does not exist. To resolve this issue, open Registry Editor, and then > locate and click > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. > Right-click MSV1_0, point to New, and then click Multi-String Value. > Type BackConnectionHostNames, and then press ENTER. > > > The Companyweb value does not exist in the BackConnectionHostNames > registry key : > The Companyweb value does not exist in the BackConnectionHostNames > registry key. To resolve this issue, open Registry Editor, and then > locate and click > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > Right-click BackConnectionHostNames, and then click Modify, In the > Value data box, type Companyweb, and then click OK. > > > The log file for the Windows SharePoint Services configuration > database is getting large : > The log file for the Windows SharePoint Services configuration > database is larger than 1 GB in size. For information about how to > reduce the size of the log file, see the Knowledge Base at > http://go.microsoft.com/fwlink/?LinkId=159745. > > > User account does not show in the Windows SBS Console : > The user account Deb Hardy does not have the attributes that are > necessary for it to display in the Windows SBS Console. > > > User account does not show in the Windows SBS Console : > The user account Remote AOD does not have the attributes that are > necessary for it to display in the Windows SBS Console. > > > Windows SharePoint Services 3.0 : > Windows SharePoint Services 3.0 is installed with Service Pack 1. > Service Pack 2 is available. > > > "Al Williams" wrote: > >> I'd verify that none of advanced networking stuff (TCP Chimney >> Offload, etc.) is enabled on the server first, it tends to cause >> issues with older PC's. Have you run the SBS BPA? Anything in the >> logs of the server or clients? >> >> http://support.microsoft.com/kb/951037 >> >> -- >> Allan Williams >> >> >> >> >> OneginNH wrote: >>> Two months ago I completed an uneventful install of SBS 2008 for a >>> company of about 25 users on brand-new hardware. The only >>> significance issues since the install have been performance-related, >>> specifically that browsing shared folders on the server is very slow >>> (displaying the contents of folders, for example). Opening large >>> documents and media files is also very slow, and at least one >>> server-based Visual Foxpro program which ran very fast under the old >>> Server 2003 server slows to a crawl with the new server. However, >>> all these woes disappear if the client is Windows 7 - the speed >>> difference is night and day! Is there something that can be done to >>> tweak Windows XP to perform better with SBS 2008? The client does >>> not have the budget to undertake a migration to Windows 7 at this >>> time. >> >> >> .
From: Al Williams on 5 Feb 2010 12:13 No, I don't think so. BTW - Do not disable IP6 on SBS, that *will* cause issues. -- Allan Williams OneginNH wrote: > To ask an obvious question, could my issue be as simple as not having > IP6 on the XP workstations? Could that be why Windows 7 has no > problems and XP does? > > "OneginNH" wrote: > >> Hi Al and thank you for your response. To answer your questions: >> >> 1) In regard to "advanced networking stuff" I'm not sure where/how >> to find that kind of thing. I guess I can poke around. In calling >> Intel about this I woudl have thought they could/woudl point me in >> this direction (if needed) since both the server NIC and the >> workstation NICs are Intel (actually that's not strictly true, one >> of the worst performers under Windows XP has a Realtek NIC). But, >> yes, what you are suggesting has been on my mind ever since I ran >> across that KB 968991 article that I mention elsewhere in this >> (rather long) posting - problem with that 968991 article is that it >> doesn't strictly apply to my circumstances. But it talks about >> Intel Advanced I/O stuff which is what you are pointing me to. Why >> Intel wouldn't have known about such an issue is a mystery to me and >> for these various reasons I have therefore held off on applying the >> 968991 hotfix - do you think I shoudl do it? >> >> 2) In regard to the SBS BPA I'm a bit embarrassed to say that I had >> not run it. Why? Because with the BPA for the Exchange piece built >> right in to the O/S, I guess I assumed that the BPA tool for SBS >> would be built right into the SBS console alongside all the other >> error checking that tool constantly does. Anyway once I saw your >> note I immediately downloaded the SBS 2008 BPA. Right off the bat I >> did show the only critical error (expected), which was that the DNS >> A resource record was pointing to both NIC's on the server. As >> mentioned elsehwere in this mammoth post, the second serve NIC got >> turned on recently only as an experiemnt and it did not change >> things at all. Anyway this mornign I shut off that second NIC again >> and ran BPA again and the critical error is gone for DNS. There are >> no critical errors. The remaining non-critical issues are, of >> course, of concern but I have no idea where to focus/get started -- >> I need to solve the slow network problem before I do any of the more >> refined fine-tuning stuff - as I'm sure you can appreciate. But >> perhaps the key to my performance issus is in these issues, and I >> have posted them below (below my next and last answer to your >> questions) -- if there is any feedback you can provide I would most >> appreciate it. >> >> 3) You ask about logs on the server and the workstations. Yes I have >> checked and not seen anything obvious but I agree, I need to do some >> careful analysis there, which I will proceed to do. If you have any >> suggestions as to what to focus on in the logs that would be >> appreciated. >> >> Thank you and here are the issues shown by BPA at this time: >> >> >> All Issues >> >> >> Exchange Server 2007 with Service Pack 1 : >> The server RIVERSERV is running Exchange Server 2007 with Service >> Pack 1; however, Service Pack 2 for Exchange Server 2007 is >> available. For more information, see "You cannot install Exchange >> Server 2007 Service Pack 2 on a Windows Small Business Server >> 2008-based computer" in the Microsoft Knowledge Base at >> http://go.microsoft.com/fwlink/?LinkId=163940. >> >> >> Add-On Congestion Control Provider : >> Add-On Congestion Control Provider is set to ctcp. To disable Add-On >> Congestion Control Provider, click Start, and in the Search box type >> "command." in the results, right-click Command Prompt, and then >> click Run as administrator. At the command prompt, run the following >> command: netsh int tcp set global congestion=none >> >> >> Firewall is disabled : >> The Firewall has been disabled and by default is enabled on Windows >> Small Business Server >> >> >> IE Enhanced Security disabled : >> IE Enhanced Security is currently disabled for Administrators. To >> enable IE Enhanced Security go to Start/Server Manager and click on >> the Configure IE ESC link on the right. >> >> >> Local activation permission to the IIS WAMREG Admin Service required >> : >> The Network Service is missing local activation permissions to the >> IIS WAMREG admin Service in accordance with the event ID 10016 in >> the system event log. For more information, see KB "Event ID error >> messages 10016 and 10017 are logged in the System log after you >> install Windows SharePoint Services 3.0" at >> http://go.microsoft.com/fwlink/?LinkId=128063. Note: This warning >> will continue to appear until at least 24 hours have passed since >> the most recent occurrence of event 10016. >> >> >> Receive Window Auto-Tuning Level : >> Receive Window Auto-Tuning Level is set to normal. To disable Receive >> Window Auto-Tuning Level, click Start, and in the Search box type >> "command." in the results, right-click Command Prompt, and then >> click Run as administrator. At the command prompt, run the following >> command: netsh int tcp set global autotuning=disabled >> >> >> Receive-Side Scaling State : >> Receive-Side Scaling State is set to enabled. To disable Receive-Side >> Scaling, click Start, and in the Search box type "command." in the >> results, right-click Command Prompt, and then click Run as >> administrator. At the command prompt, run the following command: >> netsh int tcp set global rss=disabled >> >> >> remote.riverwebnh.com does not exist in the BackConnectionHostNames >> registry key : >> The BackConnectionHostNames key should include the value >> remote.riverwebnh.com. To resolve this issue, open Registry Editor, >> and then locate and click >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. >> Right-click BackConnectionHostNames, and then click Modify. In the >> Value data box, type remote.riverwebnh.com, and then click OK. >> >> >> Service Pack 2 for Windows Server 2008 is not installed : >> Service Pack 2 for Windows Server 2008 is not installed on this >> server. >> >> >> Task Offload : >> Task Offload is set to enabled. To disable Task Offload, click >> Start, and >> in the Search box type "command." in the results, right-click >> Command Prompt, and then click Run as administrator. At the command >> prompt, run the the following command: netsh int ip set global >> taskoffload=disabled >> >> >> The BackConnectionHostNames registry key does not exist : >> The registry key >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames >> does not exist. To resolve this issue, open Registry Editor, and >> then locate and click >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. >> Right-click MSV1_0, point to New, and then click Multi-String Value. >> Type BackConnectionHostNames, and then press ENTER. >> >> >> The Companyweb value does not exist in the BackConnectionHostNames >> registry key : >> The Companyweb value does not exist in the BackConnectionHostNames >> registry key. To resolve this issue, open Registry Editor, and then >> locate and click >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. >> Right-click BackConnectionHostNames, and then click Modify, In the >> Value data box, type Companyweb, and then click OK. >> >> >> The log file for the Windows SharePoint Services configuration >> database is getting large : >> The log file for the Windows SharePoint Services configuration >> database is larger than 1 GB in size. For information about how to >> reduce the size of the log file, see the Knowledge Base at >> http://go.microsoft.com/fwlink/?LinkId=159745. >> >> >> User account does not show in the Windows SBS Console : >> The user account Deb Hardy does not have the attributes that are >> necessary for it to display in the Windows SBS Console. >> >> >> User account does not show in the Windows SBS Console : >> The user account Remote AOD does not have the attributes that are >> necessary for it to display in the Windows SBS Console. >> >> >> Windows SharePoint Services 3.0 : >> Windows SharePoint Services 3.0 is installed with Service Pack 1. >> Service Pack 2 is available. >> >> >> "Al Williams" wrote: >> >>> I'd verify that none of advanced networking stuff (TCP Chimney >>> Offload, etc.) is enabled on the server first, it tends to cause >>> issues with older PC's. Have you run the SBS BPA? Anything in the >>> logs of the server or clients? >>> >>> http://support.microsoft.com/kb/951037 >>> >>> -- >>> Allan Williams >>> >>> >>> >>> >>> OneginNH wrote: >>>> Two months ago I completed an uneventful install of SBS 2008 for a >>>> company of about 25 users on brand-new hardware. The only >>>> significance issues since the install have been >>>> performance-related, specifically that browsing shared folders on >>>> the server is very slow (displaying the contents of folders, for >>>> example). Opening large documents and media files is also very >>>> slow, and at least one server-based Visual Foxpro program which >>>> ran very fast under the old Server 2003 server slows to a crawl >>>> with the new server. However, all these woes disappear if the >>>> client is Windows 7 - the speed difference is night and day! Is >>>> there something that can be done to tweak Windows XP to perform >>>> better with SBS 2008? The client does not have the budget to >>>> undertake a migration to Windows 7 at this time. >>> >>> >>> .
From: OneginNH on 8 Feb 2010 13:28 Hi - I made those four changes to the "advanced" settings and there was no difference in the performance. Do you have any other suggestions at this time? If not then I guess my next steps need to be to install the various service packs mentioned inthe BPA, including SP2 for Sharepoint 3.0 and SP2 for Server 2008. "Al Williams" wrote: > The BPA pointed to several "advanced" networking settings that were enabled > and should be disabled: > Add-On Congestion Control Provider > Receive Window Auto-Tuning Level > Receive-Side Scaling State > Task Offload > > Fix those first using the instructions given and see if it helps. Also look > into the other settings (Firewall is disabled?). > > -- > Allan Williams > > > > > OneginNH wrote: > > Hi Al and thank you for your response. To answer your questions: > > > > 1) In regard to "advanced networking stuff" I'm not sure where/how > > to find that kind of thing. I guess I can poke around. In calling > > Intel about this I woudl have thought they could/woudl point me in > > this direction (if needed) since both the server NIC and the > > workstation NICs are Intel (actually that's not strictly true, one of > > the worst performers under Windows XP has a Realtek NIC). But, yes, > > what you are suggesting has been on my mind ever since I ran across > > that KB 968991 article that I mention elsewhere in this (rather long) > > posting - problem with that 968991 article is that it doesn't > > strictly apply to my circumstances. But it talks about Intel > > Advanced I/O stuff which is what you are pointing me to. Why Intel > > wouldn't have known about such an issue is a mystery to me and for > > these various reasons I have therefore held off on applying the > > 968991 hotfix - do you think I shoudl do it? > > > > 2) In regard to the SBS BPA I'm a bit embarrassed to say that I had > > not run it. Why? Because with the BPA for the Exchange piece built > > right in to the O/S, I guess I assumed that the BPA tool for SBS > > would be built right into the SBS console alongside all the other > > error checking that tool constantly does. Anyway once I saw your > > note I immediately downloaded the SBS 2008 BPA. Right off the bat I > > did show the only critical error (expected), which was that the DNS A > > resource record was pointing to both NIC's on the server. As > > mentioned elsehwere in this mammoth post, the second serve NIC got > > turned on recently only as an experiemnt and it did not change things > > at all. Anyway this mornign I shut off that second NIC again and ran > > BPA again and the critical error is gone for DNS. There are no > > critical errors. The remaining non-critical issues are, of course, > > of concern but I have no idea where to focus/get started -- I need to > > solve the slow network problem before I do any of the more refined > > fine-tuning stuff - as I'm sure you can appreciate. But perhaps the > > key to my performance issus is in these issues, and I have posted > > them below (below my next and last answer to your questions) -- if > > there is any feedback you can provide I would most appreciate it. > > > > 3) You ask about logs on the server and the workstations. Yes I have > > checked and not seen anything obvious but I agree, I need to do some > > careful analysis there, which I will proceed to do. If you have any > > suggestions as to what to focus on in the logs that would be > > appreciated. > > > > Thank you and here are the issues shown by BPA at this time: > > > > > > All Issues > > > > > > Exchange Server 2007 with Service Pack 1 : > > The server RIVERSERV is running Exchange Server 2007 with Service > > Pack 1; however, Service Pack 2 for Exchange Server 2007 is > > available. For more information, see "You cannot install Exchange > > Server 2007 Service Pack 2 on a Windows Small Business Server > > 2008-based computer" in the Microsoft Knowledge Base at > > http://go.microsoft.com/fwlink/?LinkId=163940. > > > > > > Add-On Congestion Control Provider : > > Add-On Congestion Control Provider is set to ctcp. To disable Add-On > > Congestion Control Provider, click Start, and in the Search box type > > "command." in the results, right-click Command Prompt, and then click > > Run as administrator. At the command prompt, run the following > > command: netsh int tcp set global congestion=none > > > > > > Firewall is disabled : > > The Firewall has been disabled and by default is enabled on Windows > > Small Business Server > > > > > > IE Enhanced Security disabled : > > IE Enhanced Security is currently disabled for Administrators. To > > enable IE Enhanced Security go to Start/Server Manager and click on > > the Configure IE ESC link on the right. > > > > > > Local activation permission to the IIS WAMREG Admin Service required : > > The Network Service is missing local activation permissions to the IIS > > WAMREG admin Service in accordance with the event ID 10016 in the > > system event log. For more information, see KB "Event ID error > > messages 10016 and 10017 are logged in the System log after you > > install Windows SharePoint Services 3.0" at > > http://go.microsoft.com/fwlink/?LinkId=128063. Note: This warning > > will continue to appear until at least 24 hours have passed since the > > most recent occurrence of event 10016. > > > > > > Receive Window Auto-Tuning Level : > > Receive Window Auto-Tuning Level is set to normal. To disable Receive > > Window Auto-Tuning Level, click Start, and in the Search box type > > "command." in the results, right-click Command Prompt, and then click > > Run as administrator. At the command prompt, run the following > > command: netsh int tcp set global autotuning=disabled > > > > > > Receive-Side Scaling State : > > Receive-Side Scaling State is set to enabled. To disable Receive-Side > > Scaling, click Start, and in the Search box type "command." in the > > results, right-click Command Prompt, and then click Run as > > administrator. At the command prompt, run the following command: > > netsh int tcp set global rss=disabled > > > > > > remote.riverwebnh.com does not exist in the BackConnectionHostNames > > registry key : > > The BackConnectionHostNames key should include the value > > remote.riverwebnh.com. To resolve this issue, open Registry Editor, > > and then locate and click > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > > Right-click BackConnectionHostNames, and then click Modify. In the > > Value data box, type remote.riverwebnh.com, and then click OK. > > > > > > Service Pack 2 for Windows Server 2008 is not installed : > > Service Pack 2 for Windows Server 2008 is not installed on this > > server. > > > > > > Task Offload : > > Task Offload is set to enabled. To disable Task Offload, click Start, > > and > > in the Search box type "command." in the results, right-click Command > > Prompt, and then click Run as administrator. At the command prompt, > > run the the following command: netsh int ip set global > > taskoffload=disabled > > > > > > The BackConnectionHostNames registry key does not exist : > > The registry key > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames > > does not exist. To resolve this issue, open Registry Editor, and then > > locate and click > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. > > Right-click MSV1_0, point to New, and then click Multi-String Value. > > Type BackConnectionHostNames, and then press ENTER. > > > > > > The Companyweb value does not exist in the BackConnectionHostNames > > registry key : > > The Companyweb value does not exist in the BackConnectionHostNames > > registry key. To resolve this issue, open Registry Editor, and then > > locate and click > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. > > Right-click BackConnectionHostNames, and then click Modify, In the > > Value data box, type Companyweb, and then click OK. > > > > > > The log file for the Windows SharePoint Services configuration > > database is getting large : > > The log file for the Windows SharePoint Services configuration > > database is larger than 1 GB in size. For information about how to > > reduce the size of the log file, see the Knowledge Base at > > http://go.microsoft.com/fwlink/?LinkId=159745. > > > > > > User account does not show in the Windows SBS Console : > > The user account Deb Hardy does not have the attributes that are > > necessary for it to display in the Windows SBS Console. > > > > > > User account does not show in the Windows SBS Console : > > The user account Remote AOD does not have the attributes that are > > necessary for it to display in the Windows SBS Console. > > > > > > Windows SharePoint Services 3.0 : > > Windows SharePoint Services 3.0 is installed with Service Pack 1. > > Service Pack 2 is available. > > > > > > "Al Williams" wrote: > > > >> I'd verify that none of advanced networking stuff (TCP Chimney > >> Offload, etc.) is enabled on the server first, it tends to cause > >> issues with older PC's. Have you run the SBS BPA? Anything in the > >> logs of the server or clients? > >> > >> http://support.microsoft.com/kb/951037 > >> > >> -- > >> Allan Williams > >> > >> > >> > >> > >> OneginNH wrote: > >>> Two months ago I completed an uneventful install of SBS 2008 for a > >>> company of about 25 users on brand-new hardware. The only > >>> significance issues since the install have been performance-related, > >>> specifically that browsing shared folders on the server is very slow > >>> (displaying the contents of folders, for example). Opening large > >>> documents and media files is also very slow, and at least one > >>> server-based Visual Foxpro program which ran very fast under the old > >>> Server 2003 server slows to a crawl with the new server. However, > >>> all these woes disappear if the client is Windows 7 - the speed > >>> difference is night and day! Is there something that can be done to > >>> tweak Windows XP to perform better with SBS 2008? The client does > >>> not have the budget to undertake a migration to Windows 7 at this > >>> time. > >> > >> > >> . > > > . >
From: Al Williams on 8 Feb 2010 13:40 Look into the device manager at the advanced properties of your SBS's NIC and ensure none of the advanced offloading is enabled in there. I'm not sure it matters if disabled in the registry but it couldn't hurt (ensure you reboot). I'd also check the slow PC's NIC settings. Have you verified it is not a network switch issue? Any "pattern" to the slowness w.r.t. how the PC's are connected to the server? Not sure what else to suggest. You may want to post to the SBS08 specific group, you need to join first: https://connect.microsoft.com/ Good luck. -- Allan Williams OneginNH wrote: > Hi - I made those four changes to the "advanced" settings and there > was no difference in the performance. Do you have any other > suggestions at this time? If not then I guess my next steps need to > be to install the various service packs mentioned inthe BPA, > including SP2 for Sharepoint 3.0 and SP2 for Server 2008. > > "Al Williams" wrote: > >> The BPA pointed to several "advanced" networking settings that were >> enabled and should be disabled: >> Add-On Congestion Control Provider >> Receive Window Auto-Tuning Level >> Receive-Side Scaling State >> Task Offload >> >> Fix those first using the instructions given and see if it helps. >> Also look into the other settings (Firewall is disabled?). >> >> -- >> Allan Williams >> >> >> >> >> OneginNH wrote: >>> Hi Al and thank you for your response. To answer your questions: >>> >>> 1) In regard to "advanced networking stuff" I'm not sure where/how >>> to find that kind of thing. I guess I can poke around. In calling >>> Intel about this I woudl have thought they could/woudl point me in >>> this direction (if needed) since both the server NIC and the >>> workstation NICs are Intel (actually that's not strictly true, one >>> of the worst performers under Windows XP has a Realtek NIC). But, >>> yes, what you are suggesting has been on my mind ever since I ran >>> across that KB 968991 article that I mention elsewhere in this >>> (rather long) posting - problem with that 968991 article is that it >>> doesn't strictly apply to my circumstances. But it talks about >>> Intel Advanced I/O stuff which is what you are pointing me to. Why >>> Intel wouldn't have known about such an issue is a mystery to me >>> and for these various reasons I have therefore held off on applying >>> the 968991 hotfix - do you think I shoudl do it? >>> >>> 2) In regard to the SBS BPA I'm a bit embarrassed to say that I had >>> not run it. Why? Because with the BPA for the Exchange piece built >>> right in to the O/S, I guess I assumed that the BPA tool for SBS >>> would be built right into the SBS console alongside all the other >>> error checking that tool constantly does. Anyway once I saw your >>> note I immediately downloaded the SBS 2008 BPA. Right off the bat I >>> did show the only critical error (expected), which was that the DNS >>> A resource record was pointing to both NIC's on the server. As >>> mentioned elsehwere in this mammoth post, the second serve NIC got >>> turned on recently only as an experiemnt and it did not change >>> things at all. Anyway this mornign I shut off that second NIC >>> again and ran BPA again and the critical error is gone for DNS. >>> There are no critical errors. The remaining non-critical issues >>> are, of course, of concern but I have no idea where to focus/get >>> started -- I need to solve the slow network problem before I do any >>> of the more refined fine-tuning stuff - as I'm sure you can >>> appreciate. But perhaps the key to my performance issus is in >>> these issues, and I have posted them below (below my next and last >>> answer to your questions) -- if there is any feedback you can >>> provide I would most appreciate it. >>> >>> 3) You ask about logs on the server and the workstations. Yes I >>> have checked and not seen anything obvious but I agree, I need to >>> do some careful analysis there, which I will proceed to do. If you >>> have any suggestions as to what to focus on in the logs that would >>> be appreciated. >>> >>> Thank you and here are the issues shown by BPA at this time: >>> >>> >>> All Issues >>> >>> >>> Exchange Server 2007 with Service Pack 1 : >>> The server RIVERSERV is running Exchange Server 2007 with Service >>> Pack 1; however, Service Pack 2 for Exchange Server 2007 is >>> available. For more information, see "You cannot install Exchange >>> Server 2007 Service Pack 2 on a Windows Small Business Server >>> 2008-based computer" in the Microsoft Knowledge Base at >>> http://go.microsoft.com/fwlink/?LinkId=163940. >>> >>> >>> Add-On Congestion Control Provider : >>> Add-On Congestion Control Provider is set to ctcp. To disable Add-On >>> Congestion Control Provider, click Start, and in the Search box type >>> "command." in the results, right-click Command Prompt, and then >>> click Run as administrator. At the command prompt, run the following >>> command: netsh int tcp set global congestion=none >>> >>> >>> Firewall is disabled : >>> The Firewall has been disabled and by default is enabled on Windows >>> Small Business Server >>> >>> >>> IE Enhanced Security disabled : >>> IE Enhanced Security is currently disabled for Administrators. To >>> enable IE Enhanced Security go to Start/Server Manager and click on >>> the Configure IE ESC link on the right. >>> >>> >>> Local activation permission to the IIS WAMREG Admin Service >>> required : The Network Service is missing local activation >>> permissions to the IIS WAMREG admin Service in accordance with the >>> event ID 10016 in the system event log. For more information, see >>> KB "Event ID error messages 10016 and 10017 are logged in the >>> System log after you install Windows SharePoint Services 3.0" at >>> http://go.microsoft.com/fwlink/?LinkId=128063. Note: This warning >>> will continue to appear until at least 24 hours have passed since >>> the most recent occurrence of event 10016. >>> >>> >>> Receive Window Auto-Tuning Level : >>> Receive Window Auto-Tuning Level is set to normal. To disable >>> Receive Window Auto-Tuning Level, click Start, and in the Search >>> box type "command." in the results, right-click Command Prompt, and >>> then click Run as administrator. At the command prompt, run the >>> following command: netsh int tcp set global autotuning=disabled >>> >>> >>> Receive-Side Scaling State : >>> Receive-Side Scaling State is set to enabled. To disable >>> Receive-Side Scaling, click Start, and in the Search box type >>> "command." in the results, right-click Command Prompt, and then >>> click Run as administrator. At the command prompt, run the >>> following command: netsh int tcp set global rss=disabled >>> >>> >>> remote.riverwebnh.com does not exist in the BackConnectionHostNames >>> registry key : >>> The BackConnectionHostNames key should include the value >>> remote.riverwebnh.com. To resolve this issue, open Registry Editor, >>> and then locate and click >>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. >>> Right-click BackConnectionHostNames, and then click Modify. In the >>> Value data box, type remote.riverwebnh.com, and then click OK. >>> >>> >>> Service Pack 2 for Windows Server 2008 is not installed : >>> Service Pack 2 for Windows Server 2008 is not installed on this >>> server. >>> >>> >>> Task Offload : >>> Task Offload is set to enabled. To disable Task Offload, click >>> Start, and >>> in the Search box type "command." in the results, right-click >>> Command Prompt, and then click Run as administrator. At the command >>> prompt, run the the following command: netsh int ip set global >>> taskoffload=disabled >>> >>> >>> The BackConnectionHostNames registry key does not exist : >>> The registry key >>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames >>> does not exist. To resolve this issue, open Registry Editor, and >>> then locate and click >>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\. >>> Right-click MSV1_0, point to New, and then click Multi-String Value. >>> Type BackConnectionHostNames, and then press ENTER. >>> >>> >>> The Companyweb value does not exist in the BackConnectionHostNames >>> registry key : >>> The Companyweb value does not exist in the BackConnectionHostNames >>> registry key. To resolve this issue, open Registry Editor, and then >>> locate and click >>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames. >>> Right-click BackConnectionHostNames, and then click Modify, In the >>> Value data box, type Companyweb, and then click OK. >>> >>> >>> The log file for the Windows SharePoint Services configuration >>> database is getting large : >>> The log file for the Windows SharePoint Services configuration >>> database is larger than 1 GB in size. For information about how to >>> reduce the size of the log file, see the Knowledge Base at >>> http://go.microsoft.com/fwlink/?LinkId=159745. >>> >>> >>> User account does not show in the Windows SBS Console : >>> The user account Deb Hardy does not have the attributes that are >>> necessary for it to display in the Windows SBS Console. >>> >>> >>> User account does not show in the Windows SBS Console : >>> The user account Remote AOD does not have the attributes that are >>> necessary for it to display in the Windows SBS Console. >>> >>> >>> Windows SharePoint Services 3.0 : >>> Windows SharePoint Services 3.0 is installed with Service Pack 1. >>> Service Pack 2 is available. >>> >>> >>> "Al Williams" wrote: >>> >>>> I'd verify that none of advanced networking stuff (TCP Chimney >>>> Offload, etc.) is enabled on the server first, it tends to cause >>>> issues with older PC's. Have you run the SBS BPA? Anything in the >>>> logs of the server or clients? >>>> >>>> http://support.microsoft.com/kb/951037 >>>> >>>> -- >>>> Allan Williams >>>> >>>> >>>> >>>> >>>> OneginNH wrote: >>>>> Two months ago I completed an uneventful install of SBS 2008 for a >>>>> company of about 25 users on brand-new hardware. The only >>>>> significance issues since the install have been >>>>> performance-related, specifically that browsing shared folders on >>>>> the server is very slow (displaying the contents of folders, for >>>>> example). Opening large documents and media files is also very >>>>> slow, and at least one server-based Visual Foxpro program which >>>>> ran very fast under the old Server 2003 server slows to a crawl >>>>> with the new server. However, all these woes disappear if the >>>>> client is Windows 7 - the speed difference is night and day! Is >>>>> there something that can be done to tweak Windows XP to perform >>>>> better with SBS 2008? The client does not have the budget to >>>>> undertake a migration to Windows 7 at this time. >>>> >>>> >>>> . >> >> >> .
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: Reinstall Intranet post-full restore (2x)... Next: SBS 2008 with integrated SP2 |