[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

3254.0. "OBM port management and Slip " by BELFST::BELCOO::HOUSTON (Peace at last) Thu Feb 08 1996 12:52

Hello.

I see from other topics that it is possible to manage the DH900 through the OBM port using 
SLIP and a modem. This is the configuration I want to use. 

However the documentation referred to seems to assume that you are using the Hubwatch 
supplied IP stack and you run strtslip.bat

I have configured my Windows Hubwatch on a Pathworks V5 eco3 client running the IP stack. 
It works fine inband.

I can edit PWTCP.ini for networktype=2.

From then on I am uncertain. Can I have my TCPIP stack ( up in Ethernet mode ) or do I 
need to create a separate template driving the TCPIP stack over the SLIP connection only ?

I need something to establish the link between the two modems talking in SLIP. What does 
this? Some kind of script ?

Thanks in advance for any help !

Regards,

Colin Houston 751 4062
T.RTitleUserPersonal
Name		DateLines
3254.1Need SLIP stackSNOFS1::KHOOJEANNIEHumpty Dumpty was pushedMon Feb 12 1996 01:1612
    Hi Colin
    
    You'll need to use an asynchronous SLIP stack (such as strtslip shipped
    with HUBwatch), as opposed to the Ethernet NDIS stack.
    
    I'm not a Pathworks expert, but in Pathworks v5 client configuration, there
    are a couple of asynch templates, one of which supports TCP/IP.  If
    you configure an asynch template during PWSETUP, some default scripts are
    copied to the client also, and you can customise these scripts for
    port, baud rate, dial string etc.
    
    Jeannie