Here's a reference, by the way, on the ipconfig usage that I mention
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
126.96.36.199" 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
>>> 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