Error 36:sharing buffer overflow - Page 2
Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22

Thread: Error 36:sharing buffer overflow

  1. #16
    Join Date
    Apr 2000
    Posts
    1,579
    What do you mean the machines are using "flash" to boot?
    What type of flash? A special memory card or something?
    Are you saying you are booting with a special "remote boot" PROM... (Programmable Read-Only Memory) usually installed on the network adapter card? These are sometimes used on computers without disk drives to boot from. So, are the two computers absent a disk drive to boot from?

    Is it possible to bring the working node network connection to a halt without disrupting important work activity? For example, at 4AM is the application program being used or needed?
    Then you could try booting the node with the problem again and see if you can get it operating as expected or otherwise see what happens.
    Are the two nodes trying to use the same remote server computer?
    If not, then the computer name and share name should be different.
    Last edited by Robert M; August 22nd, 2005 at 08:23 PM.
    Open your mind, not your computer.

  2. #17
    Join Date
    Apr 2000
    Posts
    1,579
    In the CONFIG.SYS file contents that you posted.......
    The shell= line has a blank space after the colon and before the backslash. Is the blank space present in the working computer's config.sys file?
    Open your mind, not your computer.

  3. #18
    Join Date
    Apr 2000
    Posts
    1,579
    Hello.....
    Any luck straightening this problem?
    If so, what was the magic bullet?
    Open your mind, not your computer.

  4. #19
    Join Date
    Feb 2006
    Posts
    1
    If your DHCP is on a Windows 2003 server you need need to disable the Smb signing in your domain controller security settings. Under local policies...security options. Don't forget its the server that need to have the SMB signing deactivated not the client.

    Dos networkcard drivers do not support SMB signing, nor does Linux or NT4, so you will be unable to draw an IP. or communicate with the server in anyway.

    My 2 cents worth.

  5. #20
    Join Date
    Sep 2014
    Posts
    1
    Just ran into this same issue. I solved it by changing the computername parameter in system.ini to something 8 characters or shorter.

  6. #21
    Join Date
    May 2015
    Posts
    6
    With DOS if you laod too amny or not enough DOS will not automatically load high[well it will but only 9k instead of the 20 soemthing K] to which is really debilitating on memory.Maybe this may have an affect

  7. #22
    Join Date
    May 2015
    Posts
    6

    Sorry the keyboard I have has a terrible bounce.If you dont add enough DOS buffers or too many DOS will not laod high,umb even if specified auto.Maybe this has an affect

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •