| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2008.1 | | STRWRS::KOCH_P | It never hurts to ask... | Tue Feb 14 1995 10:17 | 6 |
| A stupid question: Did you review the setup via the serial port? Does
he have the DECrepeater 900TM acting as the agent? When you put the
serial port into monitor mode, what does it show when accessing via the
ROAMabout vs. the 900TM?
|
| 2008.2 | | DPDMAI::DAVIES | Mark, SCA Area Network Consultant | Tue Feb 14 1995 12:29 | 13 |
| I reviewed the setup. The DECrepeater is acting as the agent. If not,
MY laptop would not have been able to access the DEChub.
What do you mean by "serial port in monitor mode"? Are you referring
to the serial port on the DEChub 900 chassis?
Remember, PING works fine, HUBwatch (on his system only) just doesn't
recognize the agent.
Regards,
Mark
|
| 2008.3 | NO RESPONSE FROM AGENT comprehensive reason list | NETCAD::WAGNERCOFFIL | | Tue Feb 14 1995 17:20 | 38 |
| The following is a comprehensive list of reasons why you could
get a NO RESPONSE FROM AGENT. Some may not apply to you
specifically but here they are for everyone else...
NO RESPONSE FROM AGENT message reasons list:
--------------------------------------------
1- Incorrect MIB file. Obtain from kit.
2- WINSOCK.DLL is not in path statement.
3- out of memory
4- No Response from agent (REALLY!)
5- Check HUBWATCH_LIBRARY and HUBWATCH_SYSTEM environment variables.
These may be set but may be incorrect especially if the customer
is running different versions of HUBwatch.
This would occur if the customer did not select to have
their AUTOEXEC.BAT modified. Therefore, the environment
variables are pointing to the wrong HUBwatch version that
was installed and thus trying to run.
6- WINSOCK.DLL should NOT be the same directory as the
HUBwatch.EXE. The WINSOCK.DLL should be located in the same
directory as the ipstack software. Delete the version located
where the HUBwatch.exe is located.
7- Entered incorrect Community string in the Specify Agent Window.
8- Check that the Network is running. PING can verify this.
9- Enter Community string in the Specify Agent Windows and have
a blank HW_AGENT.DAT file.
10- Can not create a socket. Increase TCPMaxSock and UDPMaxSock
in [TCPIP] section of the c:\hubwatch\ipstack\PWTCP.INI file.
If using a third party TCP/IP stack, increase the appropriate
indicators for that stack.
11- Unsupported device type.
12- Incorrect Message file HUB_MSG.MSF thus displaying incorrect
error message. May happen if reinstalled HUBwatch and using
previous version of the Message file.
13- Check WSAVERS environment variable. Should be set to 1.1.
This variable indicates WINSOCK.DLL version compliance.
If using a third party TCP/IP stack, the WINSOCK.DLL must be
Winsock 1.1 compliant.
|
| 2008.4 | DECPW.386 on Network line in system.ini | KEIKI::WHITE | MIN(2�,FWIW) | Tue Feb 14 1995 18:42 | 12 |
|
Last but not least -
Make sure that DECPW.386 exists on the network line in SYSTEM.INI
as certain Network reconfiguration in the network group will remove
this entry especially if configuring an alternative network like
Netware. We ran into this where we had to keep reinstalling the network
under hubwatch made sure it worked then added Netware to the
Networks section, and we kept getting NO RESPONSE FROM AGENT even
though we could ping fine.
Bill
|
| 2008.5 | Similar Troubles | DPDMAI::WISEE | Pobodys Nerfect | Tue Feb 14 1995 19:30 | 29 |
| I am having trouble with my Hubwatch for Windows (3.1) from 4 diff
platforms and 4 dif NICs 386/20/8Meg/PE2 486/25/8Meg/PE3 486/25/16Meg/PCMCIA
486/66/32Meg/DE202
I have verified that everything is correct as listed in .3 and .4
on all 4 machines.
I have the following configurations on 4 DEChub 900's IP addresses
are diff natch...
DEChub900 V 3.1.0 Slot 0 ;^)
In-Band IP 128.23.21.20 OB-IP 128.23.21.29
2 LAN's built { (Thinwire) and (FDDI_1) }
DECswitch900EF V 1.4.0 Slot 8
1A-Front 1B-Back (FDDI_1) 3-(Thinwire) 4/5/6/7-Front
DECconcentrator 900MX V 2.8.0 Slot 7
A/B-Back (FDDI_1)
DECconcentrator 900MX V 2.8.0 Slot 3
A-Back (FDDI_1) B-Front
DECrepeater 900TM V 1.1.0 Slot 1
1-(Thinwire) 2-Not Connected
If I set the In-Band to Slot 1 and place my UTP into any port on
the 900 TM in Slot 1 Hubwatch works fine.
If I set the In-Band to Slot 8 and place my UTP ANYWHERE I get
"No Response From Agent"
I have tried this with on 4 DEChub 900's with the same symptoms.
|
| 2008.6 | Thanks. | DPDMAI::DAVIES | Mark, SCA Area Network Consultant | Tue Feb 14 1995 22:35 | 8 |
| re: .3,.4
Thanks for the responses. I check 'em out.
Regards,
Mark
|
| 2008.7 | .0 : MS Windows should start in Enhanced mode | ULYSSE::LOUIS | | Wed Feb 15 1995 03:16 | 13 |
| Hi Mark,
Small think, but :->...
If windows is started in "Standard Mode", ping works fine
but Hubwatch doesn't, and you get the message "No Response From Agent" .
So don't forget to check on the program manager help item, the
mode used.
regards
yves
|
| 2008.8 | Never heard of it | DPDMAI::DAVIES | Mark, SCA Area Network Consultant | Wed Feb 15 1995 08:43 | 9 |
| I have never heard of STandard or ENhanced Mode. I checked the help
button on the Program Manager window and it didn't know either.
Where can I find out more about this?
Thanks,
Mark
|
| 2008.9 | Crossing cable fixed my trouble | DPDMAI::WISEE | Pobodys Nerfect | Wed Feb 15 1995 09:58 | 21 |
|
RE 2008.5
Set Face = Bright_Red
With a little luck at 9:30 P.M. last night I found out what my
trouble was.
A DECrepeater 900TM uses a BN25G cable (No crossing)
A DECswitch 900EF uses a BN24F cable (Crossing)
The clue that something was wrong with the cable came when I
noticed that the light on the PE2 stayed red when I plugged the cable
into the DECswitch 900EF, but would return to Green when I plugged it
into the DECrepeater 900TM.
Mushmind said you need a nullmodem cable not a modem cable and
I tried one. Everything worked fine!
Efw (A Little Wiser now)
|
| 2008.10 | Standard WIN /S versus Enhanced 386 WIN modes | NETCAD::WAGNERCOFFIL | | Wed Feb 15 1995 11:16 | 31 |
| re: .8
Mark,
Select the Program Manager, Help menu, About Program Manager... option.
Near the bottom of the window, it should say 386 Enhanced Mode.
When you start Windows you would have to specify WIN /S to invoke
standard mode. Standard Mode basically SKIPS the [386Enh] section
in the C:\WINDOWS\SYSTEM.INI file and executes the [STANDARD]
section which is typically empty.
The [386Enh] section contains information used for virtual-memory
page swapping, virtual-memory network drivers, and 32-bit disk access,
file access, and SCSI port drivers...
As stated in .4, DECPW.386 is required with the HUBwatch TCP/IP
stack(which is PATHWORKS V5.1 TCP/IP stack) in the [386Enh] section
of the c:\WINDOWS\SYSTEM.INI. DECPW.386 is the PATHWORKS windows
virtual-network driver that Windows uses.
Therefore, if you were running Standard Mode you would not be
specifying this required file to work with the PATHWORKS V5.1
TCP/IP stack.
When you start Windows WIN, the default is 386 Enhanced Mode.
You most likely are running the default.
Barb
|
| 2008.11 | 386 Enhanced Mode or 286 Standard Mode | ULYSSE::LOUIS | | Wed Feb 15 1995 11:32 | 23 |
| answer for .8
Mark,
You can check the running mode by selecting the "About Program Manager"
on the Help item of the "Program manager" group or "File Manager" tool.
It is the easiest way to check the running mode under Windows 3.x.
You can test the Hubwatch problem ("No Response From Agent") on your
Laptop, if you want, by starting Windows with the following command :
C:\WIN/S (like Standard).
Then, you need to restart windows with a WIN/3 (like 386) to run
in Enhanced Mode again.
Now, a question for "Hubwatch for MSWindows" specialists:
Is there any way to start Hubwatch in Standard Mode ?
Yves
|
| 2008.12 | HUBwatch runs in Windows 386 Enhanced only | NETCAD::WAGNERCOFFIL | | Mon Feb 20 1995 12:29 | 6 |
|
>>Now, a question for "Hubwatch for MSWindows" specialists:
>>Is there any way to start Hubwatch in Standard Mode ?
No.
|
| 2008.13 | another lack of answers | MLNCSC::CAREMISE | and then they were ...four ! | Mon May 22 1995 12:54 | 21 |
|
I'm having a problem with ONE of the four Hubs that I've, running
in a customer site.
The symptom "No response from Agent" comes from Hubwatch on a PC
and also on the Hubwatch for VMS on a V4060.
In fact the hub is working fine with all its component ( 2 DEC
Repeaters 900 with 50 users connected ) but since 2 days I cannot
communicate with the management port via Hubwatch.
The hub doesn't answer even to a normal ping . No other nodes on the
net has the same address ( if it was so, pinging the ip address
I should have someone else answer ....or not ? )
Hub is running version 3.1.0 of firmware and worked fine for the
last 2 months.
Any idea ?
Thanx in advance. Sergio.
|
| 2008.14 | | SLINK::HOOD | Maine state bird: The black fly | Mon May 22 1995 13:13 | 7 |
| If it doesn't reply to SNMP and it doesn't reply to PING, perhaps it doesn't
have a IP address any more.
Connect a terminal to the hub and ask it about its IP info.
Tom Hood
HUBwatch
|
| 2008.15 | ip address seems to be OK | MLNCSC::CAREMISE | and then they were ...four ! | Tue May 23 1995 05:18 | 16 |
|
Sorry, I forgot to say that the HUB correctly displays its IP
address on the LCD display.
We tried to reset the HUB yesterday night, and it worked for 10
minutes; then it failed again.
Now we have also strange problems on the repeaters :
an UNIX workstation, that load SW from the net, boots correctly,
but fails to mount NFS disks, due to timeout .......
Is there any errorlog in the Hub available , and how can I decode
it, if it is ?
Ciao. Sergio.
|