• Home
  • Consulting
  • Contact Us
    • About this site
    • Contact Wayne
    • Media Room
    • Wayne’s Bio

SBSFAQ.COM

Supporting IT Pro's & MSP's since 2000

  • Blog
  • FAQs
  • Reviews
  • Downloads

Interesting W2003 SP2 Side Effect

January 11, 2008 by Wayne Small 4 Comments

I was onsite earlier this week helping out a friend with his SBS 2003 installation. He had done the install himself and all things looked pretty much ok. He had applied W2003 Service Pack 2 as well. I showed him how to setup computers and all worked well – he added the computers to the domain and proceeded to use the server for a week or so without problems. His server is a 2 NIC installation and he was running SBS 2003 R2 standard ie – without ISA 2004. I visited site to help do the ISA install and make sure things worked fine. ISA went in just fine and we could then surf the web without problems. One interesting thing though was that SBS Companyweb would not display. It worked fine before installing ISA on the server but would not work at all on the workstations. The natural thing to point the finger at was therefore ISA – I mean it was the only thing that had changed recently.

Accessing http://companyweb came back with a DNS error. I attempted to do some diagnosis of this problem and found I could ping the server by name just fine, but companyweb would not resolve to an IP at all. I checked DNS to confirm that it had the normal CNAME record for companyweb pointing to the SBS servers name and it was there just as it’s supposed to be. Ok – so I wondered why won’t this resolve?

I thought I would try another approach. I added an A record called WRSTEST and pointed it to the SBS severs IP – this worked fine and I could ping the WRSTEST without issues. I then created WRSTEST1 as a CNAME record and tried to ping again. It didn’t work – it would not resolve the CNAME record, but it would resolve an A record. Something real strange here I thought and then it hit me… Strange things on a W2003 server with Service Pack 2 on it are ALMOST ALWAYS caused by RSS/TCPA/TCPChimney being turned on.

I had not checked this on his server as it was something that I do by default these days when I install a server and didn’t think to check it earlier given that it was working fine. So I ran the reg hacks to disable these bits on the TCPIP stack, rebooted and things worked just fine again.

So – I fixed the problem, and in the course of investigating it realised that this issue can affect much more than simple communications.

Share this:

  • Click to share on Facebook (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to print (Opens in new window)

Filed Under: Blog Tagged With: Troubleshooting

About The Author

Wayne has been working with Microsoft Server products in the SMB market for over 20 years. He has a passion for technology and been a Microsoft MVP for over 15 years. Read More…

Comments

  1. Mark Chodos says

    January 12, 2008 at 2:35 am

    We are having this exact same problem and could not find a reoslution. Could you please provide details on what Reg entries need to be changed?

    Thank you.

    Reply
  2. Simon Budden says

    January 16, 2008 at 6:01 pm

    Hi Wayne,
    Very interesting indeed, as i have had this EXACT problem on a few SBS2K3 installations. My workaround was to freshly install the OS and not use the image supplied with the server. This worked when required but may have also been coincidence.
    Are you able to provide me with the reg hacks required to disable the RSS/TCPA/TCPChimney?

    Reply
  3. Wayne Small says

    January 16, 2008 at 9:28 pm

    The MS KB article which details this some more is available here. http://support.microsoft.com/kb/936594/
    The TCPChimney registry entry is in there too. Whack it off and your good to go.

    Reply
  4. Micheal Kilpatric says

    January 25, 2008 at 6:38 am

    Look at http://support.microsoft.com/kb/912222, this details the actual reg keys as well. I just recently worked on a different case related to Windows 2003, however, I have been informed this is much like the DCOM security crunch in 2006.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Connect Online With Us

  • Facebook
  • Twitter

Reviews

Splashtop – Cost Effective Remote Control Software

September 22, 2017 By Wayne Small 2 Comments

Western Digital DL4100 NAS

March 3, 2015 By Wayne Small Leave a Comment

SBS 2011 Configuring Certification Guide (70-169)

August 7, 2012 By Wayne Small 4 Comments

Site News

Exchange Bug Stops Mail Delivery in 2022

January 2, 2022

Huge bug found in Intel CPU that could permit hackers to steal your data

January 4, 2018

Recent Posts

  • MS Exchange Zero Day and RemotePowerShell Disabling on Admin accounts
  • Setup changes for Exchange 2016 and Exchange 2019
  • Bluetooth Mouse and Keyboard Randomly Stop Responding
  • Exchange Bug Stops Mail Delivery in 2022
  • How to open and search extremely large text log files

Tags

Antivirus Backup Business Focus Cloud Computing Community Conferences Disaster Recovery Exchange 2010 Exchange Server Future Products Hyper-V Installation Microsoft Migration Patches Personal Rants SBS 4.5 SBS 2000 SBS 2000 SP1 SBS 2003 SBS 2003 Premium SBS 2003 R2 SBS 2003 R2 Premium SBS 2003 R2 Standard SBS 2003 SP1 Premium SBS 2003 SP1 Standard SBS 2003 Standard SBS 2008 SBS 2008 R2 SBS 2011 SBS 2011 Essentials SBS 2011 Standard Security Service Packs ShadowProtect SMB Community Software Software I use StorageCraft Training TrendMicro Troubleshooting Virtualisation Windows Server 2012 Essentials

Terms of Use

Privacy Policy

Copyright © 2023 · Magazine Pro Theme on Genesis Framework · WordPress · Log in