Conference netcad::hub_mgnt

2556.0. "Novell NMS and Hubwatch on same PC ?" by BRIEIS::BARKER_E (test dummy) Tue Jul 25 1995 16:29

    Hi, 
     
    	I'm having problems setting up Hubwatch Version 4 on a Novell 
    NMS Console, and could do with some advice. 
     
    	With Hubwatch Version 4 there is support for Novell NMS. I'm 
    having problems getting NMS and Hubwatch to run using the same IP
    stack.  I can get one or the other but not both, if anyone 
    has a working config that they can provide details on I'd be very grateful. 
     
    The PC is set up with Novell's NMS Version 2.0c , and is running the IP 
    stack that ships with NMS, which we think is LAN Workplace for DOS.   
     
    If I install Hubwatch without a network (as we have an IP stack already
    with the NMS) the install works but if I try to start Hubwatch up a double
    click on the icon shows the hourglass for a couple of seconds  and then
    nothing.  I had a suspicion that there was a winsock problem and it 
    does look as though the tcp/ip stack is fairly old, the tcpip.exe 
    with NMS shows a copyright date  of 1992 and a version number of 4.1. 
     
    I then tried setting up Hubwatch with the PathWORKS IP stack supplied 
    with Hubwatch, and pulled a WINSOCK.DLL from PathWORKS into 
    c:\windows.  This was more recent than the one that had been in there 
    before.  Took out all startups of  IP that were tied to the NMS version
    and used a NET.CFG and STRTODI.BAT from the \hubwatch\windows 
    directory.  This got IPX working and Hubwatch also fired up OK, but the 
    NMS software will not see any TCP/IP systems etc. and all the options 
    related to IP such as ping's etc. are greyed out in the windows boxes.     
     
    Should this work ?  Does this look like a winsock incompatibility and
    if so does anyone know if Novell's NMS can be used with our IP stack ?
    
    Thanks for any ideas, 
     
    	Euan
    

	Try DIR/TITLE="ODI "
	especially note 2108, 1240, 2114.
Barb

    Thanks for the pointers but I've already read them, followed through
    the info etc., no joy.
    
    	Euan

    I've managed to get Netrider tftp server working by now using the
    latest patches etc. available for the LAN workplace stack and it's
    winsock.dll etc, and using the LAN workplace stack.  
    Hubwatch is getting slightly further but after I
    enter a IP address and community name I get a 'system error' window,
    and can go no further.
    
    Has anyone got a copy of a working config. of Hubwatch with Novell NMS
    and/or LAN Workplace ? 
    
    	Thanks again,
    
    		Euan

>>    enter a IP address and community name I get a 'system error' window,

	Check the NO RESPONSE FROM AGENT MESSAGE WHEN HUBWATCH IS INVOKED
	section(2nd to last section) in the READ_ME.TXT or .PS file.

Barb

    
    Just curious...
    
    	You checked that the  WINSOCK.DLL in LAN WP is Winsockv1.1
    compliant?
    	Definitively using the one included with PW should work

    Sorry the last line of the previous note should say
                                "should not work"