| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9764.1 | check the RFC | SMURF::DUSTIN | | Fri May 09 1997 09:55 | 8 |
| Take a look at the "assigned numbers" RFC for the list of assigned
hardware addresses, you will probably find this is a router or
other hardware box. You can run tcpdump and capture all packets
to and from the hardware address in question, maybe you'll see
something which helps narrow down the owner of the address.
John
|
| 9764.2 | | COMICS::CORNEJ | What's an Architect? | Fri May 09 1997 10:09 | 5 |
| Thanks - I've verified the addresses from the RFC - all manner of 3rd
party boxes (at least 300 different addresses from about 10 vendors).
Jc
|
| 9764.3 | | KITCHE::schott | Eric R. Schott USG Product Management | Fri May 09 1997 13:18 | 10 |
| Hi
when I have seen this..it was a router/bridge with
an snmp agent but it is not configured with
a tcp/ip address...
If you use netview or serverworks on the network, you can
actually see where it is logically on the network.
|
| 9764.4 | For completeness | COMICS::CORNEJ | What's an Architect? | Mon May 12 1997 07:46 | 8 |
| This appears to be an ASE issue - it corrupts the routing table when
relocating a service (try netstat -rn).
A patch was issued at some stage.....but it is not on-line now. A CSC
call has been logged.
Jc
|