[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

1962.0. "HUBwatch windows:no telnet if non-DEC n/w" by ONOIS1::GAIRNS () Fri Feb 03 1995 04:29

    I have to install Hubwatch for windows on an IBM PC (ISA) that uses :
    IBM DOS
    IBM-supplied ethernet driver
    IBM IP software.
    
    As the IP network is installed and works successfully on the PC, I
    chose to INSTALL HUBWATCH BUT NOT THE NETWORK.
    
    AND......IT WORKS!!!!!! (or appears to)
    
    I have no problem starting up Hubwatch and using all the SNMP
    facilities.
    
    HOWEVER  the customer has purchased a large number of BROUTERS.
    When I click on the telnet icon within the Brouter screen, it all
    goes sick on me.
    
    This is hardly surprising as it appears that the telnet session is
    offered by SETHOST.EXE which is only installed when the "install
    network" option is requested.
    
    So I set up a subdirectory /IPSTACK and put all the software into it.
    
    BUT it still falls over because several programs below, the product
    looks for TN and below that the Digital IP stack. 
    
    I have come to a dead end.
    
    How can I use the IBM IP stack which works fine for everything else?
    
    Thanks
    
    Ian Gairns

T.R	Title	User	Date	Lines
1962.1	Not supported w/ other stacks but...	NETCAD::WAGNERCOFFIL	`Tue Feb 07 1995 11:06`	20
	SETHOST.EXE and TN.EXE are part of the PATHWORKS for DOS and Windows V5.0 TCP/IP stack which is included in HUBwatch for Windows. Therefore, you can not use these with another stack. You may be able to...??? Obtain a TELNET executable from IBM to run with their stack. Copy the SETHOST files from the HUBwatch kit. The SETHOST files must be in a directory location in your PATH statement. The SETHOST files include: SETHOST.EXE, SETHOST.HLP, aSETHOST.PIF, KBDEPC.KBD(IBM Enhanced PC keyboard map file), and KBDEPC.HLP. If the keyboard map file is not the correct one you should obtain the correct one from the PATHWORKS V5.0 for DOS and Windows kit. A list of them can be found in SWOPS::USER3:[DOCS.V50_DOS_WIN_CLIENT] TERMINAL_GDE.PS, page 3-7. You may have to edit the SETHOST.PIF file with the PIF Editor found in MS Windows Main group. Let us know if you tried this and how you made out. Barb
1962.2	re .1 the deeper you go the harder it gets	ONOIS1::GAIRNS	`Wed Feb 08 1995 03:54`	24
	re .1 Barb, I've done most of what you suggested .I'm prepared to have another bash at it but .... I believe that hubwatch preloads the telnet software ie its some sort of TSR. This isn't the case with the IBM telnet software. The DEC Telnet and IBM telnet executables do not have the same name. Is it likely that IBM Telnet software will offer the same interface to SETHOST as the DEC telnet software? Do you think that I stand much of a chance? This is all a crying shame as there is no problem with the SNMP part of Hubwatch. Thanks for your comments. Ian
1962.3	may be out of luck, problem noted	NETCAD::WAGNERCOFFIL	`Wed Feb 08 1995 13:42`	20
	Ian, I see your point... FYI, Telnet is loaded in c:\hubwatch\ipstack\strtndis.bat file(tn.exe). Also, TELNET can be loaded at the DOS prompt and unloaded at the DOS prompt. This is the syntax for what the HUBwatch code expects: WinExec "sethost.pif telnet: 01.02.03.04" I figured that the TELNETs may not have the same name but since the IBM one is not a TSR nor does it sound like it can be run on it's own, I think you are out of luck. I do not know anything about IBM's TELNET. You may want to try the PATHWORKS DOS and Windows V5.0 notesfile: NOTED::PWDOSWINV5 or call IBM. Your situation has been noted and we will see what we can do for the future around this type of problem. Barb