Discussion Locked

here is a good one...

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a win2000 machine and I need it to see a DOS machine. I know it says that I am out of luck in the White pages but is there a way I can trick it into seeing this DOS machine??? I am putting a 500point bounty for the best answer...Thanks!

14 replies

by dmiles

No chance, will create more of a problem than it would be worth the dos drivers are not recognized.

by mcorr

What services will you need from the NT server? If you only need to transfer files, then there are solutions out there.

There are direct connection products such as FastLynx (www.sewelldev.com), that will start on boot to allow file transfer.BTW what are you keeping the DOS machine around for? Is there any way to port the function to a newer PC? Or maybe upgrade the PC. You can pick up Win95/486 PCs for under $200 these days.

by guy

What you need is a Dos 3.0 client. On NT 4.0 It was in the Admin Tools, Network Client Administrator, I guess that would work, or else it may be In Win 2000 somewhere!

by fofa

Actually, we have DOS machines that can SEE the NT machines, but not the other way around. If you share a drive on the NT box you can NET USE it on the DOS box as long as MS Networking is loaded.

by mckaytech

I'm not clear what you mean by "see" the DOS machine. I'm assuming that you want to use the DOS machine for some type of I/O - i.e. to make some input or output device on the DOS machine available to the network (I have two such DOS devices that run proprietary machine interfaces).

That should be feasible and with more details about what you're trying to do, I could offer a better answer as to how you would accomplish that. It might be something like running the application as a DOS app ona machine with WfW3.11 installed with the 32-bit TCP/IP stack - I've done that to support a DOS fax-receiving app that then passed the received faxes to a server for storage and printing.

Never say never...

paul

by avidetto

There are a couple of ways, 2000 will operate SMS 2.0 , which will see all 9x,Nt,&2000 boxes. 1.2 will see Dos/Command Line, also rclient will see command line. Remote into another box (test enviroment first please)open a CMD/Command Session. Use the Dosbased Remote client of your choice that will work from a 9x to Dos. Make sure your at 10 on your network.
Method 2. Use Novell 3.1 Server, set perfered server=servername in csnw for 9x machine (or equ. on doxbox). again use Novell's Remote functions to connect to the dosbox.
Method 3) Try a Rclient into the dosbox, servcies may/maynot work, this is questionable..Ntreskit functions can emulate this..ie. At command at x.x.x.x c:\install.bat truth be known, if you can get an IP you can connect with that type of client/server situation. Note Method 1 is the only GUI based method. Good Luck..Al

by avidetto

There are a couple of ways, 2000 will operate SMS 2.0 , which will see all 9x,Nt,&2000 boxes. 1.2 will see Dos/Command Line, also rclient will see command line. Remote into another box (test enviroment first please)open a CMD/Command Session. Use the Dosbased Remote client of your choice that will work from a 9x to Dos. Make sure your at 10 on your network.
Method 2. Use Novell 3.1 Server, set perfered server=servername in csnw for 9x machine (or equ. on doxbox). again use Novell's Remote functions to connect to the dosbox.
Method 3) Try a Rclient into the dosbox, servcies may/maynot work, this is questionable..Ntreskit functions can emulate this..ie. At command at x.x.x.x c:\install.bat truth be known, if you can get an IP you can connect with that type of client/server situation. Note Method 1 is the only GUI based method. Good Luck..Al

This discussion is closed to new replies.