Printable View
am trying to setup my machine to access a network share from DOS so that I can perform a Ghost of my hard drive.
I am using MSDos 3.11 and my TCP/IP stack is setup correctly, because I can ping the machine from another machine on the network.
When I type the net logon command it tells me that the workstation service has not been started and asks me to start it. When I respond I get the following error message:
Error 36: The system has detected an overflow in the sharing buffer.
DOS3.11 ? That's ancient (Compaq DOS ?), or is it a DOS/Win3.11 (DOS 6.xx)?
Anyway, have you tried increasing either the /F: or /L: values on SHARE.EXE?
http://www.vfrazee.com/ms-dos/6.22/help/share.htm
that is microsoft network client for MS-DOS version is 3.11
redirector version is 2.51
i tried share command but not avilable.says bad command.
any other solution
No, sorry, too small a SHARE.EXE buffer was all that occurred to me with my miniscule DOS network experience. Someone else may have more ideas.Quote:
Originally Posted by niranjan
Don't know what's going on but I have a couple of questions.
What operating system is running at the computer where the share is located?
Do you have any net start command or net start workstation command on the MS-DOS client in the autoexec.bat file?
Can you provide the exact wording of the message?
Is the client strictly an MS-DOS workstation? No Windows?
Maybe the following links can help.
http://support.microsoft.com/default...b;en-us;238640
http://support.microsoft.com/default...b;en-us;183858
http://support.microsoft.com/default...b;en-us;135465
hi
microsoft network client for MS-DOS version is 3.11
redirector version is 2.51
is loaded on windows 95 it si in flash.
we have an IO system designed for a specific application.it consists two nodes for redundency.one is working fine with same config.sys and autoexec.bat files.
we connect to remote servar using
net use * \\servername\sharename.
please look at config.sys and autoexec.bat files mentioned below.
my config.sys file is
Config.sys
.....................
Device=c:\dos\himem.sys \testmem:off
Dos=high,umb
Device=c:\dos\emm386.exe noems
Files=30
Buffers=3
Lastdrive=z
Shell=c: \command.com /p /e:1024
Devicehigh=c:\dos\ifshlp.sys
and my autoexec.bat file is
.............................
@echo off
cls
path=c:\;c:\dos;c:\net;c:\tools
smartdrv /u
set TEMP=C:\TEMP
REM lh keyb sv
lh doskey /insert >NUL
set COMSPEC=c:\command.com
net initialize
netbind
umb
tcptsr
tinyrfc
nmtsr
emsbfr
net logon /savepw:no /yes
thank you and regards
niranjan
Hmmm...
No "net start" command in the autoexec.bat file.
What OS is running at the share you are trying to reach?
I think you should have a command in the autoexec.bat file similar to one of the following somewhere before the net logon command.
net start workstation basic
net start workstation full
Have you recently edited the autoexec.bat file or run a setup or install program which may have modified it?
What is the name of your redirector file?
Are you trying the net logon command at a command prompt after you begin the graphic user interface for Windows 95? If so, I don't think that method will work. You should use the F8 key and boot to command prompt only before trying it.
Here's some other information
http://support.microsoft.com/default...b;en-us;131035
http://support.microsoft.com/default...b;en-us;122494
http://support.microsoft.com/kb/122123/EN-US/
http://support.microsoft.com/default...b;en-us;124175
Where are you reading the following version information you posted? You said:
microsoft network client for MS-DOS version is 3.11
Someone in Germany (I think) has seen that Error 36 message.
He referred to a Microsoft KB article written in German (I think) here.
http://techsupport.softservice.de/kb...5&cNode=8P1T2M
This seems to be the relevant Packet Signing information in english at the link below. Apparently the Network Client for MS-DOS cannot deal with SMB signing or something like that.
http://support.microsoft.com/default...b;en-us;887429
i am giving net start command at c:/NET> prompt.
it says
The WORKSTATION service is not started.
Is it OK to start it? (Y/N) [Y]:
Error 36: The system has detected an overflow in the sharing buffer.
i have never edited autoexec.bat file and with same file it is working with other node.
there is no redirctor file it seems. how to find it?
at c:/NET>net ver
gives
microsoft network client for MS-DOS version is 3.11
i am getting same error as like mentioned in german.but i dont know german.
Here's my understanding:
Two redirectors can be started with the net.exe file.
One for Netware and the other for Microsoft.
The redirector which loads depends on the choices made at setup time when the program was installed.
By the way......
That net ver command on my computer returns a different result.
I have Windows 95 on my machine. It yields version 4.00.950.
I wonder if you have the wrong version of the net.exe file?
Your CONFIG.SYS entry for Buffers 3 doesn't seem right.
Not sure though.I posted some information in English also.
Where are you getting that version 2.51 info?
Did you do a line by line comparison of the config.sys file with the computer that seems to be working? What are the differences?
Do you have a file called protocol.ini in the C:\NET directory?
hi Robert
yes i compared both config.sys files.They are exactly same. yes i have protocol.ini file in c:\NET directory.
You are booting with a floppy disk or a hard drive at each?
Compare all the files in the C:\net directory at each location
Compare the contents of the PROTOCOL INI files at both locations.
First, you better back up the PROTOCOL.INI files at both locations.
Make a copy of the PROTOCOL.INI file at each location and call them protocol.xxx
You should be able to open the PROTOCOL.INI files with the Windows notepad.exe program or the MS-DOS edit program. Be careful not to change the contents and do not open them with a word processor such as word.
Once they are open with either of these programs, you can save them with a new name.....PROTOCOL.XXX...to make a copy of them.
What kind of network adapter is being used at the station displaying the message? What speed? How about at the node with no problem?
Identical computers? Where did you read the version 2.51 info?
How did you obtain the MS-DOS client...download or from a Windows NT Server CD-ROM? Both locations?
we are booting with flash on special board,all files are exactly same.it is loaded by the manufaturer itself.
i am getting version info on at c:\net dos prompt.
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.
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?
Hello.....
Any luck straightening this problem?
If so, what was the magic bullet?
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.
Just ran into this same issue. I solved it by changing the computername parameter in system.ini to something 8 characters or shorter.
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
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