Conference netcad::hub_mgnt

2726.0. "Hubwatch Agent Problems" by KERNEL::ELCOCKW () Fri Sep 08 1995 06:11

    I have a customer who is trying to set up a Decrepeater900TM as an IP
    agent in his DecHub900. The physical connection is via a true NE2000
    card in the PC, through a patch to the repeater in the hub.
    
    He is using Hubwatch v3.1 for Windows with the Pathworks IP stack in
    order to accomplish this. 
    
    The Hub is using v3.1.0 of the hub firmware.
    
    The customer's problem is this: 
       Whilst he can ping the 900TM, when he tries to access it through
       hubwatch, it gives a "No Response From Agent" error.
    
    I have been through the following list of diagnostics, all to no avail.
    
            - TCP/IP running?
            - Duplicate IP addresses?
            - Incorrect SYSTEM.INI settings?
            - Windows started in standard / non-network mode?
            - Incorrect IP address specified in "specify agent" window
            - Incorrect community name entered in "specify agent" window
            - WINSOCK.DLL and PWWSOCK.EXE not found in the PATH statement.
            - Incorrect environment variables in AUTOEXEC.BAT
            - Incorrect firmware version in hub or module.
            - Hubwatch cannot create a socket
            - Incompatible third-party TCP/IP stack.
            - Low conventional memory
            - Unsupported device type.
    
    I have also suggested that the customer re-install hubwatch and the IP
    stack. He has also tried this all to no avail.
    
    Why is this problem occuring?
    
    Any help/tips etc would be greatly appreciated.
    
    Will

    Did you try resetting the hub and/or the 900TM?
    
    Cheers,
    
    Pedro