[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

1802.0. "Hubwatch & IP STACK problems. Anybody??" by VAXSPO::INTERD_MARIO () Wed Dec 21 1994 07:57

    Hello,
    
    Has anybody been having problems to run Hubwatch for Windows v3.1 
    when the IP stack IS NOT the one that comes with the Hubwatch kit?
    
    We had problems in 2 different situations:
    
    1) On a Novell network: Novell IP stack & utilities (eg. Telnet, ping) work
       fine, but Hubwatch doesn't. When we replace Novell's IP stack
       by Hubwatch's stack, it works fine.
    
    2) The same problem in a Windows for WG network.
    
    
    Regards, Mario

T.R Title User Personal
Name Date Lines

1802.1 DECPW.386 needed for HUBWATCH to work KEIKI::WHITE MIN(2�,FWIW) Wed Dec 21 1994 12:13 7

T.R	Title	User	Personal Name	Date	Lines
1802.1	DECPW.386 needed for HUBWATCH to work	KEIKI::WHITE	MIN(2�,FWIW)	`Wed Dec 21 1994 12:13`	7
	We noticed that after selecting an ODI stack, but using PATHWORKS TCPIP stack that we gad to manually edit DECPW.386 back into SYSTEM.INI or HUBWATCH wouldn't work, even though TCPIP worked fine from within Windows for Workgroups. Bill

    
    	We noticed that after selecting an ODI stack, but using PATHWORKS
    TCPIP stack that we gad to manually edit DECPW.386 back into
    SYSTEM.INI or HUBWATCH wouldn't work, even though TCPIP worked fine
    from within Windows for Workgroups.
    
    						Bill