| 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 |
Hello.. :)
Once again I have a problem with a customer trying to get hubwatch to
work on a 3com card. The customer just keeps getting No responce from
agent.
I have had the exact same problem before with a cust trying to get a
3com card 509 to work with hubwatch note entry 2259, which was never
fixed in the end the cust used another ethernet card, and it worked
first time.
I have already checked everything mentioned in notes 2008 & 2216
The cust is running an Elonex pc340 386 sx16 with 4meg of ram
He is runing windows 3.1 and DOS 6.2
He is using s 3com 509 etherworks card.
The cust can ping the hub, and everything starts without any errors.
but every time he tries to get to the hub he get the no responce from
agent.
I take it we will need several files to look at to see if it is
possible to solve this, so if you could give me a list of files that
are needed I will get the cust to send them to me on floppy and I'll
will put them in the conference.
It's funny but it is always a 3com card that has ever caused me
problems with hubwatch, so lets see if we beat this one. :)
Cheers for any help steve ............
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2483.1 | MSAM00::KHENGHENG | Fri Jul 07 1995 14:25 | 5 | ||
I encountered the same problem with DECpc lp 325sx with 4 meg of ram
and etherworks 3 card. After changing the pc to 486/33 with 8 meg of
ram, everything works fine.
| |||||
| 2483.2 | Need at least 8 Meg | NAC::FORREST | Fri Jul 07 1995 15:14 | 3 | |
As stated in the SPD and elsewhere, 8 Meg is the minimum supported, and
16 is recommended for high density DEChub 900s.
| |||||
| 2483.3 | Cust got it to work on different PC | KERNEL::ARKLEYS | Mon Jul 10 1995 09:26 | 8 | |
in reference to .1 and I suppose .2 the customer did try another pc
running the same software etc, and this did not work, and cust then
tried a differnt make of pc, same config. but this worked first time.
So is this a problem with the PC's, the Ethernet cards, or a
combination of both trying to interact with HUBwatch.
Cheers Steve.
| |||||
| 2483.4 | Are the PCs CONFIGURATION really the same??? | NETCAD::WAGNERCOFFIL | Mon Jul 10 1995 15:01 | 25 | |
>> in reference to .1 and I suppose .2 the customer did try another pc
>> running the same software etc, and this did not work, and cust then
>> tried a differnt make of pc, same config. but this worked first time.
You say the same CONFIGURATION but we all know that PCs are configured
differently. Maybe just one less program is NOT loaded into
conventional memory or a parameter is different (e.g. BUFFERS, FILES).
If you really want to make sure the CONFIGURATION is the same then...
Copy the following files from the WORKING system to the NOTWORKING PC
and backup the files from the NOTWORKING PC.
-From the NOTWORKING PC, save the WIN.INI and SYSTEM.INI in the
\Windows directory and copy the WORKING system files to here.
-From the NOTWORKING PC, save the CONFIG.SYS and AUTOEXEC.BAT in the
C:\ directory and copy the WORKING system files to here.
-If the 3com card is the same and you are running the same network,
also save the PROTOCOL.INI and copy the WORKING system files to here.
>> So is this a problem with the PC's, the Ethernet cards, or a
>> combination of both trying to interact with HUBwatch.
8megs is the minimum of RAM required to run HUBwatch. It is possible
that different manufacturers of PCs "run differently".
Barb
| |||||