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
ttings?
>
>
>> -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:
>>
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:
> >
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/LANM
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
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
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."
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 wrote:
> On 6/15/2015 10:38 AM, Dave Kerber 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
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
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 ma
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
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 :
> Be sure that you have a good IP, gateway, and DNS setting from your DHCP
> server.
>
> On Sun, Jun 14, 20
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 :
> Yes, but in this case I'm not seeing that have any successful case to
> compare against.
>
> On 6/14/2015 6:01 P
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 appli
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 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 can
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
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 c
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
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
Hi,
On Sun, Jun 14, 2015 at 12:32 PM, John Hupp 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
> "
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
wrote:
> I installed MS-DOS Network Client, which successfully initializes with
> TC
22 matches
Mail list logo
