VOGONS

Common searches


First post, by jd_hupp

User metadata
Rank Newbie
Rank
Newbie

I'm hoping that someone who uses networking for a game has solved this one.

With FreeDOS 1.1 on real hardware, I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP.

But when I try to set up access to a share on the LAN with "net use z: \\server\share" and enter the password (with a user name that matches the Win Vista peer server account), I get "Error 5: Access has been denied."

Likewise, "net view \\server" yields the same error.

And "net view" yields "Error 6118: The list of servers for this workgroup is not currently available."

Linux machines on the LAN connect to the server OK with the same account.

I tried disabling SMB2 via a registry entry (per https://www.petri.com/how-to-disable-smb-2-on … -or-server-2008), but this made no difference.

Based on someone's advice, I also edited the Registry to change HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel from 3 to 1, which did not help either.

After noticing that I could not even ping the server, I found ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT. Adding the server name to the HOSTS file allowed a ping of the server to succeed, but the net use command failed as before.

Widening that ping probe, I tried pinging google.com and got "DGN0217: Remote name cannot be resolved."

Anyone know how to fix this?

Reply 1 of 5, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie

For Windows XP SP3 and later (But not Sp2 and before), in Control Panel -> Administrative Tools -> Local Security Policy, you will need to do the following to allow legacy clients to access shares:

"Network Security: LAN Manager authentication level"

lm1.png
Filename
lm1.png
File size
73.11 KiB
Views
2491 views
File license
Fair use/fair dealing exception

Change it to this:

lm2.png
Filename
lm2.png
File size
20.57 KiB
Views
2491 views
File license
Fair use/fair dealing exception

"Send LM & NTLM responses"

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 2 of 5, by jd_hupp

User metadata
Rank Newbie
Rank
Newbie

Thanks Mockingbird. Vista Home doesn't have a Local Security Policy tool in Control Panel, but in the Registry I changed HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel=3 –> 0, which is "Send LM & NTLM responses" per https://technet.microsoft.com/en-us/library/j … v=ws.10%29.aspx. Then I rebooted.

Nonetheless it seems to be a necessary-but-insufficient measure. I still get the same error on the DOS client.

Reply 4 of 5, by bnewland

User metadata
Rank Newbie
Rank
Newbie

If you have multiple DNS servers, maybe failover setup, or BigIP, or NetApp hardware, it could be that they are not syncing. Anyhow, I would suggest starting with ip before name resolution to get it id'd.
Can you ping the ip of the server? Traceroute to the ip? Is it possible that some other machine is using your ip simultaneous? What is netstat saying about the connections state? You may also try checking the AD reference commands, on TechNet: https://technet.microsoft.com/en-us/library/cc771131.aspx
If that all doesn't help any, perhaps it is time to fire up Wireshark? Or solarwinds.com has some free tools that are pretty good for trial-ware, http://www.solarwinds.com/downloads/

Good luck.

Reply 5 of 5, by jd_hupp

User metadata
Rank Newbie
Rank
Newbie

After reviewing the fact that even earlier versions of Windows have great difficulties accessing shares on Vista machines, I have concluded that the MS-DOS Network Client is going to be a no-go.

But if any of you actually has this working with Vista Home from a DOS client on real hardware, then the issue may be worth revisiting.

As it is, I have an alternative solution that I am happy with. I installed the mTCP suite on the DOS machine and run its FTP server as needed. It is fast and not a memory hog like MS-DOS Network Client.