[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

1252.0. "Hubwatch + windows for workgroups" by COMICS::REYNOLDS (Mad Dogs and Englishmen) Tue Jul 26 1994 12:53

    
    Hi,
    
    
    	a customer has enquired as to support in Hubwatch-for-Windows
    for Windows-for-workgroups v3.11. It currently supports Windows
    v3.1 and not v3.0  -  I understand this new platform is a whole
    lot different!
    
    Will it work? If not, any future plans?
    
     
    
    thanks,
    
    		John.

T.R	Title	User	Personal Name	Date	Lines
1252.1	WFW fix in next release	NAC::FORREST		`Tue Jul 26 1994 17:42`	6
	HUBwatch for Windows V3.1, our next release, should work with the WFW IP stack. HUBwatch V2.0 used the Pathworks V5.0 code, and there was a fix in Pathworks subsequently for WFW.
1252.2	Works fine in WFW 3.11	CXPERT::MCLENDON		`Wed Jul 27 1994 14:50`	6
	Hi, I'm running Hubwatch v2 on a WFW 3.11 system just fine. However, I'm also using the IPSTACK directory and not the IP in WFW. So, if you're asking a compatibility/operability question, "yes", it works. Bruce
1252.3	HUBwatch and Windows for Workgroups using TCP/IP	SNOFS1::ELEFTHERIOU		`Wed Oct 26 1994 21:55`	18
	Gidday, So Bruce, are you saying that HUBwatch does NOT run using the WFW TCP/IP stack? because I have a customer who wants to use the native Microsoft 32bit TCP/IP stack under WFW with NO NETBEUI network. He receives an error message ERROR:SOCKET CANNOT BE CREATED ERROR NUMBER RETURNED 1001. The operation of the PC under TCP/IP is just fine, it is only the HUBwatch component that fails. I have asked him to start WFW as DOS> win/n (start WFW with no net) and to try using the HUBwatch supplied TCP/IP stack. I am waiting to hear back from him but it would be nice to know if what he wants to do will work. Thanks in advance, Harry E.
1252.4	Works ok here....	SCCAT::MILLER		`Mon Oct 31 1994 16:13`	6
	I have it working on a 425 laptop. Just did an "add protocol" to bring in the RELEASED version of WFW TCP/IP (the beta version didn't work) and then install Hubwatch only. It came up without doing any manual modifications to any PC files. Works great! I still have the NETBEUI protocol installed, but I don't use it for anything (the laptop is mainly used on customer's IP networks).
1252.5	WfW with Banyan	GRANPA::DFAUST	Bad Things, man...	`Wed Jan 11 1995 10:25`	6
	I have a customer that is running WfW, using the Banyan network drivers. Can HUBwatch use their stack to run, or do I need to load the Pathworks IP stack that comes with HUBwatch? Dennis Faust
1252.6		KERNEL::MCSKEANEP	one bit brain with parity error	`Wed Jan 11 1995 11:53`	17
	I have a customer running WfW and HUBwatch. If he uses the supplied stack in the IPSTACK directory, everything works fine. If he tries to use a Pathworks V5.0 stack, then he gets an 'agent not responding'. He is however able to ping the hub using this stack. I took a trace and could see the ping packets going out but when I tried to start up HUBwatch, no packets were seen on the network. Any clues as to why I can't get this working? I tried reproducing the problem here at the CSC but the only PC I could get hold of here was running Pathworks V5.1 and everything seemed to work okay. The customer is using V5.0C of the client and server Thanks, POL.