locked
500.19 error NetBios command limit RRS feed

  • Question

  • User71546855 posted

     

     We have about 300 domains on a web farm of 4 web servers (NLB), 2 ftp servers(NLB), and 2 file servers(failover cluster) and one (1) codebase server.  All of these are on Enterprise Server 2008R2 except for the codebase server, which is 2003 sp1.  The domains are in several app pools with several (up to 40) sites in each.  Each app pool has websites according to the first letter of their domain name.  The file server has the files for each web site.

    Recently we've been getting 500.19 error 0x80070038.  This corresponds to Win32 error 56, netbios command limit reached.

    I've tried to implement the registry settings:

    HKLM\Services\CurrentControlSet\lanmanserver\MaxMpxCt = 5000 \MaxWorrkItems = 25000

    MKLM\Services\CurrentControlSet\lanmanworkstation\MaxCmds = 5000

    Still, a few times a day, I get the 500.19 error and I have to recycle some app pools to relieve the problem.  I'd like to relieve the problem for good.  Any suggestions?

     

    Wednesday, March 17, 2010 2:21 PM

Answers

  • User71546855 posted

     We found my error by using a registry comparison tool in Registry Workshop.  The SMB2 was turned off in the errored web server.  I'm all set now.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Friday, March 19, 2010 8:40 AM

All replies

  • User1073881637 posted

    Take a look at this thread.

    http://forums.iis.net/t/1158781.aspx

    Thursday, March 18, 2010 2:20 AM
  • User71546855 posted

     What is described in both http://technet.microsoft.com/en-us/library/dd296685%28WS.10%29.aspx and http://technet.microsoft.com/en-us/library/dd296694%28WS.10%29.aspx worked for three out of four of our servers.  We can't seem to figure out why the fourth server is still seeing TOO MANY COMMANDS in Procmon when viewing our sites with UNC paths.  Any other suggestions?

     

    Thursday, March 18, 2010 11:19 AM
  • User71546855 posted

     We found my error by using a registry comparison tool in Registry Workshop.  The SMB2 was turned off in the errored web server.  I'm all set now.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Friday, March 19, 2010 8:40 AM
  • User1073881637 posted

    I'll be marking this thread!  Thanks a million + 1 for reporting how you fixed it.  This will DEFINITELY help the community,

    Friday, March 19, 2010 5:35 PM