> > hmmm ...
> >
> > can you ping 192.168.0.1 ?!?
>
> Yes, yesterday I managed to ping to 192.168.0.1 with 100% success
> but failed to ping to 127.0.0.1 and
> also failed to ping to localhost
>
> using either a packet driver or a packet to ODI shim.
>
> As a final test I installed Trumpet Winsock 5c2 as a substitute
> to Microsoft Winsock in network client W95 OSR2.
>
> Result is same as with DOS packet drivers, it will ping to server
> but will not be able to open any internet application.
>
> This points me to: Only Windows 9x Microsoft TCP/IP protocol
> is allowed as a client for Internet Connection Sharing using
> W98SE or higher servers. I am not positive but looks like another
> example of Microsoft gridlock on everything
>
Hi folks
A few days ago I was able to solve my local network problem.
Basically the problem was no domain name server for the client.
So placing NameServer=192.168.0.1 in wattcp.cfg, same as gateway solved
all problems.
This taught me several lessons which I will carry with me for long.
1) Do not curse against Microsoft, for they are innocent before proven
guilty
2) Always read information generated by the manufacturer first, instead
of independent info.
I looked why I missed the NameServer setting.
In the www.practicallynetworked.com page it instructs to Disable DNS Server
In the support.microsoft.com page it suggests to manually place the
gateway number as the DNS Server, if this doesn't work then use the
same DNS as your ISP informs
Regards
Luis A. Loeff
