I have a dos box that has 2 partitons along with a Linksys LNE100TX v2.0 NIC. The primary partition has the original dos and the second one has FreeDos installed.

I installed the Microsoft Network-Client 3.0 on the original dos system so I can network my dos box to my XP system. I had to update my Network client to enabled sharing access along with printing.

Good news is that my XP system recognizes the server and is displayed as a "MS-DOS Peer Server" and then displays the computer name.

The bad news is that I cannot access the dos box network(can't see what is sharing), saying that I might not have the permissions to access the network.

I checked the sharing list on the client network and the share folder is displayed as sharing("net share" in command prompt).

What could be the reason why I cannot access my dos box's network? I can ping the ip (automatted). "net start server" in the autoexec batch file does state "Share.exe not found" when the system starts...

Jeff in 7 ways...

On the XP PC in COMMAND PROMPT access the share from there, it is a foible of W2K/XP that you can not access from the GUI.

http://www.computerhope.com/issues/ch000534.htm

Though the article states MS-DOS Prompt in W2K/XP it is not MS-DOS it should read as NT COMMAND PROMPT.

Ok, I was able to add the shared directory from dos by using "net use i: \\DOSCOMP\TEMP\" and it took forever to do but it saved that network as the I: drive but it locked up explorer and I couldn't view any of the files (everything took really long using "net" or anything inside the I: drive). not even "dir" worked in the command line inside the drive letter(Saying it was invalid for the drive???)

My dos box can't even see my xp system but it can ping to the ip, which I don't understand why.

Is there another way to access the network in DOS?

Jeff in 7 ways...

This is for NT4 Server, but basics are similar to later NT O/S:

http://www.microsoft.com/technet/archive/msdos/dosnet.mspx

This is I consider the ultimate help pages, you have installed both Client and server on the MS-DOS PC ??

http://www.wown.com/j_helmig/dosclnt3.htm
http://www.wown.com/j_helmig/dosservr.htm

If all else fails I would suggest to use Lantastic 8.0:

http://www.spartacom.com/products/lantastic.htm

ALSO SHOULD THIS NOT BE IN THE NETWORKING FORUM!!

Ah, yes. wown.com was what I referenced to in installing the Client network on my dos box. It was very helpful!

Yes I did install both the client network and the server update. It's kind of like XP sees the dos system but can't really communicate with it. If having NetBeui installed with TCP/IP is an issue on MS-DOS, then I can try just setting up TCP/IP. Although I had a perfect network connection between 95 OSR2 and XP with NetBeui and IPX/SPX installed.

I'll try Lantastic and see where I can go from there.

Jeff in 7 ways...

I only ever use TCP/IP as XP does not by default support NETBEUI, and IPX/SX is only for Novel Knitware. Therefore have three disks NWC3, TCP/IP and SERVER

On the DOS PC you should be able to get the popup box showing shares on other PC's.

On Windows 95/NT and later in a Command/MSDOS Prompt Box you should be able to access the share but may have to write out the full path:

ie NET USE [driveletter:] \\ComputerName\ShareName

Well I decided to redo everything including the partitioning (Just having a single fat16 partition for MSDOS 6.22) and I installed MSNC 3.0 without the modifications of the driver list from wown.com and everything, ... well works!

I can even access my shared files from my XP system through the dos box. I can also access the shared drive from the dos box by like you said using the command prompt in XP.

The thing is I don't know what commands could be used for the network drive letter in the command prompt inside XP, but explorer can view it's contents without a problem.

All I gotta figure out now is how to free up some memory. Right now I have a cd-rom, mouse, and sound drivers installed on the dos box leaving only 451KB and 15KB Upper memory (I need at least 560 for some DOS programs).

Thanks for your help!

Jeff in 7 ways...

Oh btw, I didn't install NetBeui, just TCP/IP.

Jeff in 7 ways...

MS-DOS6.xx

First off what type of Sound card have you got ?? If it is sound blaster compatible you can use the SET BLASTER statement in AUTOEXEC.BAT.

http://www.computerhope.com/ac.htm

Secondly at the C:\ prompt type MEMMAKER and press enter accepting the defaults..

Last but not least I have never managed more than 500K with either MS-DOS6 or PC-DOS7. Therefore only use NWC3.0 as a last resort, I use boot disks wherever feasible and either WATTCP or FileMaven, though it does cause problems accessing NTFS drives.

If you wish to know more about MS-DOS6 then give X86's website a look at, if it is down keep trying, they he is biased against Windows Compatibility to MS-DOS:

http://83.67.55.228/index.htm

Great to see it does now work, not the easiest to setup, but a worthwhile challenge..........

I have a Creative Vibra 16S CT2800 ISA Sound Card. I downloaded some DOS/OS2 Drivers that came with an installation package so everything is pretty much set in the autoexec file.

I tried running memmaker and for the final test I got network software loading errors during the boot(not sure what they were). So I just did a load high on my sound, cd-rom and mouse drivers and now getting about 482KB. I had to set EMM386.EXE before I could use memmaker because my upper block memory was at flat 0. But I don't think that had to do with why memmaker didn't work(Although I couldn't run memmaker until I added EMM386).

I think I'm going to try LANtastic because there is one specific game that requires 560KB that has network capability, otherwise all my other games seem to load without any problems.

Thanks for the links and yes I did learn something new, that MSDOS can do networking! :)

Jeff in 7 ways...