[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

1662.0. "No response from agent..." by WRAFLC::STAPP () Fri Nov 04 1994 15:56

    I am trying to configure HUBwatch 3.1 on a customers PC.
    The PC is running PATHWORKS v5.1 - TCP/IP with a SMC card.
    PATHWORKS is configured for NDIS support.
    
    When I installed HUBwatch I chose HUBwatch only (I have been
    through the install procedure and instructions several times).
    I have manually populated the HW_AGENT.DAT file with entries
    from a local VAX (which is working fine). 
    
    When I start HUBwatch from the icon, I get the main window and a
    window to specify an agent. (I can find nothing in the doc about
    this window coming up). Every agent I try (from HW_AGENT.DAT)
    gives me "No response from agent". They all respond to pings.
    
    any ideas?
    
    -Allen
T.RTitleUserPersonal
Name		DateLines
1662.1KAOFS::S_HYNDMANAcronym Decoder Ring ArchitectFri Nov 04 1994 16:359
    
    
    	If you haven't already done this try:
    
    Select IP address field and enter in the ip address for the hub or
    standalone module.  Hubwatch should figure out what agent it is talking
    to.  Should work if they are pingable.
    
    Scott
1662.2Case sensitive agent namesROGER::GAUDETBecause the Earth is 2/3 waterMon Nov 07 1994 10:484
Are you typing the agent name exactly as it appears in the agents file?  It
turns out that the name is case sensitive.

...Roger...
1662.3ThAnKs FoR ThE HeLpGNATS::STAPPTue Nov 08 1994 13:435
    
    Thanks Roger...
    
    Using the proper case for the agent name appeared to resolve the 
    problem.