Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

TCPIP Dos/Winos2 Functionality

Posted on 1997-08-22
9
Medium Priority
?
852 Views
Last Modified: 2013-12-27
I have the following lines correctly situated in my config.sys:
      DEVICE=d:\tcpip\bin\vdostcp.vdd
      DEVICE=d:\tcpip\bin\vdostcp.sys
      RUN=d:\tcpip\bin\vdosctl.exe
Also in WINOS2 DOS_DEVICE it says:
      d:\tcpip\bin\vdostcp.sys
PROBLEM: I should be able to use the DIALER in WARP 4 and
then be able to connect to NETSCAPE in WINOS2, but the WIN version of NETSCAPE gives me the following error messages:

      WSO0002:Local Status NCB Failure
      Possible causes
      .Network TeleSystems TCP Stack not loaded
      .Invalid adapter number
      
      Netscape was unable to create a network socket or      connection
      There may be insufficient system resources or the
      network may be down (Reason:Network is down)

      Do you have any idea how to correct this problem?
0
Comment
Question by:harvey0
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 1

Accepted Solution

by:
sbufton earned 240 total points
ID: 1806653
It looks to me like you have another
winsock.dll in your DOS PATH before Warp's
winsock.dll. Make sure that the path set
in the AUTOEXEC.BAT includes
C:\TCPIP\DOS\BIN early on (perhaps before
c:\os2\mdos\winos2).

      Steve
0
 

Author Comment

by:harvey0
ID: 1806654
     This above may be one solution to a similar problem, but it is not the solution to my problem.
      When I boot into WINOS2, I do not get the following advisory:
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
              Virtual TCP/IP Version 2.1 for DOS
              Copyright (c) IBM Corp. 1992, 1993
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
              Version:  2.1.0.3
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

This suggests that I have not set up something properly to enable the TCP/IP advisory to show on booting into WINOS2.
I believe that this failure is what is causing the SOCKET problem.
      I'd appreciate knowing "WHAT" I need to do to correct this and "HOW" I would go about making the correction.
      Thank you.
      Harvey Goldenberg

0
 
LVL 1

Expert Comment

by:sbufton
ID: 1806655
I've taken a look at the settings for
"Windows Ping", in the TCP/IP utilities
folder. Having just tested it, I know that
it works:

The DOS_DEVICE contains
c:\tcpip\bin\vdostcp.sys

The AUTOEXEC.BAT contains:
PATH=C:\OS2;C:\OS2\MDOS;C:\;C:\OS2\MDOS\WI
NOS2;c:\tcpip\dos\bin;
SET ETC=c:\tcpip\dos\etc

Those are the only two TCP/IP-relevant
settings. I also do not see the message
you mention when I open a DOS window.

If you have those settings, I can only
suggest again checking for a winsock.dll
earlier in your DOS PATH than the
tcpip\dos\bin\winsock.dll - remember to
check in the WINOS2\SYSTEM directory, and
the Netscape directory too.

      Steve
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:harvey0
ID: 1806656
     I would love for it to work as you say, but it does not.
I obviously do not have something configured properly. I do have the tcpip\bin files correctly listed. The PROBLEM "MUST BE" with
my having failed to INSTALL some part of the TCPIP aparatus or
the MPTS. Wherever my failure is, it still exists and I CANNOT use the dialer connect from the WARP 4 desktop to run NETSCAPE for WIN.
0
 
LVL 1

Expert Comment

by:sbufton
ID: 1806657
Can you use PING from a DOS prompt? Or the
Windows PING? If those work, then it
points to something (probably a
WINSOCK.DLL) in your Netscape directory.


0
 

Author Comment

by:harvey0
ID: 1806658
     Although I kept getting "timeout" notices in DOS Ping, I was able to WPING in WINOS2. I still do not know HOW to go about to get WINOS2 to use the WARP4 Winsock.dll. Please inform me.
      You've given me hope that this CAN work.
0
 
LVL 1

Expert Comment

by:sbufton
ID: 1806659
Good news, some progress!

OK, take a look in your Netscape directory. Can you find a
WINSOCK.DLL file there? I suspect that this file is from some
other product (Network TeleSystems), and is getting in the way
of the Warp WINSOCK.DLL. If you can find something like that,
try renaming it to WINSOCK.LLD and then starting Netscape.

      Steve
0
 

Author Comment

by:harvey0
ID: 1806660
Steve. Thank you. You solved my problem. Just as you suggested, I renamed the WINSOCK.DLL WINSOCK.LLD and I was able to use the WARP 4 IBM dial and open a working NETSCAPE in WINOS2.
      Thanks again,
      Harvey Goldenberg
0
 
LVL 1

Expert Comment

by:sbufton
ID: 1806661
Good! I'm glad I could help.

      Steve
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article was originally published on Monitis Blog, you can check it here . If you have responsibility for software in production, I bet you’d like to know more about it. I don’t mean that you’d like an extra peek into the bowels of the sourc…
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
With the power of JIRA, there's an unlimited number of ways you can customize it, use it and benefit from it. With that in mind, there's bound to be things that I wasn't able to cover in this course. With this summary we'll look at some places to go…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question