Link to home
Start Free TrialLog in
Avatar of Jason-
Jason-

asked on

DOS Networking

I have a computer running DOS that has a network interface on it. I have the Networking files configured to be on my network which is running inside a Windows Server 2012 Domain Controller. It has been a while since I have needed this DOS machine and it used to work on my network but no longer does. I configured its IP address for my network as static and provided authentication credentials from Active Directory and everything was working fine but I cant get it to work anymore. The DOS computer needs to be able to access files across the network on another computer in the same network/domain.

When booting the DOS computer all of the networking executables are working and it gets to the part where it prompts for the username and password and they are keyed in and I get this message:

"You were logged on, but have not been validated by a server. Therefore, you may not have permission to use some network resources."

After this DOS completes its booting and I can ping the DOS machine from another machine in the network. It just cannot access any of the shares.

Anyone have any clues of why it may not be able to authenticate on the network?
Avatar of LockDown32
LockDown32
Flag of United States of America image

Wow does this date. What DOS networking system are you using? Workgroup for Windows 3.11and DOS 6.22?

This link has some resolutions with 2008 R2 Server but I really doubt you'll find any Server 2012 articles in this day and age. Good luck!

https://social.technet.microsoft.com/Forums/windowsserver/en-US/dbdab0be-dccc-4c04-a520-ce2fd08bd6d1/smb-issues-with-r2-and-win311-for-workgroups?forum=winservergen
Avatar of rindi
Modern server OS's have security in place that won't allow connections from Windows ME or older systems. Although there are ways (I believe) to reduce those security enhancements, that is a really bad idea.

Find some other, less insecure way to get the data on your DOS PC. Maybe for example share a directory on the DOS PC and copy from the server to it rather than the other way round. Or virtualize the DOS PC using VirtualBox for example, and then use VirtualBox's shared folders, I believe that should work. Or use a USB stick to transfer files (provided you have USB drivers for DOS).
Did the DOS machine ever work with the Server 2012 machine?

Network protocols used by DOS might not be enabled by default on 2012.  I'm no network guru, but I think netbios protocol is needed.

A similar problem cropped  up on EE where the author of the question solved his issue by enabling "netbui over tcp/ip" (I think he means NETBIOS over TCP/IP).  So, that confirms my thinking.  See the answer here:
https://www.experts-exchange.com/questions/22740804/Domain-login-Not-validated-by-a-server.html

If there are other security features in Server 2012 that are blocking that, as the other experts pointed out, I'm not sure what you can do to resolve the issue.  

What is the purpose of the DOS machine? Can you move those functions or tasks to more a current OS?
That is a interesting article Alicia. I am trying to remember the last time I tried it and I think I actually had to track down TCP/IP 3.2 for Windows 3.11 or something like that. Microsoft also  did something to their SMB Protocol with Server 2012 that stopped a lot of copiers from accessing a Server 2012. I am still curious as to which DOS networking package he is using. There were more than one back then and it would make a difference.
have you enabled a wins server on 2012? You will need wins and netbios over tcpip
SOLUTION
Avatar of Vince Glisson
Vince Glisson
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jason-
Jason-

ASKER

The machine that runs DOS is actually a CNC Mill that operates via an application that runs on DOS. When we bought the networking package years ago they sent in an upgraded version of the CNC Software along with the instructions on how to setup DOS to be configured on the network. Back then I was running Server 2003 R2 and I had to enable NetBIOS on the server to get it to work (This was not in the instructions). We have since migrated to Server 2012 and we are now bringing the CNC back into production as we have acquired new business that we will need the mill to execute.

We are currently scripting the jobs from ArtCAM to floppy disk and transferring it that way. So we are not totally in the dark here but we are limited to the size of the floppy disk drive for the jobs we can run. I have called the manufacturer of the CNC Mill to get help but as you can guess they no longer support it as it's well beyond its life cycle and pointed me to someone who was not real helpful.

For some reason I cannot find any activity coming from the DOS machine in Wireshark. The error message comes extremely quick which makes me feel like its not trying to even contact the server for authentication or its being rejected right away because of rules in the server 2012 I do not know about.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jason-

ASKER

Windows Server 2012 is 64bit and no version of NetBEUI exists for 64bit machines so I have come to the conclusion that this DOS machine will never be able to communicate with a 64bit OS. I am going to try and spin up a 32bit VM and try to pass the files across it. I am closing out this solution, thanks for everyone's input.