Solved

TCP/IP and DHCP with OpenDOS 7.02

Posted on 1997-12-29
3
284 Views
Last Modified: 2012-06-21
I've installed OpenDOS 7.02 with the Netware client
and drivers for 2 ethernet cards. I'd like one card
to connect to a cable modem using DHCP and the other
card to connect to a unix box. First, will this support
TCP/IP and DHCP as is? If not what do I need to add?
And second, how do I configure one card to get its IP
address from the cable modem by DHCP, and how can I
assign a fixed IP address to the other ethernet card?

I'm not sure how to tell which client came with the
OS. But the configuration setup for networking allows
support for both Netware 4.x and 3.x.
0
Comment
Question by:ghowland
[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
  • 2
3 Comments
 
LVL 5

Expert Comment

by:jstegall
ID: 1591490
What client and version?
0
 

Author Comment

by:ghowland
ID: 1591491
Edited text of question
0
 
LVL 5

Accepted Solution

by:
jstegall earned 100 total points
ID: 1591492
I don't Know if your client support multiple protocols and , or can use the same protocol on two networks but here is what Novell
say of client32.  Client32 is the only client that  support multiple network connections.
You can read the Appnotes for 1996 and 1997 online at:
http://developer.novell.com/research/appnotes.htm

The TID is below:
"Binding Protocol to Multiple NICs in Client32"
  (Last modified: 06MAY1997)

     This document (2910840) is provided subject to the disclaimer at the end of this document.
         Forward this document to a colleague
         Submit comment about this document to its author

     Issue

     An article in the September 1995 Appnote entitled "An Introduction to Novell's NetWare
     Client32 for Windows 95" implies on page 10 that it is possible to bind a single protocol stack to
     multiple network boards and transparently route packets to disparate networks simultaneously.
     This is an incorrect assumption and, as of this writing, is not possible. C32W95 does not at this
     time have the capacity to route packets between separate networks. (This is the same with
     Client32 DOS/Win as well).
     If a user chooses to load separate network cards on a single station he can bind different
     protocols to individual boards with Client32 which will recognize both cards and bindings, but
     the user is faced with an either/or situation where s/he must choose to use either one at a time,
     but not both at the same time. The user can, for example, load NIC 1 and 2 and connect board 1
     to network A and board 2 to network B, but cannot do both at the same time, neither
     concurrently nor in a rapid switching fashion. If the user desires to switch from utilizing
     resources in network A to network B (board 1 to board 2), s/he must restart Windows 95 after
     changing the preferred server for one network to a server in the other network by entering that
     name in the "Preferred Server" field under the "Client32" tab in "Novell NetWare Client32"
     properties. Client32 properites are found under "Network" icon in the Windows 95 control panel.
     Keep in mind that the above scenario applies when using multiple protocols at one time for each
     board. The user can connect to multiple networks simultaneously if the user is willing to bind
     each protocol to only one board at a time, eg. by binding IPX/SPX to board 1 and talking only
     IPX/SPX on network A, and binding TCP/IP to board 2 and talking only TCP/IP on network B.
     The user will have to ensure that the appropriate boxes are selected under the "Bindings" tab in
     the network adaptor properties. This is not to say that Client32 acts as a gateway between the
     two networks. Again, Client 32 as of this time has no routing capability, and there are no
     concrete plans or statements to this effect for the near future.

                    Please select if this document solved your problem.

      Document Title:
                          Binding Protocol to Multiple NICs in Client32
      Document ID:
                          2910840
      Creation Date:
                          25JUL96
      Modified Date:
                          06MAY97
      Document Revision:
                          2
      Novell Product Class:
                          NetWare OS
      Novell Product and Version:
                          IntranetWare Client for DOS/WIN 3.x 2.12
                          IntranetWare Client for Windows 95 2.12


     DISCLAIMER

     The Origin of this information may be internal or external to Novell. Novell makes every effort within its means to
     verify this information. However, the information provided in this document is for your information only. Novell
     makes no explicit or implied claims to the validity of this information.

     Any trademarks referenced in this document are the property of their respective owners. Consult your product
     manuals for complete trademark information.





         
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

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

With the rising number of cyber attacks in recent years, keeping your personal data safe has become more important than ever. The tips outlined in this article will help you keep your identitfy safe.
The recent Petya-like ransomware attack served a big blow to hundreds of banks, corporations and government offices The Acronis blog takes a closer look at this damaging worm to see what’s behind it – and offers up tips on how you can safeguard your…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
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…

622 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