What drivers are you loading?

PCI/ISA NICs shouldn't matter, as long as you have the correct drivers for them.

I have successfully got a DOS IPX network going although it was quite a while ago.
I needed an LSL.COM file, a packet driver for the network card and a protocol driver- IPXODI.COM
I was mainly using Realtek 8029 cards as they were cheap and easy to find.

I haven't had much experience with TCP/IP under DOS although Bart's Boot Disk is set up for this, so perhaps that would be good to look at and steal drivers etc from 😀

Petty much all Realtek Chipset model work in dos the best one when it come to dos from I recall was RTL8029 or 8139 there base round the Novell NE2000 compatible thei or look for 3com
The Linksys EtherFast PCM200 has a ADMtek AN985 chipset which base on the DEC-Tulip compatible what driver are you try to used?.
Have try this
http://download.driverguide.com/driver/Linksy … ys/d311269.html
or
http://www.nodevice.com/driver/PCM200/get43675.html
Your PCI cards Bus may need drivers as well

I don't know if this will help
http://www.jacco2.dds.nl/samba/dos.html
Try Google
Microsoft Network Client for MS-DOS
or
Microsoft LAN Manager Client for MS-DOS

SMC I think it to was base DEC-Tulip compatible as well
And you need rigth dos driver for them to work

DonutKing that good idea Bart's Boot Disk

Thanks

I tried using the NE2000 compatible and NE1000 compatible drivers. I then tried the DEC Ethernet (all types) driver. I didn't know whether it was NE1000 or NE2000 compatible. Then, I found this. I tried the Windows 98 driver, which worked (I now have a "AMDtek AN985 Based Fast Ethernet Adapter" (btw, has anyone noticed that my old network driver was actually for a laptop NIC? I have no idea why it worked for my PCI desktop NIC.)). I couldn't get Microsoft Network Client to recognise the DOS driver, however. I tried MS Lan Manager, but it wouldn't install (error code 2 when reading certain files).

However, I've realised there's not much point in this because I'm trying to access this computer (and the other computer) from another computer and I would like to be able to do this outside Windows 98. I assume I need some sort of server software for this?

AdamP wrote:

However, I've realised there's not much point in this because I'm trying to access this computer (and the other computer) from another computer and I would like to be able to do this outside Windows 98. I assume I need some sort of server software for this?

Not really. I used to use Microsoft's DOS networking software to connect (via TCP/IP, I think) to WFWG 3.11 shares back in the day.

Are you trying to connect to shared folders on another Windows 98 computer? Have you tried the aforementioned Bart's Boot Disk?

hi

i currently use a realtek 8029 with PCIPKT.COM a realtek
8139 with RTSPKT.COM and surecom with FEAPKT.COM
which are all PCI and for ISA i use PNPPD.COM with a
UMC ne2000 clone.

i can report that all of the above work fine for me with
mTCP which includes an ftp server. setting up the ftp
server is trivial and allows file transfers in DOS.

you can also investigate WATTCP and PC/TCP which
are other TCP/IP drivers for DOS but mTCP just works.

bye

Thanks

This is what I'm trying to do:

Computer A - Windows 7 laptop

Computer B - Compaq Deskpro 6400 (Windows 98)

Computer C - Packard Bell Platinum 2030 (Windows 98SE)

I'm trying to make computers B and C accessible by computer A without having to be in Windows 98. Computer A is never connected to both computer B and C at the same time. Computer C also has a separate standalone installation of MS-DOS 7.1

I also got Microsoft Network Client to use the DOS driver. It recognises the NIC, but I get various errors and the computer freezes at netbind.com (I tried to do a picture but it was too bright).

No, I haven't tried the boot disk yet.

hi

i don't know much about ancient windows networking
however two things come to mind.

1. netbios/netbeui i don't suppose this is used any more
or if available enabled. not sure if this tool you are
trying uses this but don't ask me talk to a windows
admin.

2. lan manager auth. i get the impression that the old
method of workgroup or domain logins is no longer
supported or if supported perhaps disabled. again, talk
to a windows admin if you can find one.

you ought to really explain what it is you want to do
on these remote machines from windows 7. if it's
just accessing files then running an ftp server on the
dos machine is adequate.

if you want to remote control the remote machine then
you could locate PC/TCP and install TINY HOST. this
is much like remote desktop for dos.

bye

edit: missing word

I'm not quite getting the intent, too. If you want to access the Windows 9x computers, why the Windows 3.11 topic?
And as sklawz writes, it's important to know what your intent is. For controlling the 9x machines a VNC software should work fine without having to do much else as ling as the machines are in the network.

All I'm trying to do is make the hard drives in the Windows 98 machines accessible from the Windows 7 laptop when I'm not in Windows 98 (e.g. in DOS mode or Windows 3.1). When in Windows 98, I can just copy files (from the Windows 7 laptop to the Windows 98 machine, but not the other way around; I assume it's something to do with Windows 7's security) directly to it normally. Is there no way to do this while the machine's in DOS? How difficult would it be to set up an FTP server?

ah, now I get it at least. Your problem wasn't understandable before 😀

quick google returned PCTelnet or Eznos

if you need to enable network share access between your 98 and 7 machines, you need to enable guest file sharing in 7... it is disabled by default for security reasons

to enable (in vista/ 7):
click start, type "secpol.msc" in the search box and press enter (on your keyboard)
expand the "local policies" folder, and click on the "security options" folder
find "Accounts: Guest account status", then double click on it
change the selection to "enable" and click OK
close the window

now for any folders you are sharing in vista/7, you must edit the security settings for that particular folder to have guest file sharing access... it will be under the "sharing" tab in the folder properties and inside "advanced sharing"... you must add the guest username, and the guest usergroup to allow file sharing access from a system that doesn't respect logon credentials (win95/98 )

but that's not it... win95/98 does not support NTLM2 authentication, that's why there's a hold up when you try to login to a vista/7 network share from 9x... you need to enable NTLM2 this way:
1) install DSclient http://support.microsoft.com/kb/288358/
2) add the appropriate registry key to enable NTLM2 http://support.microsoft.com/kb/239869

you can also lower the security level in vista/7 to allow NTLM1 authentication, but it is not recommended... it can be changed through secpol.msc under local polices\security options under "network security: lan manager authentication level"... some in depth research is recommended beforehand: http://support.microsoft.com/kb/823659

as for file sharing from windows 3.1, you can't do it easily... stop wasting time with it and install windows for workgroups 3.11... not only is it faster and more stable, it DOES natively support SMB file sharing (what windows NT and all newer windows uses) over the network from file manager... netbiox and IPX/SPX is only supported out of the box, but if you want TCP/IP support, you need to install winsock to allow this... MS made one that worked ONLY with NICs, not modems: http://support.microsoft.com/kb/99891 but it is fast unlike trumpet or shiva (both of which support modems)... fact is, WFW3.11 is designed for small networks, while plain ol' win3.1 isn't... so again, stop bothering with the latter

remember, without any guest file sharing enabled, you won't be able to browse from your win95/98/ME machines to an vista or newer windows... default security settings just do not allow it

understand this is all "in theory"... I have no practical knowledge of this because I don't really have anything to share between an old system and my new ones, so I don't really care 😀

the best thing to do is google!

hi

here is an example setup to access the disk in DOS.

from linux i use the ftp command line client lftp.

from windows you would use cuteftp or similar.

example autoexec.bat section

1MODE CON CODEPAGE PREPARE=((850) C:\WIN98\COMMAND\EGA.CPI)
2MODE CON CODEPAGE SELECT=850
3LH C:\DOS\MOUSE.COM /Z
4LH C:\WIN98\COMMAND\DOSKEY.COM /INSERT
5LH KEYB UK,,C:\WIN98\COMMAND\KEYBOARD.SYS
6LH C:\DOS\PCIPKT.COM 0x60
7LH C:\WIN98\COMMAND\MSCDEX.EXE /D:VIACDR
8PATH;
9SET MTCPCFG=C:\MTCP\MTCP.CFG
10SET WATTCP.CFG=C:\DOS
11SET PATH=C:\MTCP;C:\WIN98\COMMAND;C:\DOS;C:\UTIL\GSPLAY;C:\SB16;C:\WBLAST2
12SET MIDI=synth:1 map:e
13SET SOUND=C:\SB16
14SET BLASTER=A220 D1 I5 H5 T6 P330
15DIAGNOSE /s
16MIXERSET /p /q

example C:\MTCP\mtcp.cfg

1DHCPVER DHCP Client version Nov 27 2010
2TIMESTAMP Sat Nov 27 10:50:38 2010
3packetint 0x60
4hostname DOSMACHINE
5ftp_connect_timeout 10
6ftp_tcp_buffer 16384
7ftp_file_buffer 32768
8FTPSRV_PASSWORD_FILE c:\mtcp\ftppass.txt
9FTPSRV_LOG_FILE c:\temp\ftpsrv.log
10FTPSRV_SESSION_TIMEOUT 120
11FTPSRV_CONTROL_PORT 21
12FTPSRV_PASV_BASE  2048
13FTPSRV_PASV_PORTS 1024
14FTPSRV_CLIENTS 10
15IPADDR 10.10.10.10
16NETMASK 255.255.255.0
17GATEWAY 10.10.10.1
18NAMESERVER 10.10.10.1
19LEASE_TIME 86400

you would change the settings above to that
suitable for your network.

in window7 you can see your current ip address
setup in CMD.EXE by typing IPCONFIG /ALL.
I won't go into any further detail regarding this.

example c:\mtcp\ftppass.txt

1myname   mpassword   [none]      [any]             all

when dos starts you would run the command
ftpsrv and leave it running. you can then access the
disk from the remote machine.

see
http://www.brutman.com/mTCP/mTCP_FTPSrv.html

for more info.

bye

ftp is cheating, but it's too halfassed to be true network file sharing

FTP isn't cheating and it isn't half-assed. It is the original file sharing program. ;-0

Mike (The PCjr and mTCP guy)

mbbrutman wrote:

FTP isn't cheating and it isn't half-assed. It is the original file sharing program. ;-0

Mike (The PCjr and mTCP guy)

Yup that ture it 40 years old

Sorry it took me so long to report back, but I've managed to get networking working in Windows 3.1 by upgrading to Windows for Workgroups 3.11 and using the driver I found (and TCP/IP-32), and from there on everything seemed to just work (which is how it should be 😀). However, I still can't get it working in DOS mode. I decided not to try an FTP server and do it the original way now I've got it working in Windows. I keep getting errors about NWLINK and NEMM.DOS.

Is it not supported in Windows 98 DOS?

Thanks

AdamP wrote:

Sorry it took me so long to report back, but I've managed to get networking working in Windows 3.1 by upgrading to Windows for Workgroups 3.11 and using the driver I found (and TCP/IP-32), and from there on everything seemed to just work (which is how it should be 😀). However, I still can't get it working in DOS mode. I decided not to try an FTP server and do it the original way now I've got it working in Windows. I keep getting errors about NWLINK and NEMM.DOS.

Is it not supported in Windows 98 DOS?

Thanks

Are you loading the drivers in the correct order?

For IPX:

1NET INIT
2NWLINK
3NET START
4NET LOGON

For IPX + TCP/IP:

1NET INIT
2NWLINK
3NETBIND
4UMB
5TCPTSR
6TINYRFC
7NMTSR
8EMSBFR
9NET START
10NET LOGON

Here is my config.sys:

1[Menu]
2menuitem=NoNetwork
3menuitem=Network
4
5[common]
6device=C:\windows\himem.sys /testmem:off /cpuclock:off /v
7dos=high,umb,auto
8device=C:\windows\emm386.exe noems 
9devicehigh=C:\windows\setver.exe
10devicehigh=C:\oak\oakcdrom.sys /D:mscd001
11device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
12Country=044,850,C:\WINDOWS\COMMAND\country.sys
13;devicehigh=C:\windows\command\ansi.sys
14FILES=45
15BUFFERS=30,0
16STACKS=9,256
17;devicehigh=C:\usbaspi.sys
18;devicehigh=C:\di1000dd.sys
19;device=C:\NETWORK\ifshlp.sys
20LASTDRIVE=Z
21;DEVICE=C:\WIN3\SMARTDRV.EXE /DOUBLE_BUFFER
22
23
24[network]
25DEVICE=C:\WIN3\IFSHLP.SYS
26
27[NoNetwork]

Here is my autoexec.bat:

1rem C:\WIN3\net start
2SET BLASTER=A220 I5 D1 H5 P330 E620 T6 
3SET MGA=C:\MGA\SETUP\
4mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
5mode con codepage select=850
6keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
7SET SOUND=C:\SB16
8rem SET PATH=%PATH%;C:\PROGRA~1\BORLAND\DELPHI5\BIN;C:\PROGRA~1\BORLAND\DELPHI5\PROJECTS\BPL
9
10rem PATH=C:\WIN3;%PATH%
11
12GOTO %config%
13
14:Network
15path=C:\win3;C:\network
16rem - By Windows 98 Network - C:\win3\net initialize
17rem C:\NETWORK\nwlink
18rem - By Windows 98 Network - C:\NETWORK\netbind.com
19rem C:\NETWORK\umb.com
20rem C:\NETWORK\tcptsr.exe
21rem C:\NETWORK\tinyrfc.exe
22rem C:\NETWORK\nmtsr.exe
23rem C:\NETWORK\emsbfr.exe
24rem - By Windows 98 Network - C:\WIN3\net start
25C:\windows\dosstart.bat
26
27
28:NoNetwork

I've just noticed - Windows 98 has remmed some of the network lines. Is there any way to stop Windows 98 from doing that? Or will I have to dual boot with DOS 6.22?

Just so you know, I may be gone for another few weeks, but I will be back.

Thanks