Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
But does your client machine know that? I.E. do you have the DNS server configured in the network settings? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 10:42 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Yes, in the static setup. And when I have had it configured instead in DHCP mode, I would expect it to pick that up automatically. On 6/16/2015 11:07 AM, Dave Kerber wrote: But does your client machine know that? I.E. do you have the DNS server configured in the network settings? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 10:42 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
The router provides DNS. On 6/16/2015 10:39 AM, Dave Kerber wrote: Do you have a DNS server configured? -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Tuesday, June 16, 2015 9:48 AM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
OK, I think now that there is more than one issue. After reviewing the fact that older Windows PC's have great difficulties connecting to Vista shares, I thought then that it probably shouldn't be surprising that this is very difficult to impossible for the MS-DOS Network Client. To test this idea, I slapped together a Win 98 machine, shared a folder, and found that the DOS client was able to connect and write to it just fine. When I last worked with FreeDOS several years ago, I think I was able to connect to Win XP, but unless one of you is successfully connecting to Vista or newer, I am inclined to write that off as a can't do. A separate issue: When DOS successfully connected to Win 98, ipconfig c:\net was still reporting that the lease was expired! And it did so whether I had configured DOS for DHCP or a static configuration. And likewise, whether it was configured as static or DHCP, the DOS client could still connect to the W98 share. The lease-expired status seems to be a bug. Yet another separate issue: As I described earlier, when I set up for a static configuration, this is ignored. I probably won't invest too much time into investigating, since I much prefer DHCP. - If I can't move files easily to/from the DOS client to a share on the Vista server, then I'll probably want to get wget and/or Arachne working. But so far I just have NDIS drivers installed, and wget seems to require packet drivers. I have a vague recollection that Arachne may also. So I think this will be my next interest. On 6/16/2015 9:48 AM, John Hupp wrote: Here's a reference, by the way, on the ipconfig usage that I mention below: ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q183/8/58.TXT A couple more observations: When I booted up this morning, ipconfig c:\net once again reported the lease expired, but the expiration time coincided exactly -- to the minute -- with the bootup time, and the lease-issued time was exactly 24 hours before I booted up this morning. Thinking to dodge the DHCP lease issue, I set up with a static IP outside the DHCP address scope (but still within the same subnet segment). Nonetheless ipconfig c:\net still reports an IP within the DHCP scope, rather than the static IP I assigned. Current functionality: I can successfully ping an IP address e.g. ping 8.8.8.8 but name resolution fails, so no-go on ping google.com. On 6/15/2015 8:25 PM, John Hupp wrote: I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
you can install a normal client on a computer and make and reord the transition data using wireshark, and compare, or just sniff the data and see if for example yhe request exit well formed from client, in some cases the error code in the packet data is more explained that what you can see at application level. 2015-06-15 0:15 GMT+02:00 John Hupp free...@prpcompany.com: Yes, but in this case I'm not seeing that have any successful case to compare against. On 6/14/2015 6:01 PM, Roberto Fazzalari wrote: I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
bt you write: Linux machines on the LAN connect to the server OK with the same account., record the transaction on that machine and compare. 2015-06-15 0:15 GMT+02:00 John Hupp free...@prpcompany.com: Yes, but in this case I'm not seeing that have any successful case to compare against. On 6/14/2015 6:01 PM, Roberto Fazzalari wrote: I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
for example you can do this by looking at the data coming from the client network interface sniffing with wireshark outgoing data from the client 2015-06-15 6:09 GMT+02:00 Louis Santillan lpsan...@gmail.com: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. On Sun, Jun 14, 2015 at 3:37 PM, John Hupp free...@prpcompany.com wrote: Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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-windows-vista-or-server-2008 ), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Forgive me if I didn't catch it, but are you able to ping successfully w/o a full network setup (just connect via packet driver and DHCP) and are you able to use wget or fdnpkg and download a file? On Mon, Jun 15, 2015 at 2:15 PM, Ralf Quint freedos...@gmail.com wrote: On 6/15/2015 10:38 AM, Dave Kerber wrote: Are you trying to connect by dns name, or by IP address? To take one level of possible trouble out of the equation, try connecting by IP addr. If the ipconfig doesn't show any IP info on the host, it doesn't matter how you try to connect from that host, either way it has to fail. Your approach would only work in case just the DNS server info wouldn't be properly set. But the really strange thing is that he states that he doesn't even get a proper response when setting a static IP on the host, with ipconfig still claiming that it doesn't get info from a DHCP server. That indicates that there is rather something more basic amiss... Ralf --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Are you trying to connect by dns name, or by IP address? To take one level of possible trouble out of the equation, try connecting by IP addr. -Original Message- From: John Hupp [mailto:free...@prpcompany.com] Sent: Monday, June 15, 2015 12:20 PM To: Discussion and general questions about FreeDOS. Subject: Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. --- --- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
I found out that ipconfig usage is not as expected for the DOS client. Ipconfig /all is meaningless. In my case, the one and only good command is ipconfig c:\net. This then reports (now again under DHCP), an IP address, gateway, and DNS server as expected. But it reports Lease Expired. Even after I forced the router to give it a brand new lease on a different IP, it still reports the lease expired. The router shows the lease as freshly issued with a day to live. The date and time are correct on client and server. Ideas? (And no, ipconfig /release or ipconfig /renew won't work either. They too are meaningless.) On 6/15/2015 12:19 PM, John Hupp wrote: I just tried changing the DOS client from DHCP to static configuration, and I still get the same net use error. Furthermore ipconfig /all still reports No DHCP data available. Shouldn't it report my static configuration info? On 6/15/2015 11:46 AM, John Hupp wrote: Fundamentals -- you may be onto something. Though TCP/IP initialization completes without error, running ipconfig /all yields No DHCP data available. I get the same result from two identical cards, both configured the same way. I do note that both cards are old non-PNP ISA cards, which I thought would be appropriate for this vintage rig. In the meantime, 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/jj852207%28v=ws.10%29.aspx. Then I rebooted. But I still get the same error on the DOS client. @ Roberto Fazzalari: I have been avoiding your approach to date since I never had more than a rank novice's acquaintance with Wireshark. But it may be that I'll have to get reacquainted! On 6/15/2015 12:09 AM, Louis Santillan wrote: Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
I use to resolve this kind of problem by monitoring the network traffic; capture the traffic data on the network wen the transaction go well aand when not and compare it, in this way you can understand more, in the past i use to do in this way to resolv problems. 2015-06-14 22:22 GMT+02:00 Rugxulo rugx...@gmail.com: Hi, On Sun, Jun 14, 2015 at 12:32 PM, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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. ... Linux machines on the LAN connect to the server OK with the same account. I tried disabling SMB2 via a registry entry ... but this made no difference. Anyone know how to fix this? Don't use Vista ... just use Linux! :-)) (Seriously, it's not wrong to dual boot. I know you want to use DOS, which is fine, but you really might have better luck with ZipSlack/Slackware 11.0 [2006] atop UMSDOS: ftp://ftp.slackware.com/pub/slackware/slackware-11.0/zipslack/ ) -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Networking: With MS Client, Error 5: Access has been denied
Be sure that you have a good IP, gateway, and DNS setting from your DHCP server. On Sun, Jun 14, 2015 at 3:37 PM, John Hupp free...@prpcompany.com wrote: Though my initial interest (and testing) was oriented toward moving files on the LAN, I also find that I cannot ping web sites. I get DGN0217: Remote name cannot be resolved. On 6/14/2015 6:14 PM, John Hupp wrote: Thanks, but making that change did not make a difference. I have also now edited the HOSTS file to add the server there, due to what I read at ftp://ftp.microsoft.com/misc1/BUSSYS/LANMAN/KB/Q130/5/38.TXT about not being able to ping the server. So I can indeed ping the server now, but access is still denied for the net use command. On 6/14/2015 3:06 PM, TJ Edmister wrote: Did you check the NTLM compatibility mode in Vista? HKLM\SYSTEM\CurrentControlSet\Control\Lsa There should be a DWORD named LmCompatibilityLevel set to value of 1 On Sun, 14 Jun 2015 13:32:34 -0400, John Hupp free...@prpcompany.com wrote: I installed MS-DOS Network Client, which successfully initializes with TCP/IP via DHCP. But when I try 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-windows-vista-or-server-2008), but this made no difference. Anyone know how to fix this? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
