> To: [EMAIL PROTECTED]
> From: [EMAIL PROTECTED] (Richard Menedetter)
> Subject: network
> Date: Wed, 04 Jul 2001 11:26:23 +0200 (CEST)
> Organization: Technical University of Vienna (Austria)
> Reply-To: [EMAIL PROTECTED]
> 
> Hi
> 
> 03 Jul 2001, "Luis A. Loeff" <[EMAIL PROTECTED]> wrote:
> 
>  LL> But I want to run the same internet DOS programs that I run through
>  LL> the PPP in the P166 client while the server A900 runs W98.
>  LL> So far I couldn't. I would like to know if I am missing something.
> 
> I have a similar setup ...
> 
> 192.168.0.1 is the linux masquerading server.
> 192.168.0.2 is tha athlon :)
>  LL> Details:
>  LL> The server communicates with the client using Microsoft TCP/IP
>  LL> protocol and assigns to itself IP address 192.168.0.1 and subnetmask
>  LL> 255.255.255.0 The client is supposed  to get his IP address
>  LL> automatically. But through recommendation of
>  LL> www.practicallynetworked.com I assigned IP address manually to the
>  LL> client and the internet sharing continued fine. I entered :  IP
>  LL> address 192.168.0.100
> why 100 ?!? ;))
> 2 seems more logical

   Hi

   I have read someplace that higher numbers are for workstations
   and smaller number are for specialized functions

>  LL>              subnetmask 255.255.255.0
>  LL>              Gateway1   192.168.0.1
>  LL> So I installed the ISA network adapter packet driver PNPPD.COM at s.i.
>  LL> 0x60 while base and irq are self configurating (0x340h, irq 12) and
>  LL> placed the above IP addresses in the wattcp.cfg file , and it didN'T
>  LL> WORK. The packet driver attaches fine to the card and also unloads
>  LL> fine but result is BAD HOST. May be somebody with network XP-rience
>  LL> has some idea.
> 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

 Regards

 Luis A. Loeff
> 

Reply via email to