🚀 go-pugleaf

Radient Software support <support@radient.com> writes:
>Nancy McGough <nancym@ii.com> wrote:
>>I just downloaded CommNet and am using it right now!
>>According to the Help:
>>
>>Requirements for Telnet Operation
>>
>>CommNet is a Windows Sockets application with integrated Internet
>>Telnet capability.  In order for this feature to be utilized, a Windows
>>Sockets protocol stack needs to be currently installed in addition to
>>being connected to the Internet.  The Windows Sockets protocol stack
>>needs to adhere with the Windows Sockets Version 1.1 specification or
>>above.
>
>If CommNet is having problems finding the winsock.dll from Netmanage,
>make sure one of the following applies:
>
>   1.  Check your PATH variable in AUTOEXEC.BAT and add the directory
>       where your winsock.dll is located.
>   2.  Copy winsock.dll into your \windows directory or \windows\system
>       directory.
>   3.  Copy winsock.dll into the directory where CommNet is.
>
>The first option would probably be best to avoid the same problem with 
>any other non-Netmanage winsock application.

My WINSOCK.DLL has been on my path all along so that wasn't the
problem.  Anyway, I just downloaded the latest (1.1D) and I'm still
having problems telnetting to a host while I'm dialed in to a shell 
account.  The message I get is:

  Could not obtain host name

I tried putting different telnet hosts into my phone book, even the
same host that I'm dialed into, and always get the above message.
Do I need to give it an IP address or tell it a lookup server to use?

It sounds like CommNet could be a really great product - I'd just
like to figure out how to get the telnet part to work!

Thanks,
Nancy
-- 
 /\_/\                  @..@    Please make sure your host gets the  /\_/\
( o.o ) Nancy McGough  (----)   new humanities.* newsgroups. Info   ( o.o )
 > ^ <  Infinite Ink  ( >__< )  is at http://www.jazzie.com/ii/      > ~ <