Access to NT share from DOS
This is a discussion about Access to NT share from DOS in the Slack Space category; Can anyone help me with this? I have a computer with a 3Com 3c905tx NIC and I need to boot from a floppy and connect to an NT4 server. I have used the network client administrator, (and i have the right NIC drivers from a floppy i made from Ghost 6.
Can anyone help me with this? I have a computer with a 3Com 3c905tx NIC and I need to boot from a floppy and connect to an NT4 server. I have used the network client administrator, (and i have the right NIC drivers from a floppy i made from Ghost 6.0). but i keep getting the error (using IPX) "5733 incorrect binding". Thanks for any help!
Jeremy Dennis
Jeremy Dennis
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Mar 2
Mar 3
0
1 minute
Responses to this topic
Unless NT4 Server has the Netware Gateway service installed, you will FAIL.
There is a DOS kit for Windows Networking that will allow you to connect over NETBEUI. Take a look in on the MS web site...
------------------
SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM
SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb
IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem"
Matrox G400 DH 32Mb AGP + Quantum3D Voodoo2 SLI PCI (CL TNT1 AGP on a shelf)
SoundBlaster Live PCI (not Value)
Win2K build 2195 Retail (not 120-day eval)
There is a DOS kit for Windows Networking that will allow you to connect over NETBEUI. Take a look in on the MS web site...
------------------
SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM
SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb
IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem"
Matrox G400 DH 32Mb AGP + Quantum3D Voodoo2 SLI PCI (CL TNT1 AGP on a shelf)
SoundBlaster Live PCI (not Value)
Win2K build 2195 Retail (not 120-day eval)
OP
Actually, i searched the Microsoft knowledgebase and found what i was doing wrong...it was just a matter of making sure all the ini files were configured correctly
