| 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 |
A customer told to me that some 900 series modules send the bootp
request (same problem reported in notes 1533) even if in the menu I
read "bootp disabled". In that way they capture an ip address from a
Server causing many problems to the customer.
The modules that experience the problem are the DECrepeater 900TM
(firmware V2.0.0) and the DEconcentrator 900 MX (firmware V3.1.1)
The customer told me that he has seen the problem only with that
firmware revision... the older revision modules (i.e. DECrepeater
900TM V1.1.0) don't send any request.
One think done by the customer was the upgrade of the firmware in one
DECrepeater 900Tm from V1.1.0 to V2.0.0 ... after the upgrade the
module begun to send boot request.
The only bypass was to assign an ip address to each module.
Any suggestion or any confirmation about the problem?
Thanks to anyone that will answer
Francesco
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3647.1 | Is it sending requests ? | COMICS::BUTT | Give me the facts real straight. | Fri Jun 21 1996 10:20 | 11 |
Please see 3644.*
When investigating the problem described in 3644.0 I tested my 900TM
running V2.0.0. I can confirm that it did NOT send out BOOTP requests
with the BOOTP menu item disabled.
Are you sure that it is sending requests ? and that you are not seeing
something similar to note 3644.
R.
| |||||
| 3647.2 | Right, non DEC X-Terminal may be the cause | ROM01::GALLANA | Francesco Gallana | Fri Jun 21 1996 10:55 | 12 |
Richard,
you are right
The DECrepeater 900 TM doesn't send any request; my customer has some
non DEC X-Terminal.
I'll ask to the customer to investigate with a LAN analyzer.
Thank you
Francesco
| |||||