This is my problem:
I'm trying to connect a DOS-machine to a Windows 7 computer, using a LAN-crossover-cable - and it won't work.
I want to access a shared directory on the Windows-PC from the DOS-machine. Best solution would be to assign a drive-letter to the shared directory and make that persistent.
I've done this before we got new hardware, establishing that connection from the DOS-machine to a Windows XP computer worked just fine.
Using Windows 7 now, it won't.
Running Windows 7 (Ultimate - or Professional, not sure right now) 64bit. There are two network cards in it, one for the logon via authentication server, internet and so on - and the second one only to build a connection to the DOS-Machine.
There is a separate local user specified, with name and password.
There is also a shared directory in
C:\ with full acces rights to exactly that user.
(That's exactly what i did when using XP)
It's exactly that - a machine. Not a PC. It's a CNC machine with a special control software and so on. This control software is running on DOS and the network connections are built up via DOS, too.
I can't tell you which version of DOS - but scanning through the directorys i tend to say that this isn't some kind of "normal" DOS-version. Seems to be something "special" or "minimal", just to get the machine software running and providing basic things.
Using the mentioned XP-computer a while ago, i could use the
NET commands to establish a connection using a drive letter, the shared network path - and the specified userdate, name and password.
That just worked. That so configured shared directory was visible and usable when running the machines control software - that's the goal of all this.
Trying to build up the connection as i did before only results in the following error:
The computer specified in the network path cannot be located.
Explanation: The server that you specified does not exist or has not been startet.
...at least that's the error message when using the "GUI" the
NET-command provides. When directly using
NET USE ... the error code is the same, just the text message slightly different (...but basically saying the same).
As i'm not into networking that much, i have no idea what to do. There must have been some changes in the network protocols from XP to 7 - that's all i can say.
I've read something about a tweak using
gpedit.msc and setting the "LAN Manager authentication level" to "Send LM & NTLM - use NTLMv2 session security if negotiated". Didn't do anything.
I've also read something about allowing "NetBIOS" on the network adapter on the Windows 7-PC, so i changed the advanced TCP/IP v4 settings - didn't do anything.
I've also stumbled upon an error on the DOS-machine - i can't use
ping there. The command itself is somehow broken, instead of some appropriate message i only see undefinable characters on the screen. I don't know if that could have any influences on the network settings.
I didn't call the machine support by now - and i don't think i will. They are not very helpful with this network-issues, they weren't able to build up a working connection when we had XP (that's why i dit that by myself).
Plus, there is no useful documentation of the machine when it comes to that topics. Detailed informations simply doesn't exist - i've asked any possible adress for that, even the japanese manufacturer of the machine.
16. Sept. 2013
I've tried to connect to the Windows 7-PC using
net use x: \\hostname\\shared_dir - that's leading to the mentioned
Error 53. I also tried that command with the option
/PERSISTENT:YES, same error.
net view \\hostname, that raised
Error 53, too.
I get the same error when trying the computers IP instead of
\\hostname - both on
net use ... and
net view ...
PC DOS Version 6.3
...so there's no MS-DOS running on the machine. I don't know how important that is, when it comes to this network connection.
Rik managed to connect his old 486-machine (runnning MS-DOS 6.22) to a Windows 7-Computer, see his answer below. I followed his steps and configured both systems like he did (changes in gpedit.msc, adding the computer to LMHOSTS, configured a new user, ...), without success - i'm not even getting various error-codes, i'm stuck with
I don't know if it's mandatory, but i changed the workgroup and the domain for the DOS-machine to match the Windows 7-PC. That wasn't the case before. It didn't help to get this working, but raise a new kind of error, when trying
net view \\hostname:
Error 6118: The list of servers for this workgroup is currently not available.
Whatever that means.
I also tried to connect another computer to this Windows 7-PC, so i brought my Notebook (running Windows 7) and unplugged the DOS-machine.
I could get a working connection between those Windows-computers at the first try, just as this should work. Both computers can ping, view and connect to the other one, all fine.
By doing this, i recognized that the two windows-machines were only talking to each other using IPv6. I'm pretty sure that the DOS-machine can't handle this new protocol and even using the two Windows-PCs, this connection shouldn't require IPv6. So i disabled this protocol from the network adapter settings.
Result: ...i lost the connection. No PC was able to ping, view or connect to the other one, they just couldn't find each other anymore.
After enabling IPv6 again, everything worked just fine.
...i don't know why this Windows 7-computers need IPv6 to communicate. I don't think it's "good" that way, as this could cause a problem when trying to connect the DOS-machine.
I don't know what's happening there - and where to make changes to get IPv4 working.
The machine is in use most of the time (...Data is transferred using Floppy-Disks), but as soon as there's time for it, i'll try any helpful suggestion.
There is no more need to think about this problem. Thanks for anyone who helped me trying several things!
Just look at the date - it's been 2013 when i tried to solve this problem. Not long after fiddling around with various settings, i've been told that it's not my job to look after this issue.
I just wanted to help, but have been told to mind my own business - and so i did.
Of course, it's still not working.
Two month ago, i overheared a conversation about this topic. Someone seems to have recognized that this broken connection is really annoying and should be fixed. Until now, nothing has happened.
Floppy discs FTW.