Conference netcad::hub_mgnt

Please check out not 2008 (especially reply .3).  Barbara has spent uncounted
hours (days, weeks, ... ) documenting HUBwatch setup and installation quirks
that help alleviate the "No response from agent" message.

...Roger...

    Maybe Note 2216 is relevant here too?
    
    jack

    Thanks for the reply but no one has got it yet, I maght have to get the
    cust to try a re-install.
    
    But everything seems to start ok, no errors at all until you get the
    error, NO RESPONCE FROM AGENT. 
    
    I have read the other two mentioned articles I have gonce through the
    first, and checked everything but nothing there, and the second is a
    startup problem.
    
    But thank you any way, but please don't give up on me yet :)
    
    Cheers Steve.

	If you have checked all the notes in 2008.* and have verified 
	all of these conditions then start typing.

	Make sure that DECPW.386 is in the Network= line of the SYSTEM.INI.

	Otherwise, it sounds like a PC configuration problem. Does HUBwatch
	have a PC configuration support center????

	The support center needs the AUTOEXEC.BAT, CONFIG.SYS, 
	\WINDOWS\PROTOCOL.INI, SYSTEM.INI, \PW\PWTCP.INI, and 
	\PW\CFG000n.TPL.

Barb

    reply to .4
    
    I'm at the support centre, and I have the files, mentioned, but I just
    don't have the knowledge to know what should be there and what
    shouldn't but I supose if there's no known problems with the 3com card
    that could cause this strange phenomina, (because I know there have
    been problems with these cards) then I guess the cust will have to try
    another PC Cos there's no way I'm typing in 20 plus pages
    of configuration files. (then again I might be able to get them on
    disk)
    
    checked the network line :) 
    network=*dosnet,*vnetbios,decpw.386
    
    are these correct from system.ini
    	[network]
    	winnet=pathworks/xx040100
    	multinet=nonet
    	filesharing=no
    	print sharing=no
    	computername=yeb03
    	LMAnnounce=yes
    
    	[network drivers]
    	devdir=c:\windows
    	loadRMDrivers=yes
    	transport=dllndis.exe
    	dllndis.exe=low
    	dllndist.exe=low
    	ipxndis.dos=low
    
        Ok I would like to thank you for your reply anyway, if no more
    suggestions come forth I will have to (shoot myself) .. No tell the
    cust to try re-installing everything, to see if that does it.
    
    Cheers Steve.

	From the excerpt that you included: looks like the customer is 
	running WFW and PATHWORKS 4.1 and there is no Novell integrated
	into the MS network(since it is not on the network line in SYSTEM.
	INI).
	
	You should have PW V5.1 if you are running WFW. 

	Please provide the PATHWORKS file that loads the stack.
	i.e. STARTNET.BAT for v4.x or CFG000n.tpl for V5.x.
	The last section [Network] is all that is needed out of
	the .TPL file.

	You really need to provide the CONFIG.SYS, AUTOEXEC.BAT, and
	\PW\PWTCP.INI files.

	How much memory does the PC have?	

Barb

	I had a problem w/ the 3C509 before in that the IRQ was incorrect
	and I had to pull a new driver off of COMPUSERV but in that case
	the driver would not load. Are you sure everything in PATHWORKS
	loads correctly? Place PAUSE statements after each component in
	PW start up file so that you can verify that they load successfully.

    Thanks for the continued ideas :) any way from what I can see the
    version of pathworks they are running is version 5.0.
    
    here is the network section from CFG0001.TPL
    
    	[network]
    	{+DEST}SCHK.EXE{SW_SCHK}
    	{+DEST}DNP.EXE{SW_DNP}
    
    Right now for the other files.
    **************************************************************
    AUTOEXEC.BAT
    
    set HUBWATCH_LOAD=C:\FIRMWARE
    set HUBWATH_SYSTEM=c:\HUBWATCH
    set HUBWATCH_LIBRARY=C:\HUBWATCH\USERDATA
    set WSAVERS=1.1
    PATH C:\;c:\dos;C:\windows;C:\net\bin;C:\PW;C:\pcapp;c:\hubwatch
    SET TEMP=C:\TEMP
    SET TMP=C:\TMP
    |
    LOAD MOUSE, DOSKEY, KEYBOAD.SYS
    |
    :END
    CLS
    IF EXIST C:\OPSTART.BAT CALL C:\OPSTART.BAT
    
    *****************************************************************
    OPSTART.BAT
    
    GOTO %CONFIG%
    
    :NOVELL
    LH DOSKEY
    IF NOT EXIST C:\NWCLIENT\LSL.COM GOTO NONETWARE
    IF NOT EXIST C:\NWCLIENT\IPXODI.COM GOTO NONETWARE
    IF NOT EXIST C:\NWCLIENT\NETX.EXE GOTO NONETWARE
    LH /L:1,16288 C:\NWCLIENT\LSL.COM
    LH /L:1,34352 C:\NWCLIENT\3C5x9.COM
    LH /L:1,30576 C:\NWCLIENT\IPXODI.COM
    LH /L:1,70400 C:\NWCLIENT\NETX.EXE
    C:\VGAMODE.EXE
    F:\LOGIN\LOGIN
    F:
    PATH X:;W:;F:;Z:;Z:\PUBLIC;C:\;C:\DOS;C:\WINDOWS;C:\NET\BIN
    CLS
    C:\NET\BIN\TCPIP.EXE
    GOTO END
    :NONETWARE
    ECHO NETWARE CLIENT SOFTWARE MISSING, NETWARE NOT STARTED.
    :DONENETWARE
    GOTO END
    
    :DECNET
    COPY C:\PW\DEC.TPL C:\CFG0001.TPL /Y
    IF EXIST C:\PW\STARTNET.BAT CALL C:\PW\STARTNET.BAT
    C:\VGAMODE.EXE
    C:\WINDOWS\WIN
    GOTO END
    
    :HUBWATCH
    COPY C:\PW\HUB.TPL C:\PW\CFG0001.TPL /Y
    CD \HUBWATCH\IPSTACK
    CALL C:\HUBWATCH\IPSTACK\STRTNDIS.BAT
    CD \
    
    :END
    
    ******************************************************************
    CONFIG.SYS
    
    [MENU]
    MENUITEM=NEVELL
    MENUITEM=DECNET
    MENUITEM=HUBWATCH
    
    [COMMON]
    DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
    DEVICE=C:\DOS\EMM386.EXE NOEMS
    BUFFERS=20,0
    FILES=40
    DOS=UMB
    LASTDRIVE=E
    FCBS=4,0
    DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS
    DEVICEHIGH=C:\DOS\SETVER.EXE
    DEVICEHIGH=C:\DOS\POWER.EXE
    DOS=HIGH
    COUNTRY=044,,C:\DOS\COUNTRY.SYS
    SHELL=C:\COMMAND.COM/P/E:1000
    STACKS=9256
    DEVICE=C:\DOS\ANSI.SYS
    
    [DECNET]
    DEVICE=C:\PW\PROTMAN.DOS /L:C:\PW
    DEVICE=C:\PW\ELNK3.DOS
    
    [HUBWATCH]
    
    **********************************************************88
    PROTOCOL.INI
    
    [protocol manager]
    	DRIVERNAME = PROTMAN$
    
    [datalink]
    	DRIVERNAME = DLL$MAC
    	LG_BUFFERS = 14
    	SM_BUFFERS = 6
    	OUTSTANDING = 32
    	BINDINGS = ELNK3.DOS
    	DECPARAM = c:\HUBWATCH\
    	NI_IRQ = 5
    
    [elnk3.dos]
    ;
    ; 3c509 3com etherlink III adapter
    ;
    	DRIVERNAME = ELNK3$
    ;
    ;   I won't put int the rest of the text.
    
    
    
    Right I have the PWTCP.INI file, if it is needed, do you require the
    whole 3 pages or just a small amount, I don't have the startnet.bat,
    but I will request it.
    
    any more info required please feel free to ask. 
    
    Cheers Steve..
    

    Well thank you for you r continued efforts, but the cust has now
    installed it on another Pc, and it works, but this pc does not have
    pathworks on ETC. If you realy want to find the reason why it did not
    work then by all means I can still get the rest of the information.
    
    Cheers, and thanks again for your replies,
    
    STEVE ;)
    

	It may be a PATH related problem.

	I notice that the PATH in AUTOEXEC.BAT is
	PATH C:\;c:\dos;c:\windows;c:net\bin;c:\pw;c:\pcapp;c:\hubwatch
	
	First, the correct path for HUBwatch is c:\HUBWATCH\IPSTACK NOT
	C:\HUBWATCH. In the case of the above PATH statement, the WINSOCK.DLL 
	shipped with the HUBwatch IP stack will never be found. I think 
	this is where your problem is.

	The WINSOCK.DLL is found through the PATH.

	You should search the whole disk to see where all the WINSOCK.DLL are
	located. If the directories that they are located appear before
	the \HUBWATCH\IPSTACK directory, it will use the first one found.

	For instance if there is one in the \WINDOWS, \NET\BIN, \PW,
	or \PCAPP directories, the HUBwatch application will use one of these.
	You will not be using the WINSOCK.DLL that ships with the HUBwatch
	stack. This could explain why you could PING, since PING uses
	ICMP and does not use WINSOCK.

Barb

    Nice try but been there tried that, you can give up if you want to.
    
    Cheers steve :)