| 1 |
Dale wrote: |
| 2 |
> Grant Taylor wrote: |
| 3 |
>> On 12/30/19 1:04 PM, Dale wrote: |
| 4 |
>>> Is there a way to find the IP for this thing? |
| 5 |
>> Try running a network sniffer as you reboot it. |
| 6 |
>> |
| 7 |
>> Most pieces of network equipment will send out some sort of broadcast |
| 8 |
>> requests that will give some hint as to how they are configured. At |
| 9 |
>> least what subnet they are in. |
| 10 |
>> |
| 11 |
>> |
| 12 |
>> |
| 13 |
> |
| 14 |
> I'm installing wireshark now. I'm starting to suspect this thing is |
| 15 |
> broke somehow. It is used but it may have set up unused for a while |
| 16 |
> before I bought it. Once wireshark compiles, I'll try it. I'll also |
| 17 |
> try anything else others come up with as well. |
| 18 |
> |
| 19 |
> Thanks. |
| 20 |
> |
| 21 |
> Dale |
| 22 |
> |
| 23 |
> :-) :-) |
| 24 |
> |
| 25 |
|
| 26 |
|
| 27 |
Got wireshark installed. Saved the results as a file. Doesn't seem to |
| 28 |
provide any info that is "sensitive" so attaching the file. I think it |
| 29 |
requires wireshark to open the file. It is not text only and I didn't |
| 30 |
see a way to do that either. It's been ages since I used wireshark. |
| 31 |
It's changed, a LOT. Still effective tho. |
| 32 |
|
| 33 |
Thoughts? It seems it can't negotiate a connection and just keeps |
| 34 |
banging away at it. |
| 35 |
|
| 36 |
Dale |
| 37 |
|
| 38 |
:-) :-) |
Archives