Re:gethostbyname problem (fwd)

Bill Woodland (
Sat, 20 Apr 1996 20:30:57 -0500

>Date: Fri, 19 Apr 1996 11:02:54 -0600 (MDT)
>From: Yani <>
>Subject: Re:gethostbyname problem (fwd)
>> ---------- Forwarded message ----------
>> Date: Fri, 19 Apr 1996 09:50:18 -0500
>> From: Bill Woodland <>
>> I run a Novell LAN at my office, and had the same problem. The solution for
>> me was simple, being the one that assigns the IP addresses from my class C
>> license. We use Trumpet Winsock and WINPKT for our TCP/IP stack for
>> Windows. We use a packet driver for our DOS TCP applications (UGH!).
>> Assumptions:
>> You log into the network before running windows
>> You go to your local C: drive and run windows from the c:\windows directory
>> You use Trumpet Winsock for your TCP/IP stack
>> Solution:
>> Create c:\windows\hosts that says:
>> mypc
>Bill, this was very helpful. I did find one thing though. There is a
>hosts file in my winsock directory which was being used instead of the
>c:\windows\hosts file. Also, I'm on an ISP TCP/IP LAN with no login
>to get initial connect to the network. I'm essentially on the 'Net.
> FYI, this machine is using trumpet winsock 2.0b, WINPKT and the crynwyr
>NE2000 packet driver running Win 3.11 for wkgroups. Feel free to fwd this
>wherever apropriate.
> _________________________________________
> Quantum Dynamics Research [ QDR ConTech ]
> Conventional Technologies Division
> Advanced Technology Research Facility
> Look for the red laser fence out in the middle of nowhere...

Get the entire collection of packet drivers from this URL:

Get for the executables of these. The other zips include the
source code for these drivers.

Bill Woodland (
Squeek on Undernet IRC
Channel Manager #CU-SeeMe
PC only, no MAC questions, please.