[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

1759.0. "ProbeWatch Cannot Communicate with Agent" by KETJE::VANDENBERG_R () Mon Dec 05 1994 13:58

	Hi,

	After the upgrade of the Packetprobe to 2.1 (display from the console)  
        and ProbeWatch 3.1, I have the following problem:
	Remark in PWTCP.IN UDPMaxSock is 30 and the IPSTACK is the one delivered
        with the kit.

	What I do is simply install DOMAIN ALL (no HOSTs, NO CONVs, NO PACKETs)
	Then from DOMAIN MANAGER -> Tools
                                 -> Segment Zoom
	I start the display.
	Everything goes fine for sevral minutes (max 5) then, I receive a popup 
        window with:


        ERROR ACCESSING AGENT .....
	WHILE RETREIVING DOMAIN ..
	ERROR: CANNOT COMMUNICATE WITH AGENT

		CONTINUE
             YES        NO

	From this moment, going to DOS I am not able to ping anymore on the     
        Probe address (other addresses are OK).
	Doing a ping from another machine is OK, I even can browse the RMON MIB 
            

	If I exit from Windows, the do a STOPNET, STRTNDIS, going back to       
        Windows, ProbeWatch, it works again for sevral minutes etc..

	Does somebody have an Idea where to look or which paramter should be
        modified?

	N.B. I have used Probewatch before (1.0) without any problem.

	Thanks in advance,
	Robert

T.R Title User Personal
Name Date Lines

1759.1 try adding more domains or groups NAC::FORREST Tue Dec 06 1994 17:57 5

T.R	Title	User	Personal Name	Date	Lines
1759.1	try adding more domains or groups	NAC::FORREST		`Tue Dec 06 1994 17:57`	5
	Well, the probe must still be working, since you can get to it from elsewhere. Sounds like a Windows or stack problem on the PC, but it's puzzling if you can ping other nodes. Try enabling more domains or groups to see if that makes a difference. Maybe it's just getting into some kind of race condition.

    Well, the probe must still be working, since you can get to it from 
    elsewhere. Sounds like a Windows or stack problem on the PC, but it's 
    puzzling if you can ping other nodes. Try enabling more domains or 
    groups to see if that makes a difference. Maybe it's just getting into 
    some kind of race condition.