Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
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 |
Can anyone tell me why when trying to use the Domain Manager in ProbewatchV3.1 for Windows I get "Error accessing agent probe3! While retrieving domains Error: Cannot open SNMP session with agent". I can talk to the probe using Probewatch from an Ultrix platform ok. I have launched the Data Capture ok and uploaded successfully. Thanks, Giles.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1778.1 | Try another PC | KETJE::VANDENBERG_R | Tue Dec 13 1994 11:19 | 30 | |
Gil, I have similar problem with my PC see 1759. I am using a DECPC 425 SL (486; 8 MBytes mem and PCMCIA XIRCOM adaptor card),a so called Workbench PC (OLIVETTI). I have spend already a day to fix that one without result , installing deinstalling the softwrare, changing IP stack, upgrading the XIRCOM driver and so one. What I see is that after several minutes, the PC can't communicate with the agent, I think also that this problem occurs when the load is high on the segment you want to monitor. From DOS you can ping on everything excepts the probe, but the probe is well reponding if you access it from another system, so the problem is in the PC and I should say in the IPStack or in the configuration ? If you wait a while then you are able to access the probe again. I did the same on DECPC 325 a DEC one (386; 8 Mbytes) same IP stack as in the kit, same XIRCOM adapter card, same config and it WORKS. Unfortunatly I don't have the time and other PC to play with, what I suggest you is to install it on another PC, that may perhaps help for the debugging of this problem. Best regards, Robert | |||||
1778.2 | This is a limitation of the PC. | SEOSS1::HARB_GE | George Harb, CNS, SEO6-15, 545-4202 | Thu Dec 15 1994 12:03 | 11 |
I've seen the same problem using the Frontier NETscount PC client running on MS Windows (it's the same software as Probewatch). There is a limitation with the IP stack with respect to the number of SNMP sessions that can be active at any one time. You'll find that if you close any other window that you launched with probewatch, you'll be able to open a new one. That's just the limitation of the PC. Best bet is to go to a UNIX platform. George | |||||
1778.3 | Make UDPMaxSock = 20 | NAC::FORREST | Wed Dec 28 1994 16:20 | 5 | |
I've noticed that this problem pretty much disappears if you edit PWTCP.INI and increase UDPMaxSock to 20. I think the problem is that the buffers allocated for UDP traffic is too small for PROBEwatch. |